Code Reviews are Dead. Here's Why.
The code review is a long-established "first line of defense" so that engineering teams don't unleash hell upon the world. Years ago, the code review literally was a developer printing out their code, handing it to a senior engineer, and having it marked up with red pen like it was a college essay. The code review has come a long way - it has been established part of development workflows everywhere largely because of the pull request feature at GitHub. Code reviews were part of the job description for senior developers and development managers everywhere - a pedagogical function that promoted stewardship over a code base. But that was then. It's time to pour one out for the code review.
Overthinking User Experience? Alexa's Jeopardy Just Did
My wife and I were loyal, sheepish players of Alexa's Jeopardy game. Every weeknight like the moths to flame that we are, we would flock to our Amazon device (well, an Alexa-enabled Sonos actually) and commanded Alexa "Play Jeopardy!"
Do You Need a Scrum Master? Why They May Be Holding Your Team Back
The Scrum Master - a mainstay in Agile culture, particularly Scrum. Heralded by consulting firms, conferred certificates by training academies - here's why you don't need a Scrum Master and why if you have one, they are hurting your agile efforts.
Here's Why Software Development Cannot Be Industrialized
Waterfall. Scrum. Spiral. RAD. XP. Software methodologies are plentiful, all in an effort to make it so that timelines and budgets are predictable. They are an attempt to create repetition and commonality within software development. But they are a lie.