A software craftsman | info sec. enthusiast #AndelaALC17 #nodejs #go
somewhere safe😁
Joined January 2010
- Tweets50K
- Following1.4K
- Followers2.5K
- Likes951
namdi retweeted
‼️One hill I am ready to die on is …
You don’t need to bombard your hair with lots of hair products to get results.
Do this:
Get the right guide to know the issue and recommend the right way out.
I am here for you on this
✔️Hair/ Beard Products+Items
✔️Consultation Services
New month, new postal code for Nigerians. 😁
postcode.gov.ng
To confirm location no go hard like that again 😁
namdi retweeted
Your business should be ready for growth even before the growth comes.
Growth is exciting, but without the right systems and structures in place, it can quickly become overwhelming.
Set up your inventory. Organize your products. Keep your business finances separate. Make it easy for customers to discover, order and pay for what you sell.
Don’t wait until your business gets bigger before you start putting things in place.
Build the structure now. So when the growth comes, your business is ready for it.
#bizflexafrica
#bcommerce
#structure
#fyp
#viral
namdi retweeted
Did you know you can sell digital products on B-Commerce?
From ebooks and templates to guides, courses, and other digital products, you can put your products online and make it easier for customers to discover and buy from you.
Your business can sell beyond physical products. Start exploring what’s possible with B-Commerce.
#bizflexafrica
#bcommerce
#digitalproducts
#didyouknow
#nowyouknow
namdi retweeted
Interviewed a Senior Backend Engineer today.
Knew APIs, rate limiting, queues, retries — all of it.
Then I asked:
"Your Node.js service calls a third-party API.
It starts returning 429 Too Many Requests.
You are getting rate limited.
Your service crashes because it keeps retrying
immediately — hammering the same API.
Users are seeing errors.
You cannot remove the third-party API.
You cannot pay for a higher rate limit right now.
How do you fix this without changing the API?"
Silence.
Your turn:
Third-party API rate limiting you ❌
Immediate retries making it worse ❌
Users seeing errors ❌
Cannot change the API ❌
How do you handle third-party rate limits
gracefully in production? 👇
(This pattern is in every serious backend —
most junior devs have never implemented it)
namdi retweeted
I think the internet has accidentally made “software engineering” look like:
Frontend → API → Database → Cloud
Meanwhile, somebody is writing software that controls the ABS in your car.
Someone is writing code for a pacemaker.
Someone is optimizing software where being 5 milliseconds late actually matters.
Someone is writing firmware for the router carrying this post to you.
Someone is writing the software inside your washing machine.
And someone somewhere is probably debugging a fucking satellite 😭
Web development is HUGE, so naturally it dominates programming conversations online.
But sometimes I remember how much software exists outside browsers and phones and realize this field is ridiculously bigger than most of us interact with.
namdi retweeted
Senior Backend Interview Problems:
Redis goes down for 30 seconds.
Your application starts sending every request directly to the database.
How do you prevent the database from collapsing?
namdi retweeted
If I were to start Software Engineering all over again, knowing everything I know today, I would take a very different path.
I wouldn’t start by chasing frameworks.
I wouldn’t try to learn every programming language.
And I definitely wouldn’t spend years collecting certificates.
Here’s exactly what I’d do:
namdi retweeted
Please, and please, and please…
Always review the dependencies being installed within your company’s codebase.
Clearly review every dependency before adding it.
This is something that should never be taken lightly.
Imagine installing a package that was last published or updated 3 years ago, with just about 12 weekly downloads.
That should immediately raise questions.
Who maintains it?
Is it still actively supported?
Are there known security vulnerabilities?
Why does it have such low adoption?
Does the package actually need to be installed?
Are there more trusted alternatives?
And again, senior developers and engineering teams:
Please do extensive code reviews before merging things into production.
Don’t just review whether the code works.
Review what is being introduced into the codebase.
A dependency can become part of your application’s attack surface.
One careless installation can introduce security vulnerabilities, malicious code, abandoned software, or unnecessary technical debt into an entire production system.
Code review is not just about checking the code someone wrote.
It’s also about reviewing what they are bringing into your ecosystem.
Review the package.
Review the maintainer.
Review the download activity.
Review the update history.
Review the security status.
Review the necessity.
Please, be careful with dependencies.
It's 7 days already and keep getting same messages of the issues is being looked into.
If the fibre x thing is not working then refund my subscription. @MTNNG @MTN180 @NgComCommission
namdi retweeted
Tell a brother to tell a brother
I will only deliver a brother
that always treat me like a brother. ⚓️
namdi retweeted
To bury the hatchet, you must first remove it from your back.
It is painful, but necessary, if we are to move forward.
namdi retweeted
If you are living in Nigeria, the key thing is to understand what the company means by “authorized to work in the U.S.”
If the application says:
“Are you legally authorized to work in the United States?”
and you are in Nigeria with no U.S. work authorization, the truthful answer is No. U.S. employment authorization is about your legal ability to work in the United States, not simply whether you can do the work remotely from Nigeria.
