Timicoding

if after the bun rust rewrite and 1M code merge in a few days you still think that software engineering hasn’t changed massively idk what to tell you

So all the tech bros in this Lagos can’t build an app to find houses and beat all these agent crap? Nawa o

You need an element of luck and the right type of greed to be a millionaire. Intelligence is not enough in making money.

when i was younger, i was very insecure. i did this kind of thing too. over time you learn that it is critical to be truthful and not misleading about every single thing you do. i had to learn this lesson the hard way, but boy, have i internalized it. UNDERSELL yourself.

OOP and Databases don’t mix well. When you force them to mix, you get a lipstick. Also know as ORMs.

• get a loan of 25M • buy a land of 10M • build it with 15M • sell it for 50M • repeat the cycle be intelligent.

Am I the only developer without a portfolio website?

What was your first UTME score?

What exactly am I going to expect from someone who got into poly with 100/400 ?

One day I'll tell my story about startup funding in Africa. It's just a syndicate, and it's sad. Sad because those who had the opportunity to receive international funding close the doors on others either by recycling opportunities amongst themselves and getting re-funded by proxy, or triggering investor apathy on competing startups. I'm starting to think it's this melanin 😭

As a Principal Backend Engineer with over 12 years of experience, I can tell you quite certainly that if you're still getting rejections in system design interviews after good efforts, I think your fundamentals are not strong... Dedicate 2-3 months to mastering these design fundamentals, then practice designing a few systems(and do plenty of mock interviews). Scaling & Architecture ↬ CDN ↬ Caching ↬ Sharding ↬ Queueing ↬ Replication ↬ Partitioning ↬ API Gateway ↬ Rate Limiting ↬ CAP Theorem ↬ Microservices ↬ Load Balancing ↬ Fault Tolerance ↬ Database Scaling ↬ Service Discovery ↬ Consistency Models ↬ Eventual Consistency ↬ Distributed Transactions ↬ Monolith vs Microservices ↬ Leader Election Databases & Storage ↬ Leader-Follower Replication ↬ WAL (Write Ahead Log) ↬ Asynchronous Processing ↬ Transaction Isolation ↬ Read/Write Patterns ↬ Consistent Hashing ↬ Redis/Memcached ↬ Backup & Restore ↬ Hot/Cold Storage ↬ Data Partitioning ↬ Object Storage ↬ SQL vs NoSQL ↬ Data Retention ↬ Data Modeling ↬ OLAP vs OLTP ↬ ACID & BASE ↬ Bloom Filters ↬ File Systems ↬ S3 Basics ↬ B+ Trees ↬ Indexing Communication & APIs ↬ JWT ↬ CORS ↬ OAuth ↬ Throttling ↬ Serialization ↬ API Security ↬ Long Polling ↬ WebSockets ↬ API Gateway ↬ Idempotency ↬ Service Mesh ↬ Retry Patterns ↬ REST vs gRPC ↬ API Versioning ↬ Circuit Breaker ↬ API Rate Limits ↬ Fan-out/Fan-in ↬ Protocol Buffers ↬ Message Queues ↬ Dead Letter Queue Reliability & Observability ↬ Metrics ↬ Alerting ↬ Failover ↬ Logging ↬ Rollbacks ↬ Monitoring ↬ Heartbeats ↬ Retry Logic ↬ Autoscaling ↬ SLO/SLI/SLA ↬ Load Testing ↬ Error Budgets ↬ Health Checks ↬ Circuit Breaker ↬ Incident Response ↬ Chaos Engineering ↬ Distributed Tracing ↬ Canary Deployments ↬ Graceful Degradation ↬ Blue-Green Deployment

I ranked backend problems by pain level NULL POINTERS　　　　　　　　　　- 12% MEMORY LEAKS　　　　　　　　　　- 38% N+1 QUERIES　　　　　　　　　　　- 61% CASCADING FAILURES　　　　　　　- 84% DISTRIBUTED LOCKS　　　　　　　　- 93% RACE CONDITIONS　　　　　　　　　- 97% DEBUGGING PROD AT 3AM　　　　- 1000%