• 10 Posts
  • 242 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle


  • Product Owner: “How many more people is it going to take to fix the road?”

    Dev Team: "Well, there’s a ticket in the backlog to put out the underground fire. It’s been in the backlog for five years, and it’s a blocker for this “Fix Road” ticket.

    Product Owner: “…so, can we fix the road first and then go back and put out the fire a little bit at a time as capacity allows over the next few sprints?”

    Dev Team: “…”




  • Every time I think about hosting my own mail server, I think back to the many, many, many times I’ve had to troubleshoot corporate email systems over the years. From small ones that ran on duct tape and prayers to big ones that were robust, high dollar systems.

    98% of the time, the reason the messages aren’t coming or going is something either really obscure or really stupid. Email itself isn’t that complicated and it’s a legacy communications medium at this point. But it’s had so much stuff piled on top of it for spam and fraud prevention, out of necessity, and that’s where the major headaches come from. Honestly, it’s one service that to me it’s worth paying someone else to deal with.






  • Reviewing large PR’s is hard. Breaking apart large PR’s that are all related changes into smaller PR’s is also hard.

    If I submit a big one, I usually leave notes in the description explaining where the “core” changes are and what they are trying to accomplish. The goal being to give the reviewers a good starting point.

    I also like to unit test the shit out of my code which helps a lot. The main issue there is getting management to embrace unit tests. Unit tests often double the effort up front but save tons of time in the long run. We’re going to spend the time one way or the other. Better to do it up front when it’s “cheaper” because charging it to the tech debt credit card racks up lots of expensive interest.