dolch
177 posts


@PSG_Report He doesn't like PSG, and he doesn't like Real Madrid either... He just loves money, nothing more... He doesn't put in that much effort on the pitch.
English

🚨🎙️| Kylian Mbappe: “If i didn’t sign for Real Madrid, I would’ve stayed at PSG until the end of my career. I dreamt of playing for the club and I’m very happy I did.”
“I still watch PSG matches every day, I have friends on the team and they're playing really well right now. I have always said that it’s the biggest club in France and one of the best in the world.” @beinsports_FR

English

@Iampreshtush @softangrygirl That's sounds very niche how much do u make
English

@softangrygirl For career advancement and trust me it’s the best decision you can ever make for yourself.
Linguistics and AI are more connected than you think.
I did Bsc in linguistics and a masters in cybersecurity with a focus on computational linguistics. So I’m speaking from experience
English

Yesterday I had my first coding interview, at one of the big AI labs, after 4 years of being a founder.
It was a disaster.
The task? agents algorithm. something I work with literally every single day.
I forgot basic js syntax. blanked on how to delete an array element. panicked on recursion.
The solution was crystal clear in my head. I could see exactly how to write it. but my hands just... couldn't.
The knowledge is there. the muscle memory is gone.
3 years of vibe coding did this to me. I haven't written code manually since. I just read it, design systems, think in architectures.
Somewhere along the startup journey, I stopped being a coder. I became someone who just ships.
Am I alone in this?
Sitting there, embarrassed, I think that's actually the right direction.
We used to write code. now we read it. soon with agentic engineering, we won't even need to read it. we'll just architect.
English

@_shavashava_ Did u just nickname urself on a Twitter post that's cringe asf
English

ShavaShava 💃 is Learning — Day 5
Have you ever felt lonely
even inside a group that calls you a friend?
You’re there.
But not really included.
Plans happen without asking your opinion.
Decisions are made without considering you.
They think you’re “busy living life,”
so your absence feels convenient.
And slowly you realise
being surrounded isn’t the same
as being chosen.
English

@0xlelouch_ Top ten yap fests, keep ur posts shorter bro just get to the point goddamn
English

How to get better at system design (for juniors)
A pro tip: try explaining systems like a geek, forget your GF, become a nerd, you will become good soon, trust me.
Not kidding but here are my 10cents.
1. Learn the basics first: HTTP/HTTPS, DNS, TCP, TLS, latency, plus OS basics like threads, memory, context switching.
2. Get solid at databases: indexing, transactions, isolation levels, replication, and when SQL vs NoSQL makes sense.
3. Understand caching properly: cache-aside, TTL, eviction, cache invalidation, cache stampede, Redis basics, CDN basics.
4. Learn async systems: queues/streams, retries, backoff, idempotency, dedup, DLQ, scheduled jobs.
5. Practice small designs before big ones: URL shortener, rate limiter, notifications, comments, file upload + processing, leaderboard.
6. Always write APIs + data model: endpoints, request/response, tables/keys, hot partitions, retention, basic schema evolution.
7. Do capacity math every time: QPS, payload size, storage/day, bandwidth, cache hit ratio impact, peak vs average.
8. Learn reliability patterns: timeouts, circuit breakers, load shedding, backpressure, bulkheads, graceful degradation, multi-AZ basics.
9. Learn observability: logs, metrics, traces, SLO/SLA, alerting, dashboards, debugging slowdowns and timeouts.
10. Use one repeatable interview flow: requirements → APIs → data model → high-level diagram → bottlenecks → scaling → failures → observability → tradeoffs.
English

A Max protein bar with 10 g of protein
India has a lot of catching up to do
Anushka Singh@nush_1320
Are these protein bars genuinely healthy to be eaten daily ??
English

“Leonardo DiCaprio” is his best performance of all time and we didn’t know
Kyle Buchanan@kylebuchanan
Something has activated Leonardo DiCaprio during this commercial break
English

Spoke to a dev friend of mine and he says that he basically just designs now and claude handles the rest and no one in their right mind should learn to "code" its kind of like how coding in python or whatever is an abstraction of binary and now vibe coding is an abstraction of coding in python for example
English

@uncledoomer Didnt know trevor wallace had it like that back in high school
English

@typecraft_dev Nah I don't feel this way, but I take great pleasure when I code on my own instead of relying on AI, but ultimately vibe coding with some human supervision is the META
English

A lot of engineers start their career dreaming of becoming a Staff Engineer.
They imagine:
- designing systems end-to-end
- mentoring teams
- influencing architecture
- being the person leadership trusts
- operating at a strategic level
And in the beginning, they do the right things — they learn relentlessly, take ownership, debug hard problems, read RFCs, build internal tools, ship features nobody else wants to touch.
---
But then something subtle happens:
They get comfortable.
They become good enough at their current job:
- They know the systems well.
- They can deliver features quickly.
- Nothing feels intimidating anymore.
And that comfort becomes a trap.
Instead of pushing toward Staff-level skills, they:
- stop volunteering for ambiguous high-impact work
- avoid cross-team problems
- stick to their familiar stack
- stop writing design docs
- avoid failures that would have taught them
- wait for promotions instead of growing into them
The result?
Years go by, and they're still a Senior Engineer who could have been Staff — if only they hadn’t settled into the comfortable plateau.
This is the Staff Engineer quicksand:
You’re productive enough to be praised…
but not stretched enough to grow.
The way out?
Start acting like Staff long before the title:
- Own systems, not tasks.
- Write technical strategies, not just PRs.
- Fix cross-team bottlenecks.
- Mentor others intentionally.
- Become the person who solves the hard, messy, ambiguous problems.
- Build breadth across systems, not just depth.
- Document, communicate, and influence — not just code.
A Staff Engineer isn’t created by title;
they emerge from someone who refused to stay comfortable.
Comfort gives you stability.
Discomfort gives you seniority.
Consistent discomfort gives you Staff.
Justin Skycak@justinskycak
Lots of people begin their upskilling journey with the intent of pushing the status quo. Then they get lazy and use their skills to minimize the amount of work needed for a baseline comfortable life. This is a trap. You start out feeling like you found a way to hack the system. But then you get tired. Like, fatigued. You're tired *of* doing nothing yet fatigued *from* doing nothing. It's quicksand. If you fall in, you can waste years in there before someone or something pulls you out.
English


















