Quotes About Code

When we have long deployment lead times, heroics are required at almost every stage of the value stream. We may discover that nothing works at the end of the project when we merge all the development team's changes together, resulting in code that no longer builds correctly or passes any of our tests. Fixing each problem requires days or weeks of investigation to determine who broke the code and how it can be fixed, and still results in poor customer outcomes.

The latter pattern is what has become known as immutable infrastructure, where manual changes to the production environment are no longer allowed—the only way production changes can be made is to put the changes into version control and re-create the code and environments from scratch. By doing this, no variance is able to creep into production.

technical debt' is what creates hardship, toil, and reduces the agility of our software engineers,

developers should be able to understand and update the code of a service without knowing anything about the internals of its peer services. Services

But in reality, when developers work, they're usually staring at the screen, deep in concentration, trying to understand what the code does so they can safely and surgically change it without breaking something else as an unintended side-effect, especially if they're working on something mission-critical

Without automated testing, the more code we write, the more money it takes for us to test.

In tightly coupled and complected systems, it's nearly impossible to change anything, because you can't just change one area of the code, you must change one hundred, or even a thousand, areas of the code. And even the smallest changes can cause wildly unpredictable effects in distant parts of the system, maybe in something you've never even heard of.

a continuous integration server that is doing code builds and automated tests on Data Hub for every check-in,

Locality in our code is what keeps systems loosely coupled, enabling us to deliver features faster.

you pay down technical debt as a part of daily work. It's a magnificent example of the First Ideal of Locality and Simplicity in our code and organizations.

I could wave this magic wand, I would change this step. Instead of getting source code or compiled code from Dev through source control, I want packaged code that's ready to be deployed.

In the DevOps ideal, developers receive fast, constant feedback on their work, which enables them to quickly and independently implement, integrate, and validate their code, and have the code deployed into the production environment (either

We cannot achieve deployments on demand if each of our production code deployments take weeks or months to perform (i.e., each deployment requires 1,300 manual, error-prone steps involving up to three hundred engineers). The countermeasure is to automate our deployments as much as possible, with the goal of being completely automated so they can be done self-service by any developer.

Taken from last speech at West Point Academy 1962: The Highest Moral Law: THE CODE - DUTY/HONOR/COUNTRY.....THERE IS NO SUBSTITUTE FOR VICTORY.

He was of knyghthod and of fredom flour.

They may be surprised to find how tough a warrior code the chivalry of medieval times was and how much it valued sheer prowess.

In our universe, we measure time with clocks, and computers have a "clock speed," but the clocks that govern the digital universe are very different from the clocks that govern ours. In the digital universe, clocks exist to synchronize the translation between bits that are stored in memory (as structures in space) and bits that are communicated by code (as sequences in time). They are clocks more in the sense of regulating escapement than in the sense of measuring time.

The fundamental, indivisible unit of information is the bit. The fundamental, indivisible unit of digital computation is the transformation of a bit between its two possible forms of existence: as structure (memory) or as sequence (code). This is what a Turing Machine does when reading a mark (or the absence of a mark) on a square of tape, changing its state of mind accordingly, and making (or erasing) a mark somewhere else.

Life evolved, so far, by making use of the viral cloud as a source of backup copies and a way to rapidly exchange genetic code. Life may be better adapted to the digital universe than we think.

There are two kinds of creation myths: those where life arises out of the mud, and those where life falls from the sky. In this creation myth, computers arose from the mud, and code fell from the sky.

Bits that are embodied as structure (varying in space, invariant across time) we perceive as memory, and bits that are embodied as sequence (varying in time, invariant across space) we perceive as code. Gates are the intersections where bits span both worlds at the moments of transition from one instant to the next.

I ordered four eggs and my new friend ordered some doughnuts. We both stayed away from sausage. Unless you knew the restaurant well and trusted the cook, ordering ground meat was a bad idea, because for some places "beef" was a code for rat meat. The

Until a few months ago we had a code of honor, and even the worst ruffians behaved with decency. You could leave your gold in a tent with no guard and no one would touch it, but now all that has changed. The law of the jungle rules, the only ideology is greed. Don't let yourself be parted from your weapons, and always travel in pairs or groups, because this is a land of thieves.

In jail, you just zone out, so that's the thing. That's like a cheat code.