Quotes About Software

Fundamentally, blockchains are software protocols that allow multiple parties to operate under shared assumptions and data without trusting each other. These data can be anything, such as location and destination information of items in a supply chain or account balances of a token. Updates are packaged into "blocks" and are "chained" together cryptographically to allow an audit of the prior history – hence the name.

hen you're writing software, you have to ask, "Are we saving babies here?" If you're writing software that is actually helping babies to survive, then you should take your software really seriously. But if you're just making a shopping cart, you should turn it down a notch and take a breather. - Scott Hanselman

Ask a programmer to review ten lines of code, he'll find ten issues. Ask him to do five hundred lines, and he'll say it looks good.

How in the hell do you support and secure something that's written in Microsoft Access? When

Maybe my group being outsourced wouldn't be the worst thing in the world. I've been in software development for virtually my entire career. I'm used to everyone demanding miracles, expecting the impossible, people changing requirements at the last minute, but, after living through this latest nightmare project, I wonder if it might be time for a change…

Ward Cunningham in 2003. He said, 'technical debt is what you feel the next time you want to make a change.

They also knew that until code is in production, no value is actually being generated, because it's merely WIP stuck in the system.

Without automated testing, continuous integration is the fastest way to get a big pile of junk that never compiles or runs correctly.

the architecture that our services operate within dictates how we test and deploy our code. This

Microsoft, still has a culture that if a developer ever has a choice between working on a feature or developer productivity, they should always choose developer productivity.

our competition is not the FAANGs—it's the other horses in our industry and tiny little software startups that are encroaching on our market.

Instead, code is only "done" when it has been fully tested and is operating in production as designed. (Note

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

a joke: "A QA engineer walks into a bar. Orders a beer. Orders zero beers. Orders 999,999,999 beers. Orders a lizard. Orders negative one beer. Orders a 'sfdeljknesv.

For Phoenix, it takes us three or four weeks for new developers to get builds running on their machine, because we've never assembled the complete list of the gazillion things you need installed in order for it to compile and run. But now all we have to do is check out the virtual machine that Brent and team built, and they're all ready to go.

what's the plural of 'developer'?" says Maxine. "A 'merge conflict.

if we all want our developers to be productive, they need to be able to perform builds on Day One.

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

Continuous Delivery.

If you don't find problems quickly, you end up finding them months later. By then, the problem is lost in all the other changes that every other developer made, so the link between cause and effect disappears without a trace.

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.

Code deployment lead time, code deployment frequency, and time to resolve problems are predictive of software delivery, operational performance, and organizational performance, and they correlate with burnout, employee engagement, and so much more.

a small number of reliable, automated tests are almost always preferable over a large number of manual or unreliable automated tests.

Creating software should be a collaborative and conversational endeavor—individuals need to interact with each other to create new knowledge and value for the customer.