Prebs Tamar

“The terrorists need all the money they’re getting from kidnapping, It’s not like they are living luxurious lives; The government is putting too much pressure on them so they need money to finance their war machines.” – Sheik Gumi

Kan please leave street akara and patronize THE AKARA LEKKI, it just 7 pieces for 22k 🔥 Very affordable my bro and healthy

The second in command of a global terrorist organisation was Nigerian?

This lady nearly ran mad because of Tinubu 😭😭 What kind of international embarrassment is this?

We have successfully issued SEIS Investor certificates and claim forms from HMRC to our early stage investors who can now claim 50% tax relief of their investment in MOmsi, from HMRC. If you’re based in the UK and would love to join the limited investment round, let’s talk.

As a Senior Backend Engineer trying to move towards Staff, I can tell you one thing clearly: At Senior level, knowing system design fundamentals is not enough anymore. You are expected to design a good system. At Staff level, you are expected to design the right system for the business, explain the tradeoffs, influence multiple teams, reduce long term operational pain, and make sure the system does not collapse when traffic, teams, and complexity grow. So if you are already good at system design but still feel stuck at Senior, spend the next 3-6 months building these Staff Engineer muscles. Architecture & Technical Strategy ↬ System boundaries ↬ Platform thinking ↬ Build vs buy decisions ↬ Monolith decomposition ↬ Multi-region architecture ↬ Migration strategies ↬ Backward compatibility ↬ API contracts ↬ Long-term maintainability ↬ Reducing operational complexity ↬ Designing for org structure ↬ Architecture decision records ↬ Technical roadmap planning ↬ Removing accidental complexity ↬ Identifying single points of failure ↬ Choosing boring technology ↬ Knowing when not to build ↬ Designing systems that teams can own Scalability & Distributed Systems ↬ Caching strategy ↬ Queueing strategy ↬ Partitioning ↬ Sharding ↬ Replication ↬ Leader election ↬ Rate limiting ↬ Load shedding ↬ Backpressure ↬ Fan-out/Fan-in ↬ Idempotency ↬ Retry storms ↬ Consistency models ↬ Eventual consistency ↬ Distributed transactions ↬ Data locality ↬ Hot partitions ↬ Graceful degradation ↬ Capacity planning ↬ Failure mode analysis Databases & Data Architecture ↬ Data modeling ↬ Indexing strategy ↬ Query patterns ↬ Read/write scaling ↬ OLTP vs OLAP ↬ CDC ↬ WAL ↬ Transaction isolation ↬ Schema evolution ↬ Data retention ↬ Backup and restore ↬ Archival strategy ↬ Hot/cold storage ↬ Multi-tenant data design ↬ Event sourcing ↬ CQRS ↬ Denormalization tradeoffs ↬ Data correctness ↬ Reprocessing pipelines ↬ Analytics vs product database separation Reliability & Operations ↬ SLO/SLI/SLA ↬ Error budgets ↬ Alert quality ↬ Incident response ↬ Postmortems ↬ Runbooks ↬ On-call pain reduction ↬ Canary deployments ↬ Rollbacks ↬ Feature flags ↬ Disaster recovery ↬ Load testing ↬ Chaos testing ↬ Health checks ↬ Circuit breakers ↬ Distributed tracing ↬ Metrics design ↬ Log quality ↬ Dependency failure handling ↬ Designing for recovery, not perfection Execution & Influence ↬ Writing design docs ↬ Getting alignment ↬ Mentoring seniors ↬ Reviewing architecture ↬ Asking better questions ↬ Challenging vague requirements ↬ Explaining tradeoffs simply ↬ Driving cross-team projects ↬ Creating technical standards ↬ Reducing duplicate systems ↬ Unblocking other teams ↬ Making hidden risks visible ↬ Communicating with product ↬ Saying no with reasoning ↬ Turning ambiguity into execution ↬ Making other engineers more effective The Senior to Staff jump is not just about “I can build complex systems.” It is: “I can help the org make better technical decisions, avoid expensive mistakes, and create systems that other engineers can safely build on top of.” That is the mindset shift imo.

"I don't want a relationship where we text each other; I don't have strength for that. I want a relationship where we satisfy ourselves s3xually and when I am leaving I have money in my pocket." - Lady says

I’m a learner myself and that’s why I would not shut down someone’s design decision until they have the chance to defend it. Open to extension, closed to modification has nothing to do with predicting future architecture prematurely and bearing the cost for it. For instance, you can have a service layer that makes it easy to swap out underlying implementation. That doesn’t mean setup kubernetes on day 1 so you can easily setup the api for that service and scale it. As for how it works, I don’t know much about but what he said is not new tech. Databases can have functions, triggers and procedures and very sophisticated ones too. So it’s possible to move most business logic there if you want. Everything is a trade off.

nigerian software engineers, be humble, keep an open mind, your opinions are not absolute and always assume that you’re not as good as you may think you are.