• 2 Posts
  • 205 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle


  • Cook’s Venture (an Arkansas poultry processor) went bankrupt practically overnight. Then the state came in and killed all the chickens at each farm, leaving the farmers to deal with all the dead and rotting corpses.

    What did our wonderful governor do? Well, as I recall, her administration refused to declare a state of emergency and pretty much told all the poultry farmers to go fuck themselves because it’s “not the government’s job to bail out private businesses” or some bullshit like that.

    Doesn’t feel so good when you’re the one getting told to fuck off. I hope all the people who voted for Trump and Sarah Sanders are happy since this is exactly what they voted for.







  • That’s a tough one. There’s not a ton of great options for personal accounting apps, much less self hosted ones. I used Pocket Smith (subscription based) for years which actually does what your looking for. Decent product overall. I switched from them to Quicken mostly because I’m an anal retentive personal accounting nerd and the fact that they couldn’t produce a conventional income statement or balance sheet was a long running frustration of mine.

    If I had to choose another platform again, I would go with spreadsheets since it can be as simple or complex as you want to make it. I know that’s not really what youre looking for. Wish I had a better suggestion.







  • One time I worked on a team that had a ridiculously high defect rate. Stuff was constantly getting kicked back from QA. Management kept piling on all kinds of convoluted processes to try to reduce the number of defects which only made things worse.

    I started really hammering the need for doing a root cause analysis as part of bug/defect tickets. Don’t just fix the bug. Make sure you understand what caused it and link the bug ticket to the ticket that caused it.

    Big surprise (not really), 90% of the bugs and defects were being caused by like 3 people.

    Your comment made me think of some of the PM’s whining about adding one story point for doing an RCA because apparently it’s better to just ignore the problem and keep pumping out shitty broken code as fast as possible.





  • PO: “Why does it seem like it takes a really long time to develop new features?”

    Dev: “I’m glad you asked! We’ve got this piece of code (points at smoldering pile of spaghetti) that literally has to be changed every time we do anything. The person who wrote it has been gone for like four years. No one knows how it works and it’s central to the entire application. I would estimate that this easily doubles the time it takes to work each ticket. I’ve created a set of stories to rewrite this code. We just need your approval to bring it into an upcoming sprint.”

    PO: “Can’t… Hear… Breaking… Up… Bad connection…”

    Dev: “Uhhh… This isn’t a Teams meeting. You’re sitting in the room with us right now.”

    PO: …

    Dev: “We know you’re still here even if you’re not moving.”

    PO: …