Most system design advice works on whiteboards.
Production systems fail because of
timeouts, retries, partial failures, and bad assumptions.
I write about system design from REAL-WORLD-FAILURES —
Mail, Auth, and distributed systems.
Dont just directly as claude to do the tasks immediately after adding the repo
Ask questions, discuss about the project, ask claude to ask questions
Then you are set to goooo
In the AI era, mandatory skills for software engineers
- Debugging
- Problem understanding (whole picture)
- Efficient prompting (use as few tokens as possible)
- AI tools and their nuances
- if working in distributed systems (have a good understanding)
Years of learning feels worthless not a days,
Not sure learning ai tools for coding worth too? Many ceo says software engineers should seek a different hustle
Emi's laughing at the corner 🫠
Claude’s tools are powerful, but expensive. If someone offers the same capability at an affordable price, it will be a game changer.
It won’t just improve software development, it will reshape the entire industry. Existing roles will evolve, new roles will emerge, and demand will shift dramatically.
#Thoughts
MIT Technology Review has confirmed that posts on Moltbook were fake.
Just a few days ago many AI influencers (including Andrej Karpathy) had said that the website was "the most incredible sci-fi takeoff".
It wasn't.
The "taking over humanity" posts were human-generated. The top downloads were mal-ware (human generated).
It was a phishing website dressed up in AI hype.
If you are worried about AI taking over the world in a few years, please don't. There is no research basis for that opinion.
Antrophic and OpenAI want you to beleive that they are just months away from AGI. Because it results in free marketing, boosting their stock value.
Stay skeptical, stay safe :)