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

help-circle

  • eldavi@lemmy.mltoProgrammer Humor@lemmy.mlDebugging
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    3 days ago

    With imperative style, you have a lot of implicit state that you need to know to figure out what actually happened. So, you end up having to go through the steps of building that state up before you can start figuring out what went wrong.

    i think i struggle with this part the most since i’m entirely self taught and relied on very old methods for writing my source since the educational material i used was the most common and freely available at the time i starting doing development work. i’ve learned that it was acceptably sufficient for the IT-based problems that i was trying to solve at the time i learned it and that legacy style has been keeping me at a disadvantage.

    if seen some of the newer style of debugging like the one you’re shared from the young fresh graduate developers who are lucky enough to be spared the slog of a over decade within “customer service” oriented side of the tech industry umbrella and it’s painfully evident to me how vastly superior it is compared to the old methods that i taught myself and it’s encouraged me to seek a degree to help me master them and my new job will make that degree free for me; which matters A LOT as an american considering the price tag it entails.



  • it’s more a reflection of my experience and their stereotypical blind spots:

    the IT work that i did before becoming a developer has taught me to succeed by placing emphasis on delivering on time and with minimal maintainability to the exclusion of everything else and it verbally sits poorly with the more privileged engineers that i work with; but they do the same thing obliviously nonetheless. like you, they make assumptions based on who they think you are without realizing that they’re the same way.

    their insistence that they own all aspects of the peer reviews; plus management’s insistence that we acquiesce to them despite seeing blind spots in the review process; plus their unwillingness to listen to someone who doesn’t fit into the in-group allows for this to happen and i’m only allowed to voice my concerns when prompted to like a soldier in the implicit security example that i shared.

    developers are just a screwy as everyone else and the ones that management help to drink their own bathwater is creating a world where new developers will have to be likewise privileged to even be allowed in, in the future; i know that the ivory tower developers believe that this is a good thing, but this disconnect with reality is fueling the socioeconomic gaps that let people like trump win elections and ruin things for everyone.



  • i start everything i do w chatgpt and it’s twice given me a dummy function/method that immediately worked and this was my reaction both times. lol

    it shipped both times and not even the senior guys caught it in any of the peer reviews before it reached the clients; it’s been almost a year for the first one and they’re still happy w it. 🤷










  • i use scotty’s 2:1 rule now: if i think it’s going take an entire sprint i automatically tell my managers that it’s either a story or an epic. if i’m sure that i only need the sprint, then it becomes a story; but if i’m not sure i can get done in a sprint, it becomes an epic.






  • I’ve left jobs before because the description and the interviews made it seem fascinating; but I mastered the stack in a couple weeks and became VERY bored.

    Somehow; the less savvy the interviewers are the more interesting the work is and its usually bad more often than good; but when it’s good It’s fantastic and with usually mediocre pay.

    Also it’s somehow always a mixed bag when the interviewers are more experienced than I because you would think that it would be great, but it’s never as good as the previous category; decent but not good. But they usually pay the most so that mostly makes up for it.