One of the purpose of writing is to persist consciousness.
It is one way to transcend time and space.
It can take you into the past, pin you in the present, or fly you into the future.
Write for yourself and persist your consciousness.
I usually like this part, it is useful in finding out if the working environment will be a good fit.
I asked the CTO the following questions:
1. Are engineers empowered to work or managed ?
2. In the team, how will I determine the value I offer in realtime?
Dear Dev, no matter the urgency ensure you calm down and do a good job.
You have the right to always slow down or push back.
When the beans is cooked, you will be the one to eat it.
I prefer Cache-Aside with Write-Invalidate
This is because the system I currently manage is dependent on faster read for certain data, each write is new and unique. The transitive data that each write depends on are what is cached.
(I take care of Thundering Herd)
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)
Today is Day 4: Cache Invalidation.
Caching data is easy. Knowing when to throw it away is where every team I've worked with has gotten burned at some point.
Write-through. Write-behind. Write-around. TTL vs event-driven. Breaking down each one today.
Follow along if you're preparing for system design interviews. Thread below 👇
(90+ system design fundamentals in one guide → https://t.co/Ots2nRhO5f)
Does “Compensate on timeout” refer to immediate refund ?
Will the business not be losing money if they treat timeouts as a refund trigger ?
Will like to know more about that part in this system (a lot of things about systems boils down to agreed constraints)
I once reviewed a code of engineers working with one of the outsourcing companies in Nigeria.
On a Banking Back-End, They checked the balance, and then they credited the receiver before coming back to debit.
If your Payment App is not designed like this, you are wrong. 👌
The Work Ahead:
There is a lot ahead regarding stablecoin usage for settlement in cross border trading (payments)
Things like non-dollarised stablecoins, settlement guarantors, treasuries not tied to stablecoin issuers, compliance stamping, FX liquidity, etc
Interesting 🪙
A reliable and compliant payment infrastructure is needed to power Intra Africa trade.
Onafriq has that rail.
Onafriq Intra Africa Payments API makes movement of money within Africa easy and fast.
https://t.co/arFVU35Ce0
A reliable and compliant payment infrastructure is needed to power Intra Africa trade.
Onafriq has that rail.
Onafriq Intra Africa Payments API makes movement of money within Africa easy and fast.
https://t.co/arFVU35Ce0
Why Stablecoin is Adopted in Remittance:
Stablecoin is enjoying a good ride with remittances because of the customer type.
For trading, compliance is harder to navigate and that made or is making adoption slower.
We need more payments from intra-africa trading.
Why Stablecoin is Adopted in Remittance:
Stablecoin is enjoying a good ride with remittances because of the customer type.
For trading, compliance is harder to navigate and that made or is making adoption slower.
We need more payments from intra-africa trading.
Cross Border Payments Thinking:
The thinking behind building cross border payments for trading is different from the one behind building for remittances.
In Remittance, you think of your customer as an individual.
For trading, your default customer is a business
Cross Border Payments Thinking:
The thinking behind building cross border payments for trading is different from the one behind building for remittances.
In Remittance, you think of your customer as an individual.
For trading, your default customer is a business
@iam_azeezadio "..and they all think he has become eloquent in old age"
Dad is surprising them with commodified intelligence.
Hold something
The cure to motion sickness is in holding on to something.
That thing could be taste, community, context development and refinement, etc
I’m using LLMs for:
1. Architecture Review and Evaluation
2. Code Scanning for Vulnerabilities
3. Explicit Code Review
4. Refactoring where necessary
5. Code Generation when I’m lazy or for straight to the point feature
6. Research
Arthur Schopenhauer in Authorship and Style:
As soon as this is perceived, the book should be thrown away, for time is precious. As a matter of fact, the author is cheating the reader as soon as he writes for the sake of filling up paper ….
1/ We are sharing additional details regarding our investigation into unauthorized access to GitHub's internal repositories.
Yesterday we detected and contained a compromise of an employee device involving a poisoned VS Code extension. We removed the malicious extension version, isolated the endpoint, and began incident response immediately.
A lot of people continue to pick node because it is accessible and can be used for whatever they’re trying to do.
The community, the tooling, etc.
When starting, performance issue is rarely related to language (except in strict environment)
you people are beginning to see the light.
no reason to be writing backend applications in nodejs and python when you have go in 2026.
go is superior in every way.
speed, dx, efficiency, simpler (than ts. no hidden quirks), concurrency and tooling.