Quotes About Code

The grandeur of space, dig it. Zillions of stars, each one gets its own pixel." "Awesome." "Maybe, but it's code's all it is.

My belief is that 'recluse' is a code word generated by journalists... meaning, doesn't like to talk to reporters...

You can't trust code that you did not totally create yourself.

Actually this book is built on a rather fragile premise: that good code matters. I have seen too much ugly code make too much money to believe that quality of code is either necessary or sufficient for commercial success or widespread use.

The majority of the cost of software is incurred after the software has been first deployed. Thinking about my experience of modifying code, I see that I spend much more time reading the existing code than I do writing new code. If I want to make my code cheap, therefore, I should make it easy to read.

Sometimes I feel silly introducing methods "just" to satisfy an "aesthetic" urge like symmetry. Aesthetics go deeper than that. Aesthetics engage more of your brain than strictly linear logical thought. Once you have cultivated your sense of the aesthetics of code, the aesthetic impressions you receive of your code is valuable feedback about the quality of the code.

Don't make more versions of your source code. Rather than add more code bases, fix the underlying design problem that is preventing you from running from a single code base.

If you're happy slamming some code together that more or less works and you're happy never looking at the result again, TDD is not for you. TDD rests on a charmingly naïve geekoid assumption that if you write better code, you'll be more successful. TDD helps you to pay attention to the right issues at the right time so you can make your designs cleaner, you can refine your designs as you learn.

Used Pluggable Adaptor, which we promise not to use again for four months, minimum, because it makes code hard to statically analyze.

And where, on earth, dwell hope and truth? In childhood's uncorrupted heart; Alas! too soon to guileless youth The world doth its dark code impart!

Ante la burocracia somos todos extranjeros, (...) la burocracia es, en esencia (y en eso radica su utilidad), un código ajeno.

the crucial step in programming is not the actual act of mechanically typing commands into a computer, but instead crafting the underlying solution that is then translated into code.

Recall our XP case study, where Greg Woodward noted that a lot of developers dislike the extreme environment and end up leaving after a few weeks. The aspect that most distresses them? The transparency. You're either producing good code, or you're obviously not. Some are simply not comfortable with this blunt assessment of what they're actually accomplishing.

work on contributing a clever piece of computer code to an Open Source project.

Consider this quote from the coding prodigy Santiago Gonzalez describing his work to an interviewer: Beautiful code is short and concise, so if you were to give that code to another programmer they would say, "oh, that's well written code." It's much like as if you were writing a poem.

In Ethereum, there are two types of addresses: the externally owned account (EOA) and an address of a contract account. Transactions sent to an EOA can only transfer ETH.1 In Bitcoin, all addresses are EOA. In Ethereum, when data is sent to a contract account, the data are used to execute code in that contract. The transaction may or may not have an accompanying ETH payment for use by the contract.

There were other miscalculations. Bernstein should not have used the silent confirm-or-hang-up method with the Justice Department lawyer. The instructions were too complicated. (Indeed, they learned, the attorney had gotten the instructions backward and had meant to warn them off the story.) With Deep Throat, Woodward had placed too much faith in a code for confirmation, instead of accepting only a clear statement.

We all see the signals because there is a universal code of violence. You'll find some of you need to break that code in the following chapters, but most of it is in you.

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

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.

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

Right now, we focus mostly on having deployable code at the end of the project. I propose we change that requirement. At each three-week sprint interval, we not only need to have deployable code but also the exact environment that the code deploys into, and have that checked into version control, too.

Even high-profile product and feature releases become routine by using dark launch techniques. Long before the launch date, we put all the required code for the feature into production, invisible to everyone except internal employees and small cohorts of real users, allowing us to test and evolve the feature until it achieves the desired business goal.

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