You're 28, single, working in a bank on ₦450,000 a month.
A fintech in Lagos wants you, and lets you choose your package.
Option A: ₦650,000 a month in cash. No shares.
Option B: ₦450,000 a month, plus shares worth 0.2% of the company, earned over four years. Their last funding round valued the company at $20 million, which puts your 0.2% at about ₦54 million on paper.
Option A pays you ₦9.6 million more over those four years. Option B only pays off if the company survives and someone buys the shares.
Which one are you taking, and why?
Reflect. Refocus. Rebuild. 🎯
The 2027 Blueprint is a free virtual workshop for students, graduates & young professionals.
📅 Sat 23 Jan, 4pm WAT
Only 20 slots!
Register: https://t.co/LJFH7CHoHg
#2027Blueprint#Haus9Academy
Happy Wednesday!
Start your week with a little Laravel magic: a Fortune Cookie that delivers a random inspirational quote every time you visit. Using Laravel Collections, we can create this fun feature in just a few lines of code!
There’s a simple test I like when building software:
“Will I understand this code six months from now?”
Because sometimes, your most important reviewer is future you.
And future you has absolutely no patience for the nonsense you wrote today. 😂
@stanlee0nX We'd get further if we stopped searching for signs of "vibecoding" and instead, looked at skill, alignment and simplicity.
AI didn't invent beautiful designs. It learned it from humans. And just because I used AI to simplify my coding doesn't mean I can't code.
Starting something takes courage.
Staying consistent takes discipline.
Knowing when to change direction takes judgment.
They’re completely different challenges, and getting good at one doesn’t automatically make you good at the others. But start, my friend.
Early this year bragging almost cost me a 450k client.
I bragged I had gotten a client from cold DM I did on LinkedIn. I posted it on Facebook.
Everything like this. 😂
Even after blurring some details.
I didn't know people could still scan possible screenshot and find the business.
They messaged my client and offered them a lower price.
My client checked my timeline on LinkedIn and Facebook to see where they discovered her from.
She saw that I posted it.
She sent me an email with screenshots because that's where we communicate. That was how she told me to kindly bring that post down.
Fear entered my body.
I brought it down quickly. If you follow me on Facebook, this happened in February, you might have seen the post. I collected free congratulations but deep down I was about to lose my contract with that woman.
I stopped posting to brag.
These days I don't prove to anyone that I tried something and it came out well.
I will do the work.
Get paid for it.
And live my best life. No be una go put me for talk.
Recently, spurred by some internal validation, I decided to take another hard look at what I was building with @Maelishq
One thing I kept coming back to was how features can sometimes take away from the viability and usability of a product.
Most times, when you keep adding features to a product, confusion grows with it. Users start spending more time figuring out what they should use than actually using the product. You end up giving them more choices, but not necessarily making their work easier.
So I decided to streamline Maelis.
By streamlining, I mean deliberately eliminating some things, reshuffling where certain features live, changing how they are used, and in some cases replacing them with simpler alternatives.
That meant destroying some of the things I had already built.
And honestly, that is one of the harder parts of building a product. You can spend days or weeks building something, get attached to it, and then realize that keeping it simply because you built it is actually hurting the product.
Some features had to go. Others had to be simplified. Some had to move completely.
The goal wasn't to have fewer features just for the sake of having fewer features. The goal was to make the things that matter most obvious, accessible, and useful.
Sometimes building better means adding.
Sometimes it means rearranging.
And sometimes, it means having the discipline to delete something you worked very hard to build.
I wish I actually knew this when I was starting out.
Your skill has a business model.
You heard me.
When you learn something valuable, there is an entire business ecosystem sitting around that skill that you also need to understand.
Who pays for it?
What are they paying for exactly?
How do people in that industry find clients?
How are projects priced?
What do the people making serious money in that space actually sell?
For years, I thought getting better at the skill was the main thing. So I kept learning, building, practising and trying to become technically better.
That part matters, obviously.
But eventually you realise that being good at something and knowing how to make money from it are two different skills.
Take programming.
You can spend years learning Laravel, React, Python, databases, cloud infrastructure and everything else, but none of that automatically teaches you how to find a company that needs your expertise, understand what problem they have, package a solution, price it properly and close the deal.
That's another skillset.
And you can learn it.
The same thing applies to almost everything.
If you learn photography, study the photography business.
If you learn writing, study publishing, content businesses and the different ways writers get paid.
If you learn design, study how designers get clients and how design agencies make money.
If you learn marketing, study the businesses that buy marketing and what they actually measure when deciding whether to keep paying.
Once you understand this, your skill starts looking different.
You stop seeing it as something you simply know how to do and start seeing the different problems it can solve, the people who have those problems and the different ways you can build a business around solving them.
I really wish someone had told me this when I was starting out.
Learn the skill.
Then go learn the business of the skill.
That's where you start milking what you've learned.
Your Product Can Be Too Flexible
The more ways you allow people to configure a product, the harder it can become to understand.
Flexibility feels like a feature, but every option adds another decision for the user and another rule for the system.
Sometimes the best product decision is simply deciding how something should work and making that behaviour really good.