As high performing development teams we need to have individuals on our teams with high technical knowledge and individuals with high domain knowledge as well as many other factors to keep our teams performing well. However the most important thing we all need for our teams to perform their best is psychological safety.  What Is Psychological… Continue reading Encouraging and Maintaining Psychological Safety in Software Development Teams

“Hey Framework! Any time this API endpoint is called and we create an object that is a SomeController that needs an IDoThingsService, create a brand new DoThingsThisWayService and use that. When the SomeController object gets destroyed, keep the IDoThingsService we created until we’re done with the API request in case something else needs it during this scope. Once we’re done with the API request, then destroy the IDoThingsService.”

Writing about technical things is hard to do well. These are some of my tips for communicating about technical things which should help whether we’re asking questions or giving answers or just providing documentation. Be VERY specific When writing about an issue, whether we’re asking a question or giving an answer, be very specific about… Continue reading Tips for Online Communication: How to Ask Good Questions and Give Good Answers

I was gonna sit down and write about how hard it is for me to spend at last 30 minutes once a week to sit down and write because there’s work to be done and OMG why aren’t I doing that work right now?! I was also going to publish my writing from last week… Continue reading Technology Makes This Easier All The Time

In a perfect world, specifications are clear and concise. Developers take those clear and concise specifications to write unit tests before writing the code that does the work. Then it’s red -> green -> refactor -> Bob’s your uncle you have good code! In the real world, you could end up writing tests after the… Continue reading A Guideline for Unit Testing After Development: Only Test Your Code