Quotes About Technology

If I had known that I could be a programmer and a teacher at the same time, I think I would have aimed for this career much sooner because this is my sweet spot: being able to do something that's creative and logical like programming, but also focusing on the documentation, the teaching, and the speaking - Trisha Gee

She went in the pool," she finished for me. "Ohmigod. She was killed while tweeting. It was Twittercide!

Replies began arriving seconds after he pressed send, and soon every single one of the warriors (besides William) had agreed to come home. Take me out of your address book, William

Ninety-eight percent of American homes have TV sets, which means the people in the other 2% have to generate their own sex and violence.

We found out the Gemini spacesuit was, well, oxygen was flowing to keep me cool as well as to breathe, and it wasn't good enough. My visor got fogged.

I know in another decade or two I'm going to have to get used to the idea of reading without paper in my hands, but I'm going to be making that trip kicking and screaming. Maybe that sounds stubborn, but my relationship with the printed word is the longest one I've ever had and I'm not ready to quit on it yet.

Once again, I can provide ample scientific—" "Yes, I know. But understand that at least twenty percent of the people reporting to me, think wireless internet access is witchcraft.

Progress in science and technology is real, but it builds on past truths without rejecting them. Computers don't have to be re-invented in order to keep getting better; innovations expand what they already do. Knowledge accumulates, so it can increase. Scientists and engineers know this, but artists, authors, and philosophers keep trying to start over from ground zero in the humanities. Thus, they don't really progress—they become primitive.

In studying the Bible as a young man, I found intimations of the idea that forms of media favor particular kinds of content and therefore are capable of taking command of a culture.

Something seems wrong in a world where half the e-mail messages sent are urgent. Can everything really be that important?

Left unchecked, technical debt will ensure that the only work that gets done is unplanned work!

The only thing more dangerous than a developer is a developer conspiring with Security.

It's difficult to overstate the enormity of this problem—it affects every organization, independent of the industry we operate in, the size of our organization, whether we are profit or non-profit. Now more than ever, how technology work is managed and performed predicts whether our organizations will win in the marketplace, or even survive.

Bill Baker, a distinguished engineer at Microsoft, quipped that we used to treat servers like pets: "You name them and when they get sick, you nurse them back to health. [Now] servers are [treated] like cattle. You number them and when they get sick, you shoot them.

In ten years, I'm certain every COO worth their salt will have come from IT. Any COO who doesn't intimately understand the IT systems that actually run the business is just an empty suit, relying on someone else to do their job.

So much about DevOps is counter intuitive, contrary to common practice, and even controversial. If production deployments are problematic, how on earth can deploying more frequently be a good idea? How can reducing the number of controls actually increase the security of our applications and environments? And can technology really learn anything from manufacturing?

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

Are we playing to win and to establish the technical supremacy we need to keep up with what the business needs, or do we just keep limping along, shackled to things built decades ago, and tell our business leadership to throw in the towel and stop having good ideas?

You've helped me see that IT is not merely a department. Instead, it's pervasive, like electricity. It's a skill, like being able to read or do math.

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

Show me a developer who isn't crashing production systems, and I'll show you one who can't fog a mirror. Or more likely, is on vacation.

When Dev teams had problems with testing or deployment, they needed more than just technology or environments. What they also needed was help and coaching. At first, we embedded Ops engineers and architects into each of the Dev teams, but there simply weren't enough Ops engineers to cover that many teams. We were able to help more teams with what we called an Ops liaison model and with fewer people.

It is virtually impossible to make any business decision that doesn't result in at least one IT change.

In the technology value stream, we optimize for downstream work centers by designing for operations, where operational non-functional requirements (e.g., architecture, performance, stability, testability, configurability, and security) are prioritized as highly as user features.