PinnedDan Goslen·Jan 31, 2024Why I Wrote a BookWriting a book is not for the faint of hear. Here is why I decided to do it anyway.A response icon1A response icon1
PinnedDan Goslen·Oct 3, 2023Getting Stuff Done on a Software TeamInstead of starting things, let’s focus on finishing them.A response icon1A response icon1
PinnedInBetter ProgrammingbyDan Goslen·Jun 21, 2023What’s the Point of Blameless Postmortems?Do you remember Bob Ross?A response icon5A response icon5
PinnedInITNEXTbyDan Goslen·Jun 15, 2021I’m Changing How I Review CodeCollaboration is more than just writing a comment on the internet.A response icon7A response icon7
PinnedInBetter ProgrammingbyDan Goslen·Mar 2, 2021Our Obsession With Design PatternsDesign patterns are great to use. However, they can lead to roadblocks when used in excessA response icon5A response icon5
Dan Goslen·Jun 23, 2025How to Respond When Your Project is LateA practical guide for handling the inevitable situation of being on (or leading) a late project.
InLevel Up CodingbyDan Goslen·Apr 15, 2025Speed Through CompetenceThe other week, I heard an interesting little sound bite
Dan Goslen·Jan 22, 2025Layers of InnovationSoftware companies love to talk about innovation. Whether they are building a product that will “revolutionize the way teams do X” or will…
Dan Goslen·Sep 26, 2024One Key to Growth: Seeking Out DiscomfortThere are many newsletters, tips, and tools for growing as a software engineer these days. And I think that is great! In many ways, I wish…
