hello_(tanya's)world; π retweeted
Pro tip: If the LLM generates code that you cannot understand, it means you need to upskill. Use AI to explain what was generated and provide more resources to help you keep up with the model. Being able to review the code that AI generates will become a mandatory requirement for software engineers.
hello_(tanya's)world; π retweeted
read code. no matter what. accountability is still yours. optimizing for speed while risking correctness is stupidity.
The real danger isnβt too few connections.
Itβs too many.
At high utilization (>80%):
β’ wait times spike π
β’ context switching kills CPU
β’ DB throughput drops
This is where Kingmanβs insight matters:
Small load increase β huge latency jump.
hello_(tanya's)world; π retweeted
the essence of being a software engineer is simply not giving up when you're stuck
hello_(tanya's)world; π retweeted
As a backend developer in 2026, how many of these 10 terms do you understand?
1. Idempotency
2. Backpressure
3. Circuit Breaker
4. Eventual Consistency
5. Distributed Lock
6. Exactly-Once vs At-Least-Once Delivery
7. Cold Start
8. High Cardinality Metrics
9. Sharding vs Partitioning
10. P99 Latency
hello_(tanya's)world; π retweeted
It's sad that we promote and encourage complexity in the tech industry
I'd love to see more of a push towards simple solutions to problems
hello_(tanya's)world; π retweeted
The most underrated skill in development:
Reading code you didn't write.
joined a new company recently as a swe-2. Unlearning and relearning new workplace patterns currently
started @edwarddonner's llm course. week 1 looks fun so far
So put my creativity + vibe coding skills to use and started with this mini project.
The goal was to make it as simple as possible. βοΈ
Tools I used:
@Pinterest : Inspiration β¨
My notebook: Planning ποΈ
@canva : Designing the UI & choosing the fonts πͺ
Vo by @vercel: Vibe-coded some parts π©βπ»









