Building in public

I'm Stephen. I build web apps for a living and I'm learning cloud and DevOps right now. Nobody in my family did this. I picked it up from free tutorials and a lot of projects that never worked, and I post what I learn while I'm still learning it.

years writing code
0+
years writing code
products shipped
0
products shipped
certifications so far
0
certifications so far
azureci/cdcontainersinfrastructure as codestill learningbuilding in publiclinuxpipelines

The story

None of this was fast and none of it was given to me. That's the whole reason I think it's worth writing down.

  1. Before

    01 / 05

    Where I started

    I didn't grow up around tech. Nobody I knew worked in it, so there was no one to ask and no plan to follow. What I had was time and a connection to the internet. I decided that was enough to start with.

  2. Learning

    02 / 05

    Teaching myself

    Free tutorials. Broken projects. A lot of nights that ended with nothing working and no idea why. JavaScript first, then React, then everything that comes attached to it. It was slow enough to be embarrassing. I kept going.

  3. Working

    03 / 05

    Getting paid for it

    Self-taught turned into client work. React, Next.js, TypeScript, Supabase. A car marketplace, a work-experience platform, a site for a food business. Real users, real deadlines, real bugs at midnight. I learned more in six months of that than in the year before it.

  4. The turn

    04 / 05

    The half I kept avoiding

    I could build the thing. Deploying it, scaling it, keeping it up when traffic arrived, that part I handed off every single time. Once I noticed I was doing that, it started to bother me. I wanted the whole job.

  5. Now

    05 / 05

    Learning the other half

    Azure, pipelines, containers, infrastructure as code. I'm bad at most of it today and better at it than I was last month. I'm posting the whole thing publicly instead of waiting until I look like I know what I'm doing.

    Here today

If you're starting out

I know the feeling of reading a job post and quietly deciding it isn't meant for someone like you. It is. What's between you and those people is time, and nothing else.

I wasn't the smartest person learning this. I was just still there in month eighteen.

01

Start before you're ready

Waiting until you feel qualified costs you years. You get qualified by doing it badly first.

02

Post while you're still bad

It's uncomfortable and it works. People help you a lot faster when they can see exactly where you're stuck.

03

Show up on the boring days

Most people quit somewhere around month four. Staying is the whole trick.

04

Free is enough to start

Almost everything I know came from documentation, free videos and projects I broke. No money makes it slower. It doesn't make it impossible.

What I'm on now

I'm early in both of these and I'd rather say so. The work is real and so are the mistakes I post about.

01still learning

Azure

Learning the platform properly instead of clicking around a portal and hoping it holds.

  • Compute, storage, networking, identity
  • Provisioning with infrastructure as code
  • Regions, scaling and what things actually cost
02still learning

DevOps

Getting the distance from a commit to production short enough that shipping stops being an event.

  • CI/CD pipelines and release automation
  • Containers and environments that reproduce
  • Logging, monitoring, knowing when it breaks

Work

All of this came before the cloud work. Paying clients, live users, deadlines I didn't set.

Toyota Nigeria Preowned Cars2024

Lead developer

Toyota Nigeria Preowned Cars

A marketplace for certified pre-owned vehicles. Listings, search and filtering, inventory management and lead capture. I built most of it end to end.

  • Next.js
  • React
  • TypeScript
  • Supabase
View project
Future Inspired2024

Sole engineer

Future Inspired

A UK platform that connects students to work-experience placements. I was the only engineer on it, working next to a product manager at my agency.

  • Next.js
  • TypeScript
  • Supabase
  • Auth
View project
Amari's Kitchen2023

Design and build

Amari's Kitchen

Brand and portfolio site for a Nigerian food and catering business. Menu, gallery and enquiries, built for the phones nearly all of its traffic came from.

  • React
  • Next.js
  • Tailwind
View project

Posts

Short notes on X about whatever I broke or worked out that day. Something longer on LinkedIn every couple of weeks, once it actually makes sense to me.

Sample posts, live feed coming

Daily

Day 41 and resource groups finally clicked

Spent the morning breaking my own environment on purpose. Naming conventions aren't bureaucracy. They're the only thing standing between you and a graveyard of resources you're scared to delete.

Read on X
Daily

First pipeline that didn't need babysitting

Push to main, build, test, deploy. It took fourteen failed runs to get there. Posting every error I hit and what actually fixed it.

Read on X
Biweekly

Why I stopped calling myself a frontend developer

Owning the deploy changed how I write the app. Some notes on the gap between building software and running it, and why I went looking for that gap on purpose.

Read on LinkedIn
Daily

Learning this without a mentor

You don't need permission or a bootcamp fee. A free tier account and the patience to be confused for a few weeks will get you further than either. Here's the order I'd learn it in.

Read on X

Tools

Things I'm good at

9

Used these on paid work, under deadline.

  • React
  • Next.js
  • TypeScript
  • JavaScript
  • Tailwind CSS
  • Supabase
  • PostgreSQL
  • Node.js
  • Git

Things I'm bad at

8

Working on these now. Some of them still catch me out.

  • Azure
  • Docker
  • GitHub Actions
  • Azure DevOps
  • Terraform
  • Linux
  • CI/CD
  • Monitoring

Contact

Fill this in and it lands in my inbox. If you're learning this too and you're stuck on something, that's the message I most want to get.

I answer everything, though sometimes it takes a few days.