π Full-Stack Dev | Building production apps with React/TS/Next.js β’ Node/Nest β’ Python/Django
By day I ship clean, scalable web apps. By night I keep the rhythm on the drums πΆ
Open to new roles & collabs (Lagos or remote) β DMs open!
GitHub & LinkedIn in bio π
if you're using AI to avoid learning to code, you're renting a skill you don't own.
The tool gets switched off. Your knowledge never does.
Stop using AI as a crutch. Use it as a weapon.
Learn to code now.
Retweet if you're a dev. Save this if you're becoming one.
Most people get locked out and wait for help.
I got locked out of a live project today.
Session expired. No support. No way in.
I opened the codebase. Found credentials.json. Deleted it. Logged back in.
An end user panics. A developer adapts.
You should be a developer. π
The difference is skill, not tools
- AI makes you fast. Not capable.
- Developers find the way in.
- No prompt saves you when production breaks at 2am.
- If AI stops tomorrow, devs still ship.
- Every AI you depend on today was built by a developer. Never an end user.
Best career advice nobody gave me as a dev
Stop just building. Start building in public.
β Ship on GitHub AND talk about it
β Have an opinion, not just a CV
β Write about what you built
That's what gets you noticed.
Most devs write code that works.
The best write code the next person can actually read.
What separates them:
- Meaningful names over clever shortcuts
- Small functions that do one thing
- Comments that explain WHY, not what
Your code is a message. Write it like one.
Stop building for yourself.
Implement what's on paper, and youβll ship a ghost town.
Get a pilot user early.
Real feedback kills "dev ego" and builds a product people actually use. π
Biggest dev mistake: Following the spec instead of the user. Pilot tests > Paper plans.
Action: Let a user break your app today. Benefit: You build a solution, not just a set of features. π οΈ
Building a Flutter app?
Don't just say "it's almost done." Show the Widget tree or a screen recording.
Visual progress builds more trust with clients/non-devs than any status update.
What are you building today?
@frontend__fairy I bet if you didn't learn a tech skill before now, it would be hard for you to learn it now in this AI era @frontend__fairy. so flip the table around, there you have the answer.
Use const constructors and Consumer (or Select) wisely in Flutter.
Only rebuild the specific widget that changed, not the whole tree.
A massive CPU/Battery savings for your users. π
Stop guessing which Docker env is active.
Explicitly pass --env-file to every command in your Makefile.
This ennsures your command targets the right containers (Dev vs Prod) -zero accidents. π‘οΈ