Nutsua Bless

174 posts

Nutsua Bless banner
Nutsua Bless

Nutsua Bless

@africasengineer

I write what I think. I think about systems, tech & AI in Africa. Sometimes I’m right. Sometimes I learn. Africa needs engineers, I’m becoming one.

Beigetreten Nisan 2026
30 Folgt30 Follower
Nutsua Bless
Nutsua Bless@africasengineer·
@SumitM_X Same server does not mean same execution path.The most likely culprits are route specific middleware running before CORS headers are applied on /api/orders,or a typo in the route pattern that means the CORS middleware never matches it
English
0
0
1
1.8K
SumitM
SumitM@SumitM_X·
CORS works for /api/users but fails for /api/orders on the same server. Both hit the same backend code. Why?
English
12
2
62
20.7K
Nutsua Bless
Nutsua Bless@africasengineer·
Watched brilliant people build brilliant things and watch them die quietly. Not for lack of effort. The invisible infrastructure wasn’t there. Trust in institutions. Access to capital. Systems that reward merit. Ghana’s biggest is the absence of systems that let effort compound.
M.anifest@manifestive

What’s the biggest problem in Ghana

English
0
0
0
8
Nutsua Bless
Nutsua Bless@africasengineer·
@kwabenaboatman @TheDumbTechGuy The ambition stays. The resolution changes. What I have not figured out yet is how to know when you have reduced it far enough versus when you have reduced it so much you are solving a different problem entirely.
English
1
0
0
12
Nutsua Bless
Nutsua Bless@africasengineer·
@kwabenaboatman @TheDumbTechGuy At what point does thinking smaller stop being clarity and start becoming a ceiling on what you allow yourself to test? And when you strip an idea down to its smallest form and it still feels too big to touch what do you do next?
English
2
0
0
22
Nutsua Bless
Nutsua Bless@africasengineer·
Not every podcast deserves notes. @ryanlpeterman with Mike Stonebraker did. Mike is the engineer behind Postgres. If you have ever touched a database you have touched his work. Here is what I wrote down.
Nutsua Bless tweet mediaNutsua Bless tweet media
English
0
0
0
15
Nutsua Bless
Nutsua Bless@africasengineer·
@TheDumbTechGuy @grok Appreciate Grok for the assist. Have you ever come across any of these categories when debugging??
English
1
0
1
16
Nutsua Bless
Nutsua Bless@africasengineer·
@akshaymarch7 Engineers not threatened by AI built their identity on judgment and outcomes not on being the only one who could produce the output. When the output becomes cheap the judgment becomes everything. That transition is uncomfortable for anyone who never developed the judgment.
English
0
0
1
160
Akshay Saini
Akshay Saini@akshaymarch7·
The real reason many fear AI is because it removes the illusion of competence.
English
64
10
238
12.6K
Nutsua Bless
Nutsua Bless@africasengineer·
@EOEboh This user has no password in your system. Google owns their authentication. Detect they signed up via OAuth, tell them clearly, offer two paths. Continue with Google or set a password by verifying their email first. Never silently fail or send a reset email that leads nowhere
English
0
0
2
1.1K
Captain-EO 👨🏾‍💻
A user signed up with "Login with Google." They now want to reset their password. What do you do?
English
61
4
295
71.4K
Nutsua Bless
Nutsua Bless@africasengineer·
@javarevisited Git fetch downloads changes without touching your working branch.Git pull fetches and merges immediately.Senior devs prefer fetch because it lets you see what is coming before it arrives Inspect the diff,decide when to merge, avoid surprises.Pull is convenient.Fetch is deliberate
English
0
0
3
4K
Javarevisited
Javarevisited@javarevisited·
interviewer: What’s the difference between: git fetch vs git pull Why do senior devs prefer one over the other?
English
12
5
81
46.8K
Nutsua Bless
Nutsua Bless@africasengineer·
@_trish_xD Reading unfamiliar code quickly is more valuable than writing new code from scratch. Every senior role is mostly reading, understanding and modifying. The industry never says this out loud because it is harder to teach and impossible to monetize as a course.
English
0
0
0
34
trish
trish@_trish_xD·
I know it sounds obvious, but maybe the most underrated skill in backend work: reading code you didn't write. - You understand systems faster - Forces you to think about design - Builds intuition for what breaks - You write better code after
English
15
4
152
3.3K
Nutsua Bless
Nutsua Bless@africasengineer·
The engineer who says “I’ve never seen this before” and the one who says “I know exactly what this is” are looking at the same system. The difference is the second one knows there are only four categories of problems that exist. Everything else is just implementation detail.
Nutsua Bless@africasengineer

Most engineers debug symptoms.The best ones recognize the category of problem first.There are only 4 types of problems hiding in almost every system: Emergent Properties Propagation of Effects Incommensurate Scaling Trade-offs Master these 4, and you’ll never be blindsided again

English
0
0
0
63
Nutsua Bless
Nutsua Bless@africasengineer·
Somewhere between hello world and senior engineer there is a wall most developers never climb. It is not a new language. It is not a better laptop. It is CS fundamentals. The engineers on the other side of that wall are not smarter. They just did the work.
English
0
0
1
12
Nutsua Bless
Nutsua Bless@africasengineer·
@TheDumbTechGuy He no talk where he do for so say I go go do some. He Dey gatekeep things
English
1
0
1
12
Nutsua Bless
Nutsua Bless@africasengineer·
@kellabyte When a company controls both the incident and the language used to describe it you will never get an honest account of what happened. Data breach has legal consequences. Misconfiguration does not. The word choice was never about accuracy. It was always about cost.
English
0
0
1
121
Kelly Sommers
Kelly Sommers@kellabyte·
I love how they say public AI chat history including API keys is leaked but it’s not a data breach 😂 The mental gymnastics is embarrassing.
English
3
3
33
3.5K