• 0 Posts
  • 63 Comments
Joined 1 year ago
cake
Cake day: July 5th, 2023

help-circle


  • I have a few times in life, but I’ve always found a new one.

    Each time I’d get deep enough into something, tech advancements always made that thing functionally obsolete.

    Once again I’m watching my skill set being phased out, but am working on my big last hurrah project right now that I’ve dreamed of for years. Having a great time doing it, but have already started the process of replacing it over the next 18 months.

    The one plus side now is that the company I’m with has already invested in my training for the next big thing. I’ve been through it enough times that I don’t feel like I’m losing something or wasted my time.


  • Don’t let yourself get bottlenecked. The debug cycle can spiral out of control when you too fixated on one element.

    When you feel that happen, take a five minute break and figure out some other part of the project you can spend time on that you know will work. Wasting hours on a stuck pig is frustrating, spending those hours instead making other progress let’s you simmer on the issue.

    Come back to it later with fresh eyes, and maybe it will be easier. If you hit the same wall after many attempts, maybe you have to find a different solution, and at least you got a ton of other stuff done.

    The sunk cost fallacy is a lot worse when you’ve spend multiple sessions on the same issue.

    It also helps when you can identify these problems early in the project cycle. Knowing what parts will work because you’ve done it before, versus new modules you haven’t worked with, helps to plan testing of the unknowns early, even if they are used later in the project.

    On large scale projects, I make sure to prototype the unknowns right at the beginning, and when I get stuck, I do easy work till I feel relaxed again. If I don’t solve the first one, move on to the next, and next, unknown till I’ve been through each at least oonce. Then you’ll have a road map of what works, and what’s going to take the hard, head down, jam music on, I’m not stopping to piss till this works or I abandon it, sessions.

    Then I know there are X number of those sessions in the project, and when I’m in that kind of mood, I tackle one. Some days you just want to bang out easy UI and functions, others you’re ready to beat your head on the keyboard till that one thing works.

    Other than that, I write a lot of test code around the problem so I can isolate exactly what where is. Then once it’s fixed, I go back and strip it all out. Don’t be afraid of spending time really understanding the issue before just doing brute force. In your example, if a module doesn’t do what is expected, are you sure your connected to the module? Are the commands formatted correctly? Do you get any response from it or is it just dead or not loading? Can you write around it? Are there other modules available? Can you write your own code instead of using the module?

    At the end of the day, what you said is right, step away and clear your head. I can’t count the number of times I’ve come back to something I strained at for hours or days, only to solve it in 15 minutes a week later.


  • The pace of change is about every five years, and some elements are always in transition.

    All in one turn key solutions are always one to two cycles behind, so may work great with the stuff I’m already replacing.

    I think these are honest attempts to simplify, but by the time they have it sorted its obsolete. If I have to build modules anyway to work with new equipemnt, might as well just write all the code in my native language.

    These also tend to be attempts at all in one devices, requiring you to use devices only compatible with those subsystems. I want to be able to use best tech from what ever manufacturer. New and fancy almost always means a command line interface, which again means coding.









  • If you don’t feel it, don’t do it. Some injuries don’t heal right, and many of the hobbies I enjoy have a pretty damned high risk factor. Almost every single time I’ve had a serious injury, that little voice was telling me “This one might not end well”, and I went for it anyway.

    I could have walked away, called it a day, and come back another time. It wasn’t a contest, I was just out filming a few tricks for my “You’re turning 40 and still doing it” video. Didn’t stretch, didn’t warm up, and my over enthusiastic filmer was all “Try this, do that”. Ended up collapsing my knee and fully tearing my MCL.

    Between that and a few neck and back fractures over the years, my mobility and flexibility are pretty well shot. There are things I just can’t do anymore.

    Sure I still skate, and am amazed just how much I can still get away with, but now every minute on the board includes a constant “Is this safe? Is this worth it?” chant.