Quotes About Development

We are; therefore, we evolve.

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

It's rare that someone who knows the topic better than you will sit in your talk because they will go to other talks.... I wrote a book on Spring, just because I was learning it as I was writing it. - Matt Raible

The phrase in tech writing was "easy reading comes from hard writing." Easy consumption of an app comes from really hard work on the backend. - Tori Wieldt

How can we, supercivilized out of almost all real emotion, develop the potential charm of this first glimpse of a new personality ?

The gift of the teacher is to let go before the aspiring artist becomes locked within a closed system of instruction.

Evil isn't born, it's made. One thought and action at a time." I paused for effect. "Take a good look at what you've made.

The author relates that the word "OBSCENE" springs from the concept in Greek drama that certain actions would be performed outside the scene or off the stage. He clarifies that the Greeks did not shy away from shocking actions, but they knew that portraying them in the audience's view would drown out the emotional subtlety of the character development and ethical dilemmas.

No young believer should ever rise quickly in the ministry.

Improving daily work is even more important than doing daily work.

Practice creates habits, and habits create mastery of any process or skill.

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

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

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.

we're hearing more lately: something called "DevOps." Maybe everyone attending this party is a form of DevOps, but I suspect it's something much more than that. It's Product Management, Development, IT Operations, and even Information Security all working together and supporting one another.

You get what you design for. Chester, your peer in Development, is spending all his cycles on features, instead of stability, security, scalability, manageability, operability, continuity, and all those other beautiful 'itties.

There should be absolutely no way that the Dev and QA environments don't match the production environment.

What use is it having all these offshore developers building features if we aren't getting to market any faster? We

the Third Way focuses on creating a culture of continual learning and experimentation. These

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…

This kind of service-oriented architecture allows small teams to work on smaller and simpler units of development that each team can deploy independently, quickly, and safely. Shoup notes, "Organizations with these types of architectures, such as Google and Amazon, show how it can impact organizational structures, [creating] flexibility and scalability. These are both organizations with tens of thousands of developers, where small teams can still be incredibly productive.

One goal is that our tooling reinforces that Development and Operations not only have shared goals but have a common backlog of work, ideally stored in a common work system and using a shared vocabulary, so that work can be prioritized globally.

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

Features are always a gamble. If you're lucky, ten percent will get the desired benefits.