Hey {{first name | there}}. Somewhere past midnight last weekend, I got to thinking about how much software is changing. I feel like I have said this a million times in the last quarter, but it is.
Someone with little or no technical background can go from nothing to an app in a few hours.
That does beg the question. If everyone can code now, what would you build?
In today's technical notes:
WTH is gang scheduling
Why partial placement is the actual bill
Why I am willing to try it
🧠TOGETHER WITH EVERYTHINGDEVOPS
Your resume says you know Terraform, Kubernetes, AWS, and GitHub Actions.
But what have you actually built with them?
In this video, we go through five Cloud and DevOps projects you can build for your resume, including a Terraform infrastructure project, a multi-tier Kubernetes app, a CI/CD pipeline, a homelab, and an AI-assisted incident agent.
But the projects are only half of it. We also get into how to document your work and talk about the decisions you made.
If you're building projects for your next Cloud or DevOps role, this is a good place to start.
Subscribe: @EverythingDevOpsHQ for deeper dives on agents, Kubernetes, MLOps, and AI infrastructure.
📰Technical notes: I was up because of a side project
As engineers, we sometimes unplug by working on something that may or may not be related to the day job. For me, that is hardware these days, and shockingly, the models are not bad if you are new to it.
That is the part that kept me up. If a model can walk me through hardware I do not know, then the person who has vibed seven websites is not a hypothetical. They have something they can show.
Which leaves two questions.
Can they pass themselves off as an engineer?
What does it say about execution if a vibecoded app is doing better numbers than my perfectly engineered microservice?
I can answer the first one without much trouble. A weekend of generated sites is not the same as owning a system that has to stay up. The second one is harder.
So the ideas guy was right?
In 2026, the ideas guy probably cannot believe his luck. He can finally work on the app he has been describing since 2016.
For a long time, the joke was that ideas were cheap and execution was the job. Execution, in that joke, meant you could sit down and make the thing exist. That part got cheaper. He did not become an engineer. He got past the part that used to keep the idea in a notes app.
The annoying follow-on is that making it exist was also how a lot of bad ideas died. A six-month build was a crude test. If you were not sure, you did not start. That test is gone, which is why I have three tabs open instead of a conclusion.
🌍IN THE ECOSYSTEM
ETOOMANYTHINGS? Run Fewer Agents, Josh Bleecher Snyder on why starting another agent every time you get stuck is a way to hide the latency, and why the scarce thing is attention.
How to solve hard problems — Ope Onikute on getting people on board, putting the thing in their hands, and finding out the idea was wrong.
What to Build When Building Is Free, Vikas Malpani on the filter that disappeared. When building was expensive, cost did some of the judging. Now the judging is yours.
⏱️UNTIL NEXT TIME
Unlike the last issue, I would really like to hear this. Personal tooling, hardware, a 3D project, open source, the app from 2016. Reply, and I will feature a few of them next time.
Know an engineer who will find this helpful? Share this link with them
Jubril Oyetunji
CTO, EverythingDevOps