• 0 Posts
  • 15 Comments
Joined 7 months ago
cake
Cake day: February 27th, 2026

help-circle

  • There is a laboratory of sorts. A pornography laboratory. If you were to inadvertently stumble upon this pornography laboratory, I would strongly discourage using an external search engine with site: to peruse its despicable contents. You might find all sorts of revolting content you thought had been safely buried in the sands of time.










  • I fondly remember the time I hired a QT expert onto an embedded app team and on his first project he imported a sort algorithm from std. He found the system got weird and glitchy, and often crashed.

    Yeahhh turns out the algorithm he chose needed to make a copy in memory and the thread he was working in only had 2048 bytes of stack, so larger inputs would corrupt the stack allocated to the next thread. I had to explain to him that we had a full second to complete the math before we had to give back our semaphore, so saving a couple milliseconds on the sort was not a priority. Fun times.




  • There’s an important lesson you have to learn at a certain point in your career: how and when to say no.

    In your early years, it makes sense to be the guy who scoops up the side quests. It’s basically the best way to learn new skills and figure out what interests you.

    When you reach a certain level of seniority, you’ll need to be much more selective about what you take on. You should be focusing on the highest value work that your skills allow.

    So what do you do when these requests come up? Ideally you delegate them to a junior team member, but you can also just say no. Obviously you should be professional about this, but it’s perfectly reasonable to say that what you’re doing is higher priority and you can’t be distracted from it. If it’s important, they’ll ask someone else, and if it turns out you really are the only person who can do it, then you can pick it up when you, the expert, think it’s appropriate.



  • My company recently acquired another and picked up some interesting legacy infrastructure: on-premises mainframes running COBOL. What I found particularly funny is that this system has deprecated but still in-use legacy components of its own, like a telnet server, and that this legacy component also has legacy components that may or may not still be in use (character mappings for specific teletypes that different remote clients used).

    I guess that at some point, everything any of us do will become someone else’s headache.