Nightshift Dev

Code is cheap now. Builders aren't.

AI writes most of the code. It still can't tell you what's worth building, ship it without breaking things, or notice when it was the wrong call. That's the job now. I'll help you move into it, the way I did.

FE-24173 points

Add a sort dropdown to the orders table, as in the Figma

Assignee: you

  • Nobody sorts. They search for one order.
  • Agent builds search tonight, I review.
  • Monday: did support tickets drop?
Same ticket. Different job.

I'm Albert Nahas, a senior engineer at a European health-tech scale-up. Before that, Miro.

people used the web builder my team shipped in Dubai
15M
people used the web builder my team shipped in Dubai
of engineers coding with AI after I ran the rollout at work
90%
of engineers coding with AI after I ran the rollout at work
agents help me run a side product with paying customers
4
agents help me run a side product with paying customers
open-source tools I've built for Claude Code
7
open-source tools I've built for Claude Code

The job that's left

Tickets used to arrive with the answer already in them. Now an agent can close most of them before standup. These are the parts that stay yours.

  • Pick the problem

    Talk to users, read the numbers, decide what's worth a week. Most of the job is saying no.

  • Ship it with agents

    Claude Code does the typing. You set the rules: what it owns, what it can't touch, when it has to ask.

  • Keep it safe at 3am

    Hooks, budgets and a reviewer that only merges what's safe. Nothing breaks while you sleep.

  • Own the result

    Check whether it worked, then keep it or roll it back. Nobody can automate that part for you.

Your time, right now.

My agents work nights.

A normal night for one of them looks like this. It fixes something, gets a second agent to review it, merges it, and leaves the risky one for me with a note. I read the report over coffee. In the cohort you set up the same thing on your own repo.

One agent, one night
  1. 21:00ops-agent starts, reads CHARTER.md
  2. 21:02sweep: 3 open PRs, rebased on main
  3. 21:14hook blocked: git push --force origin main
  4. 21:15pushed to branch fix/stale-cache instead
  5. 22:40PR opened: fix stale cache on pricing page
  6. 22:43reviewer subagent: grade A, tests green
  7. 22:44merged, deploy green
  8. 01:10PR touches checkout: grade X, left for a human
  9. 03:30budget check: $1.84 of $5 spent
  10. 07:00morning report sent: 2 merged, 1 needs you

Two ways in

Early in your career? Start with The Future of Engineering. It's about becoming the person who decides what gets built. Already shipping and want agents doing more of it? Take Agent Ops.

Time card 0417

The Future of Engineering

For developers early in their career who would rather own a product than work through a ticket queue.

  1. 01Think in problems, not ticketsWk 1
  2. 02Pair with AI without handing over your judgmentWk 2
  3. 03Ship a real product end to endWk 3
  4. 04Talk to users and read the numbersWk 4
  5. 05Run your first agentWk 5
  6. 06Build a portfolio that proves itWk 6

Time card 0418

Agent Ops

For engineers who already ship and want Claude Code doing more of the work without breaking anything.

  1. 01Write the charter your agent obeysWk 1
  2. 02Guardrails with hooksWk 2
  3. 03Run headless on a scheduleWk 3
  4. 04Skills and subagents that earn their keepWk 4
  5. 05Evals and independent PR gradingWk 5
  6. 06Escalation and the kill switchWk 6
  7. 07Roll it out to a whole teamWk 7

Hi, I'm Albert

I wrote my first production code in Aleppo in 2013. Since then I've worked in Beirut, Dubai and Amsterdam. I led the team behind a web builder that reached 15 million people, built enterprise features at Miro, and I'm now a senior engineer at a European health-tech scale-up. There I ran the rollout that got 90% of our engineers coding with AI.

Somewhere in the last year my job changed. I write less code than ever and ship more than ever. On the side I built OpenWhen on my own. People write about 470 letters a day on it, and there have been 426 paid orders so far. Four Claude Code agents help me run it.

I started this because a lot of engineers I talk to can feel the floor moving and nobody is showing them where to step. Everything here is something I do every week. The tools are open source on GitHub.

Join the first cohort

A small group, live, working on your own code. You leave with an agent shipping in your repo and a much clearer idea of the job you're growing into. Teams can book it as a private workshop.

Which track?

One email when the first cohort opens. No drip sequence.