Uncle Bob Martin

A brief intro to Clean Code Second Edition a.co/d/h81TOYL

Our first cybercab ride. Fantastic!

New best on Level 30 · Red Crowd: 30,139 points! 🏆 Every orbit is a first. Play Orbit Slinger 👉 apps.apple.com/app/id6815441…

Level 40 · Grand Orrery: beat my best with 44,787 points ✨ A system no one has ever seen. Play Orbit Slinger 👉 apps.apple.com/app/id6815441…

Disengaging from syntax is not disengaging from engineering. I’m working on a significant project at the moment. It’s in a pre-production state so far. More than a prototype, less than ready for real users. I’ve been making multiple passes over the structure for each of the following concerns: Architecture, coverage, race & concurrency, security, API, etc. Each of these requires significant interrogation and review of verification procedures; but not review of the code. At base are the /ub-mode (GitHub.com/unclebob) rules that keep the agents disciplined as far as coding structure and tests are concerned. But above that it’s me making sure that all the bases are covered well enough to keep my client safe from stupid sloppy mistakes. I am the engineer. I am responsible. The agents are just my tools. They are power tools, to be sure. But power tools in the hands of novices result in missing fingers. So I am very careful.

Fascinating story of A. Q. Khan. youtu.be/0HIiKwuVH34?si=9831… via @YouTube

the Cybertruck is CANCELLED…and here’s why youtube.com/shorts/m2_ulkIgo… via @YouTube

Grab a Cybertruck while you still can.

Saturation Testing. I use crapper and mutator to ensure that every expression in the system is covered by tests. If an expression is changed, one or more tests will fail. This used to be impractical. We simply could not afford to create that many tests. We also could not afford to change so many tests when requirements changed. The burden was too high. Now it’s trivial. The agents, under the lash of crapper and mutator, will write those tests and make them pass. And when requirement changed, they’ll write the new tests and change the old tests. None of this proves that the system works. That’s up to humans to judge. Humans can do that with tools like gherkin, or they can use manual tests. What the saturation tests provide is Semantic Stability. When the requirements change, and code has to be added and changed, those tests ensure that those changes do not inadvertently break unrelated parts of the system.

I used to be a language lawyer. In the late 80s I _studied_ the ARM (Annotated Reference Manual for C++). I knew the language cold, inside and out. I could make it do backflips. I shipped a lot of code using it. A LOT. I’ve attacked other languages with a similar intensity and depth. Until recently, that was simply the only way to become adept at building software systems. I now consider the deep understanding of a language to be a supreme waste of time and effort. I don’t want to learn Rust, or Golang, or Typescript, or any of the thousands of other languages out there. I’ll leave that to my agents. What I need now is to understand the high level gestalt of the system. I want to see the systems and subsystems. I don’t need to inspect the cogs. If I truly need to understand a detail at the cog level, I’ll interrogate my agents. I’m not going to pretend to be a language expert anymore.

the tesla cybertruck is seriously underrated. youtube.com/shorts/xl9bgFNKN… via @YouTube

Personal record on Level 35 · Contraflow! 37,617 points 🚀 No two games are ever the same. Play Orbit Slinger 👉 apps.apple.com/app/id6815441…

If you understand code, you can spot-check most languages — even if you don’t know them. Mid and high level structure are pretty obvious in virtually all languages. Names are self-evident. The captain knows how the ship works at a high level. He does not know the torque rating of every bolt.

New best on Level 30 · Red Crowd: 31,455 points! 🏆 A system no one has ever seen. Play Orbit Slinger 👉 apps.apple.com/app/id6815441…

Musk lives in an airstream near the worksite. He walks the floor of the site at midnight. He inspects the ship like a captain preparing for battle. And that is how you manage agents. You must be as relentless, and efficient, as the captain of the ship, or Elon Musk.

Level 28 · Retrograde: beat my best with 20,705 points ✨ No two games are ever the same. Play Orbit Slinger 👉 apps.apple.com/app/id6815441…

Personal record on Level 11 · Little Ember! 16,909 points 🚀 A system no one has ever seen. Play Orbit Slinger 👉 apps.apple.com/app/id6815441…

… point taken.