I'm not one to be opening my mouth about these types of things. Let's get that our there right now: I'm super unlikely to identify any of these concerns I'm not gonna be affected if nothing changes My lack of being bothered has zero impact that others are I want…

There's a lot of tools that exist to make what developers to easier to do. If it's something we do a lot, we tend to find ways to have something do it for us. I've done it. I'll probably do it again. I built a little tool to automate the…

There's a lot of tools that exist to make what developers to easier to do. If it's something we do a lot, we tend to find ways to have something do it for us. I've done it. I'll probably do it again. I built a little tool to automate the…

There's a lot of tools that exist to make what developers to easier to do. If it's something we do a lot, we tend to find ways to have something do it for us. I've done it. I'll probably do it again. I built a little tool to automate the…

No new inline? Coming from a predominately Java and C# background, new is how the language instantiates an object so it's a nice short phrase. When we write a method and need a collaborator, we'll typically instantiate the collaborator right there. public void DoStuff(){ var thing = new Thing(); ... } I consider…

Testability - The only way to not have legacy code. If the code you're working in doesn't have tests - it's legacy code. The more tests you have the less legacy it is. I say this coming from the many conversations I've had about what makes code "legacy code&…

As a Software Engineer, what's our job? As a Software Engineer, what's our responsibility? As a Software Engineer, what do we do for the company? I assume we all have a job description - Is that what we do? Design, Write, Test, and Debug software? At a high, generic level,…

ifs only as a guard clause is one of the most impactful things that can be done to reduce complexity in code. I'm a very strong advocate for a lot of Object Oriented Practices. Most of them, really. I'm not great at all the buzzwords... or words I should know.…

MicroObjects is a fantastic way to write OO code. There's very few pain points that I've encountered. The teams using MicroObjects deploy confidently and have near zero bugs. New functionality and features are quick and easy to implement. The practice is vastly different than how most people write code. Most…

We don't have to agree on everything to learn and grow from each other. This is exemplified for me with the Elegant Objects by Yegor Bugayenko. Elegant Objects being a book read about 6 months after an OOBootCamp from Fred George crystallized a few remaining pieces that the boot camp…