Check out my new sticker :)

I’m having to justify why our QA team doesn’t actually point stories… anyone have a good reference?

I recently worked on a small website for a nonprofit…and I unintentionally burned myself out. I enjoyed the work, but I obsessed over it and didn’t take enough breaks…

The organisation lost all their content because someone didn’t pay the host provider and the admin didn’t care to keep a backup…Wayback Machine to the rescue, I got 80% back, it’s just missing some photos. Then I migrated the static WP files to a Nuxt app.

“Please don't use Google docs in the [redacted] env--it is not allowed at all and we will get dinged. You should all have MS Office so please save important artifacts in an approved format.” —Said someone being bribed by Microsoft

For a moment, I forgot how wasteful the government can be… our team is being forced to use VMs in the cloud which will cost somewhere around 3-5 hundo a month per instance

Immediately after the last major release, I enabled CheckStyle to fail on unused methods and variables, and then I proceeded to delete all dead code. The test suite passed and I got approval to merge. Two months later, the next major release went out the door…guess how that went :)

Using TDD or at the very least writing unit tests ensures your code won’t break, or go missing!

So I snapped during pointing session and told the BA that I didn’t have time to explain software engineering to the team….then they proceeded to make up new requirements that the client didn’t ask for which resulted in more complex error handling that presents the user with a list of generic message; I try really hard to keep implementation details out of those meetings, because all it does is bog down the team and waste time, but I suppose I fell into that trap.