sjolsen@beehaw.orgtoProgramming@beehaw.org•I have a confession to make... I code in Comic SansEnglish
2·
1 year agoFriendship ended with font gatekeeping and dogpiling, accessibility is my new best friend
he/him but also any
Recovering software developer, computers resenter
I like playing the bass guitar, painting, and some other things I’m not very good at
Mastodon @sjolsen@tech.lgbt
Friendship ended with font gatekeeping and dogpiling, accessibility is my new best friend
At my last job, doing firmware for datacenter devices, almost never. JTAG debugging can be useful if you can figure out how to reproduce the problem on the bench, but (a) it’s really only useful if the relevant question is “what is the state of the system” and (b) it often isn’t possible outside of the lab. My experience with firmware is that most bugs end up being solved by poring over the code or datasheets/errata and having a good long think (which is exactly as effective as it sounds – one of the reasons I left that job). The cases I’ve encountered where a debugger would be genuinely useful are almost always more practically served by printf debugging.
Profilers aren’t really a thing when you have kilobytes of RAM. It can be done but you’re building all the infrastructure by hand (the same is true of debugger support for things like threads). Just like printf debugging, it’s generally more practical to instrument the interesting bits manually.