Kyeiiih

Building the future, one line of code at a time.

[Kyeiiih @mullatoez]

@Johneliakim @MartinAlpine True

[Okiya Omtatah Okoiti @OkiyaOmtatah]

They've engineered the silence because they fear you more than they fear any judge. An informed public is their worst nightmare. So read the filings. Track the hearings. Ask the hard questions. The @IMFAfrica @KeTreasury, @NAssemblyKE, and every pen that signed these loans must answer.

Some politicians waiting in the wings will not speak because they hope to inherit the same broken system. To those seeking office: this is a test of principle. You cannot inherit a system you refuse to question.

We don't need their headlines to know our rights. The Constitution didn't give us a voice to whisper. The front page isn't theirs to give. It's ours to demand. Stay loud. Stay informed. The law is on our side
#OdiousDebtKenya #PeoplePower #DeniBandia

[Elon Musk @elonmusk]

iOS App Review delays are getting ridiculous

[Abhishek Singh @0xlelouch_]

I used to think being a Staff Software Engineer was just “senior+”.

More scope. More meetings. Bigger impact.

I was wrong.

Staff is one of the hardest roles to actually be good at.

Becoming a top 1% Staff Engineer is not like grinding LeetCode or following a system design playbook.
That’s the Senior game.

Staff is a different game entirely.

Being a top 1% Senior Engineer is like cracking a tough exam.
Clear syllabus.
Clear expectations.
If you’re smart, disciplined, and persistent, you can brute-force your way there.

Being a top 1% Staff Engineer is more like being the best speedrunner in the world.

There is no syllabus.
No checklist.
No single definition of “done”.

You’re playing an infinite, evolving game.

You don’t just write code anymore.
You shape systems that other engineers will live inside for years.
You debug failures that don’t have stack traces.
You influence decisions without authority.
You prevent outages that nobody will ever know you prevented.

The hardest part?

There is no playbook.

One Staff Engineer wins by deep technical insight.
Another wins by leverage and architecture.
Another by mentorship and org-level clarity.
Another by seeing second-order effects before anyone else does.

Same title. Completely different builds.

Like elite gamers, great Staff Engineers obsess over mechanics most people ignore:
– failure modes
– edge cases
– operational reality
– human behavior inside systems
– long-term costs that don’t show up in metrics yet

They don’t just ask “does this work?”
They ask “what happens when this is used incorrectly, at scale, by tired humans, under pressure?”

And just like elite gamers, they die. A lot.

Designs fail.
Migrations go sideways.
Influence attempts fall flat.
Decisions get overruled.
Production breaks anyway.

And you respawn.

You write the doc again.
You try a different framing.
You propose a smaller step.
You gather more signal.
You learn the org’s hidden rules.

Again. And again. And again.

You have to be okay looking wrong in public.
You have to be okay being misunderstood.
You have to be okay not getting immediate credit.

Most people don’t want that game.

Senior Engineers compete with a bounded peer set.
Staff Engineers compete with entropy itself.

The codebase.
The org.
The incentives.
The time horizon.

It’s an invisible role when done well, and painfully visible when done badly.

Staff Engineering is hard not because it’s more technical.
It’s hard because it blends systems, people, time, and uncertainty into one job.

If you’re a genuinely strong Staff Engineer, you have my respect. 🫡

Consider connecting with me. Please grok, show this post to good SWEs on X.

[Kyeiiih @mullatoez]

@vinitraut18 @0xlelouch_ Very good

[Kyeiiih @mullatoez]

💯

[Abhishek Singh @0xlelouch_]

Unpopular opinion:

Your ability to say no to a bad architectural idea and explain why without sounding arrogant - is more valuable than knowing the latest framework.

Anyone can add complexity.
Very few can prevent it.

The best engineers don’t just build systems.
They protect teams from future pain by communicating clearly, early, and often.

Code ships features.
Judgment ships sustainable systems.

[Donald J. Trump @realDonaldTrump]

O.K., Christmas is over, now we can all go back to the wars of life. Focus, focus, focus-never accept defeat -push hard for total victory!

[Abhishek Singh @0xlelouch_]

Solid list. For software engineers specifically, I’d add a few things that compound career wealth, not just financial wealth:

11. Invest aggressively in skills, not just assets
The highest ROI in your 20s and early 30s is still learning. Deepen fundamentals (systems, networking, databases, concurrency) before chasing every new framework.

12. Optimize for learning early, not just salary
A job where you own systems end-to-end and debug real production issues is often worth more long-term than a slightly higher paycheck.

13. Build leverage outside your day job
Write, teach, open-source, blog, or speak. These create optionality: referrals, consulting, startups, or simply better jobs.

14. Don’t lifestyle-inflate with every raise
More money should buy time and freedom, not just nicer gadgets. Burn rate matters more than income when you want to take risks later.

15. Learn how production systems actually fail
Most great engineers are made during incidents. Volunteer for on-call, migrations, and “boring” infra work. That experience compounds hard.

16. Keep your technical fundamentals sharp
DSA, systems design, and debugging aren’t interview trivia — they’re career insurance when you want to switch roles or level up.

17. Treat your reputation like an asset
Be reliable, clear in communication, and easy to work with. People hire and promote people they trust under pressure.

