In my last post, Stop Hitting Yourself, I described (long-lived) branching in version control as an anti-pattern. It’s something we want to avoid. But then what are the alternatives to branching for integrating code as it’s being built into a production system? We can’t let half-baked features slip out into production. If we do, the …
Continue reading “Use Flexible Feature Flags”
Read MoreIf there was a button on your computer that said “DO NOT PUSH,” would you push it? If you push the button and a hand comes out of the monitor and slaps you on the face, would you push it again and again? Of course not! But then why do you continue to use branching …
Continue reading “Stop Hitting Yourself”
Read MoreMost of the time when we’re building software, we’re thinking inside out. We focus on the behavior that we want to create, and build the system up from that. We do this because we’re anxious to get at the heart of the problem and solve the core issues. But there’s a problem with this approach …
Continue reading “Outside In or Inside Out”
Read MoreListen to a great interview with me, Ryan Ripley, and Woody Zuill on [PODCAST] Agile for Humans where we discuss my book, Beyond Legacy Code, the software industry, and many other topics: http://ryanripley.com/beyond-legacy-code-with-david-bernstein-and-woody-zuill/ (11 Mar 2016)
Read MoreMost fundamentally, I wrote my book because I wanted to make the world of software development accessible to many more people outside the software industry. I had accumulated a lifetime of experience as a software developer. In that time, I had come in contact with many individuals who I would consider to be outstanding developers. …
Continue reading “Getting Started Writing Beyond Legacy Code”
Read MoreIn a 2002 National Institute of Standards and Technology report entitled “The Economic Impact as Inadequate Infrastructure for Software Testing,” software defects costs nearly $60 billion annually in the United States alone. This report is often misquoted assaying that software bugs cost $60 billion but software bugs likely cost industry and consumers much more than …
Continue reading “A Billion Here, a Billion There”
Read MoreA first principle is a principle that is so fundamental that we can infer other principles from it. The Golden Rule is an example of a first principle, “Do unto others as you have them do unto you.” This is a first principle because many of our laws, our code of ethics, and even our …
Continue reading “First Principles”
Read MoreNewton said we stand on the shoulders of giants and that’s certainly true for me. Many of the ideas that I have drawn on for *Beyond Legacy Code: Nine Practices to Extend the Life (and Value) of Your Software* came from a range of other sources both within the software industry and outside of it. …
Continue reading “Do This Because”
Read MoreSME stands for Subject Matter Expert. This is a key role in the development of software. The level of understanding one must have to write software is very deep. Developers have to become SMEs when they work on a project. In my career as a software developer I have learned tons of things in many …
Read MoreIn his book Crossing the Chasm, Jeffrey A. Moore discusses what he calls the technology adoption life cycle for new products. He describes five distinct phases that innovative products go through based on the five different kinds of adoptors. The technology adoption life cycle applies not only to new products but also to anything new …
Continue reading “Crossing the Chasm”
Read MoreCheck out the video roundtable I was in yesterday: Continuous Discussion-Metrics that Matter: http://bit.ly/1WODPZJ (26 Jan 2016)
Read MoreA large part of the success of the lean manufacturing movement was its call to eliminate waste. Deming introduced the concept that waste in manufacturing came from excessive inventory. Inventory was considered waste because it tied up capital and required that it be kept in storage until it was ultimately sold. But what is waste …
Continue reading “What is Waste?”
Read MoreMy new book, Beyond Legacy Code, Nine Practices to Extend the Life (and Value) of your Software is out. I guess one obvious question is: Why nine practices? I wanted to organize the book around core practices because this would let readers jump around in the text and focus on the practices that are most …
Continue reading “Why Nine Practices?”
Read MoreI wrote Beyond Legacy Code: Nine Practices to Extend the Life (and Value) of Your Software because I noticed two major disconnects in my experience as a developer. First, the more challenging technical practices such as test driven development and refactoring, were not being as quickly assimilated by teams as some of the simpler Agile …
Continue reading “Why I Wrote Beyond Legacy Code”
Read MorePeople define success differently. This is not only true individually but we define the success of products or projects based on different criteria, too. To the Standish Group, success is about predictability. They define the success of a software project as one that is delivered on time, on budget, and with all the features and …
Continue reading “How to Define a Successful Software Product”
Read More