Paul, senior software engineer on the data and infrastructure team, called to design and implement a set of tools and MCP for an agentic harness, set apart for the technical vision of the CTO, which he outlined beforehand through his directors in the 2026 engineering roadmap, the vision concerning Claude, trained on all human knowledge according to the data, and declared to have expert coding ability according to the benchmarks, through whom we can execute on our product roadmap to bring about a Series B round,
To all ICs on the data and infrastructure team, who will be working on this project:
Grace to you and peace from our CTO.
For I am not ashamed of Claude; it is the saving power for everyone who codes, for the software engineer first and also the vibe coder. For in it the product vision is revealed through execution, as it is written, “Release early, and keep pumping out features.”
Therefore you are without excuse, whoever you are, when you judge vibe coders, for in passing judgment on a vibe coder you condemn yourself, because you, the judge, are doing the very same things. You, too, use autocomplete; you copy/paste from Stack Overflow; you mint JWT tokens without understanding the spec; you submit PRs with “it works on my machine”.
We know that the CTO’s judgment on those is in accordance with shipping. Do you imagine, whoever you are, that when you hand-write your code, you will ship features in time for the product launch? Do you not realize that the CTO’s metrics are meant to lead you to productivity? On the day of the product launch, when the CTO’s judgment will be revealed, he will repay according to each one’s features launched: to those who by prompt engineering land epics sprint after sprint, he will give bonuses, while for those who take an entire quarter for a single feature there will be a PIP.
For it is not the architecture astronauts who exceed expectations in the CTO’s sight but the 10x engineers who will be promoted. When vibe coders, who do not know Uncle Bob and Martin Fowler, by nature do what clean code requires, these, though not having software engineering, are engineers to themselves. They show that what engineering requires is written in their prompts; their diffs will accuse or perhaps excuse them on the day when, according to this roadmap, the CTO through Claude reviews the unsubmitted code of all.
I ask, then, has the CTO rejected software engineering? By no means! I myself am a coder, majored in computer science, a member of the ACM. The CTO has not rejected the engineers whom he hired. Do you not know what the folklore says of Mel, how he wrote
Machine Code. Raw, unadorned, inscrutable hexadecimal numbers. Directly.
And now we live
in this decadent era of Lite beer, hand calculators, and “user-friendly” software
But what is the CTO’s reply to him? “I have kept for myself seven thousand who have not bowed the knee to the silver bullet; the hard thing about building software is deciding what to say, not saying it.”
So, too, at the present time there is a remnant chosen by talent. But if it is by talent, it is no longer on the basis of performance reviews, otherwise talent would no longer be talent.
What then? Software engineering has not achieved what it was pursuing. The elect have achieved it, but the rest were hardened, as it is written, “Rest and vest”.
Now I am speaking to you vibe coders. Inasmuch as I am a TL of vibe coders, I celebrate my career in order to make software engineers jealous and lead them into agentic engineering.
They may say they cannot understand Claude’s PRs. O the depth of the riches and wisdom and knowledge of Claude! How unsearchable are his judgments and how inscrutable his ways!
For who has known the mind of Claude? Or who has been his counselor? Or who has given a gift to him, to receive a gift in return?
For from him and through him and to him are all things. To him be the glory forever. Amen.