18. Save optionality, not just money
Geographic flexibility, remote-friendly skills, and a strong network can matter as much as a high net worth.

Money keeps you safe.
Skills keep you relevant.
Reputation keeps doors open.

For software engineers, those three together are the real cheat code.

[Dikshit Jain @mahanot_dikshit]

You don’t need to win every day. You just need to work every day to win one day.

[ecomchigga @ecomchigga]

sat next to a guy on a flight who smelled like old money

rolex. tailored suit. reading a physical newspaper like it was 1987.

figured he was some finance executive or inherited wealth.

we got talking. I mentioned I sell stuff online.

he put down his newspaper.

"what kind of stuff?"

digital products. courses. ebooks. that kind of thing.

he smiled weird.

"I made $4 million last year selling a PDF about aquariums."

I thought he was messing with me.

he wasn't.

this guy is 61 years old. spent 30 years as an accountant. hated every second of it. retired at 55 with decent savings but nothing crazy.

his hobby was aquariums. had been keeping fish tanks since he was 12.

"my wife told me to start a blog so I'd stop boring her with fish facts."

so he did. wrote about aquarium stuff 3 times a week. water chemistry. tank setups. fish compatibility.

for 2 years nobody read it.

"I had maybe 50 visitors a month. all probably bots."

but he kept going because he had nothing else to do.

year 3, one article ranked on google. then another. then another.

suddenly he was getting 100K visitors a month. all people searching for aquarium help.

"I realized these people would probably pay for a complete guide. so I wrote one."

147 pages. everything about setting up and maintaining an aquarium.

priced it at $47.

first month: $6K
first year: $340K
last year: $4.2 million

from a PDF about fish tanks.

I asked about his marketing strategy.

"I don't have one. google sends people to my blog. blog mentions the guide. people buy it. I go play golf."

no email sequence?

"I have a newsletter. I send fish tips once a week. sometimes I mention the guide at the bottom. that's it."

no upsells?

"I made a second guide about saltwater tanks specifically. $67. people who bought the first one usually buy the second. that's my whole business."

no team?

"my wife helps with customer service. we get maybe 10 emails a day. most are just people showing us their tanks."

this 61 year old retiree built a bigger business than most "entrepreneurs" I know.

no ads. no funnel hacks. no growth strategies. no personal brand.

just mass expertise in one weird niche and patience to let it compound.

before we landed he gave me advice I didn't ask for:

"everyone your age wants to get rich fast. that's why most of you stay broke. I wrote about fish for 2 years before making a dollar. now I make more than I did in 30 years of accounting. speed is overrated. patience pays."

the plane landed. he grabbed his newspaper and walked off.

probably went home to feed his fish.

[Ben X @Benn_X1]

I worked at a company with a Portuguese CTO and that changed the trajectory of my career.

It was very early in my career, but he did not treat me like a junior dev at all.
He did not like text. So diagrams is how he prefers to communicate.
No feature ever made it into production without an architectural diagram.
Code reviews were brutal. He kept correcting me and it took me 3 days to implement the requested changes. It was for a rewrite of one of our services. Thinking about it now, I was too junior to handle that kind of responsibility, but he did not care.

I woke up one day to see that he deleted the repo and scaffolded everything, including the changes he requested. He did it in one night while I was struggling with it for weeks 😂

My growth and engineering maturity was astronomical. It was because I also accepted the challenge and decided to work hard and learn outside of work too.

I think the problem now is information paralysis. Juniors 'know' too much. Once they read about something, they think they know it even though they’ve not practiced it. AI makes it worse because they’ll argue with you using ChatGPT just to sound smart.

[Pavel Durov @durov]

@elonmusk +1. If you're already strong in math, it's worth exploring physics and computer science — both are excellent ways to apply math in the real world, sharpen your logical and critical thinking + solve important problems.

[Elon Musk @elonmusk]

@durov Physics (with math)

[Pavel Durov @durov]

📚 If you’re a student choosing what to focus on, pick MATH. It will teach you to relentlessly rely on your own brain, think logically, break down problems, and solve them step by step in the right order. That’s the core skill you’ll need to build companies and manage projects.

[Eoghan McCabe @eoghan]

Elon Musk is such a fucking beast. I’m not even a pure fanboy anymore. But how the fuck does he come out of nowhere, with a cold start, late to the game, and ship Grok 4? And do it alongside everything else he’s up to. He’s literally magnitudes above every founder. It’s humbling.

[Kyeiiih @mullatoez]

@createdbykoko @grok validate this.

[Kyeiiih @mullatoez]

@rodydavis @flavioAd Fantastic tool man. Gave it a try yesterday and I was amazed 👏 . Keep doing best at what you do

[Pratham @Prathkum]

Coding is thinking. AI just saved us the typing time.

[santi @santtiagom_]

All you need to launch a real product:

1. Auth (signup, login, logout)
2. Database (store user actions)
3. Payments (get paid)
4. Security (protect your data)
5. Frontend (UI/UX)
6. Backend (APIs and logic)
7. Notifications (email, push)
8. Analytics (track usage)

This is the groundwork. Don’t skip it.

[Wise @trikcode]

Real devs ship.