![]() ![]() I got a better solution from a different angle. Turns out all my prior digging was unnecessary. In the end, the more-experienced engineer would likely just google a term I had never heard of that precisely describes my problem, and present me with a handful open-source libraries (or a stack overflow post) that already solved it. That, as it turns out, is first question I should have been asking. After some confusing back-and-forth I’d usually get the quizzical response, “what exactly is the problem you’re trying to solve?” My thought process was this: I need to prove that I have been really digging through the weeds and whittle my question down to something unambiguous to save their precious time while saving face. In the early days, I’d nervously walk up to a more experienced engineer and start rattling off a hyper-specific algorithmic question, probably while fingering exact lines of code on the laptop cradled in my arms. In my past life as a software engineer, I learned this lesson quickly: asking the wrong question often yields the wrong solution. tube amp powered by a lunchbox-sized battery Here’s a question I’ve seen come up again and again: “Which battery-powered amp should I get?” Fender Pro Jr. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |