1,387 karma · joined June 5, 2019
My approach to interviewing is that I want candidates to do the best they possibly can.
Sometimes it feels like Jira is so incredibly configurable but is really missing the "pit of success". There is a way to make it nice to use and reasonably performant, but you really need to go into it with a strong plan. And even then it's really easy to balls it all up in short order if you're not vigilant.
I'm also bullish on using them with Marimo notebooks as a replacement for Jupyter notebooks.
One case where git bisect really saved me was when we discovered a really subtle bug in an embedded project I was working on. I was able to write a 20 line shell script that built the code, flashed the device, ran 100 iterations of a check, and do some basic stats. I left the bisect chugging away over the weekend and came back to an innocuous-looking commit from 6 months earlier. We could've spent weeks trying to find the root cause without it.
Because most of the iteration is happening in the Bazel layers I can generate a full system update in about 15 seconds with everything being fully reproducible.
I have also had managers who are great at linking the wider strategic goals of the organisation to their team's work. They were rare and worth their weight in gold.
https://www.neowin.net/news/microsoft-points-finger-at-the-e...
The problem with the kind of dirty work the article suggests is that, often, it's invisible. The benefits of solving a lot of these problems are just far enough removed the work that you will work your arse off and other teams will be the ones shipping faster and getting the credit. You'll spend your day fighting fires and the guys running around with a can of gas and a pack of matches are the ones who the execs will see "making things happen".
If you get a manager who understands what you do and has your back, and you get satisfaction from a job well done it can be rewarding. But if either of those changes you can also be on a fast track to burnnout and disillusionment.