Mustapha Aminu

Backend engineer. Otaku. Arsenal fan. I build the parts of software users never think about, until they break. Here I'll share what I'm learning, what I'm building, and the mistakes I'm making along the way. Just getting started. Come along.

How cracked do you have to be at something (in tech specifically) to write 1,000 pages of real value about it? 90% of people couldn’t even fill 50 pages about their entire lives, let alone a slice of their knowledge. It honestly blows my mind. Big respect to tech authors.

@rxhit05 Infrastructure, tooling or a service for the next significant shift in tech, whatever that is ...

You get $100k and 6 months. What are you building? 1. AI startup 2. SaaS 3. Consumer app 4. Open-source project

@sattyyouneed We endangered species should stick together

In the age of Codex & Claude i still learn code manually

@uday_devops Thanks, I too hope so

@backendHashira Great hope you're in right place and connected with right people

Why are you on X? - Networking - Just scrolling - Finding clients - Building in public - Learning from others

@YashHustle_22 Antigravity, so ... VS Code

Where do you spend most of your coding hours these days? - Cursor - VS Code - Replit

@codevsdev Build and ship the 3 open source projects I am working, learn as much as possible along the way. Leverage that to land my first proper dev job

what's your next career milestone? 🚀 → Land my first developer job. → Get promoted to a senior role. → Master AI/ML and build real projects. → Launch my own startup/product. → Become financially independent through tech.

@system_monarch Another masterpiece, very well written

I've started a 25-day series on Scaling and Architecture. One topic per day. Day 1: Load Balancing Day 2: CDN Day 3: Caching (the 5 layers) Day 4: Cache Invalidation Day 5: Rate Limiting Day 6: API Gateway Today is Day 7: CAP Theorem. The most quoted and most misunderstood concept in distributed systems. Most people get it wrong in interviews. I'm going to explain it the way I wish someone explained it to me 10 years ago. Thread below 👇

@suryanox7 Not really, devs tend to favor the abstraction ORMs like Prisma and Drizzle provide.

Is writing SQL queries off the top of your head still a flex?🫠

@themishra4402 Postgres all day, everyday

AI can write SQL. You can keep only ONE database. Which one survives? • PostgreSQL • Supabase • MySQL • MongoDB

@vivoplt 2 years ago, I would have def said JavaScript. Right now, it might be English

If you had to learn only one programming language in 2026, what would you pick?

@Tech_girlll What should be built, the systems to power it and the methods to distribute it

Which is more valuable in 2026: Knowing how to code? Or knowing what should be built?

@Sherifdeenolat2 Opencode coding agent + Deepseek v4 lite == $0/mon. Do not ask me how much I make, my ROI is mathematically infinity regardless

So far, has AI actually helped you make more money, or has it mostly taken money from you?

@knowRowan Self-hosted betterAuth

Which authentication provider will you choose?

@Gamingtronium What wheel are you reinventing?

At this point the tokens are doing the thinking, not Claude 😭

If you made it this far, Congrats. This was a long one. Everything in this thread came from the Altexsoft YouTube playlist on software documentation. 12 videos covering the full stack, and I genuinely think it's a really nice resource for anyone building software. And if found any value in this thread, drop it here 👇. Follow for more threads on product, engineering, and building things that actually ship.

10/10 - When API Documentation IS The Product If you are building something other developers will consume programmatically, the documentation is the product experience. Full stop. There are 24 million developers in the world. They spend a huge chunk of their time figuring out how other peoples APIs work because the docs are either missing, outdated, or wrong. Companies like Stripe, Twilio, and HubSpot invest heavily in API docs for a reason. Good docs reduce support tickets, increase adoption, and create a feedback loop that improves the API itself.

"We'll document it later" is the most expensive lie in software development. Nobody ever documents it later. The project ships broken features, the team forgets why decisions were made, burning through tokens like the scorching US sun melting European players at the World Cup (no shade), and the next developer inherits a mess with no map. I went through the Alexsoft playlist so you don't have to make that mistake. 🧵