Abdelrhman Shawky

Software and cloud stuff. He/Him. Opinions are my own.

[Abdelrhman Shawky @shawkyz1]

@excid3 Request failed successfully

[Lynx @Purring_Lynx]

dockerize your microservices

[Stack Overflow @StackOverflow]

We’re thrilled to announce we’re partnering with @OpenAI to bring best in class technical knowledge and the world’s most popular LLM models for AI development together! This groundbreaking partnership with OpenAI will drive our mission to empower the world to develop technology through collective knowledge.

https://t.co/CbgZIEoB2z

[Matt Boyle @MattJamesBoyle]

John Cena is bullish on Postgres too.

[Abdelrhman Shawky @shawkyz1]

@AhmedHemaz @ahmd3ssam @YouTube فيه already linux foundation backed fork

https://t.co/8RpTNLJ18z

[Abdelrhman Shawky @shawkyz1]

@m_aty @Bashmohandes Jonathon Blow talked about this 2 years ago on how bad actors can include backdoors in OSS projects
https://t.co/avpYlEYB24

[Abdelrhman Shawky @shawkyz1]

@m_aty @Bashmohandes It took him 2 years though. He has been actively working and allegedly pushing useful features, engaging with distro maintainers, etc
Until he decided to push the backdoor.

[Abdelrhman Shawky @shawkyz1]

Both maintainers Github accounts have been suspended along with the repos.
https://t.co/rpw6911kVm

[Abdelrhman Shawky @shawkyz1]

What I find to be interesting in the whole xz saga is that the *bad* maintainer worked in the project for almost 2 years and established credit before pushing the change with the backdoor.

[Abdelrhman Shawky @shawkyz1]

The whole story is also interesting of how he became a maintainer, since the original maintainer mentioned that he didn't have time, I also read somewhere that he was burnt out.

[Rob Mensching @robmen]

Lots of analysis of the xz/liblzma vulnerability. Most skip over the first step of the attack:

0. The original maintainer burns out, and only the attacker offers to help (so the attacker inherits the trust of the project built by the maintainer).

Read their words👇🏻 1/

[Abdelrhman Shawky @shawkyz1]

SBOM SBOM You’re a SBOM

[ThePrimeagen @ThePrimeagen]

golang greatest mistake is normalization of single letter variables

[Abdelrhman Shawky @shawkyz1]

@rgbdev @Bashmohandes Kubemonkey?

https://t.co/0p5afUtXNZ

[ThePrimeagen @ThePrimeagen]

there is no escape from software complexity, you just get to choose the place where it happens

anyone that tells you otherwise is trying to sell you something

[Mitchell Hashimoto @mitchellh]

Breaking news: computers can be fast when you aren't forty two billion abstraction layers above the CPU instructions.

[Abdelrhman Shawky @shawkyz1]

Also your code ultimately shouldn’t know about the different stages you have. It just expects some value for some env var

[Abdelrhman Shawky @shawkyz1]

Imo this could be chaotic in the long run

Just use the Options pattern and inject the values through env vars.
You may use appsettings as a fallback for local dev stuff.

[Karen Payne MVP @KarenPayneMVP]

Setup for EF Core configuration for development, staging and production.