I have tried for 20 years to get into coding, and among adhd and having 10 million other projects going on, just could never get it beyond absolute basics and knowing some differences between languages.

Now it seems every tutorial I see is really just clicking around in a gui. Very little actual typing of code, which is the part I actually find cool and interesting.

So my question is, since everyone on lemmy is a programmer, what do you guys actually do? Is it copying and pasting tons of code? Is it fixing small bugs in Java for a website like “the drop down field isn’t loading properly on this form”?

I just dont get what “a full stack developer sufficient in sql and python” actually does. Also i dont know if that sentence even made sense!

  • noughtnaut@lemmy.world
    1·
    1 day ago

    …and then you get reprimanded for lackluster productivity (judging by progress on the projects on your own plate). 😑

    You lifting up others doesn’t translate to losing yourself up, unless there is (unusually) healthy culture about that in your company.

    • LedgeDrop@lemmy.zip
      3·
      2 days ago

      You have a good point… and I’ve worked on both sides of the fence. Currently, I’m at the “healthy culture” camp, but it wasn’t always that way.

      While I was working at companies that had a not-so healthy culture, there were things I did to “bring visibility” to these non-work tasks. However, I should add that at these types of companies didn’t really offer a lot of financial compensation for this non-work, but at no-time did anyone challenge my productivity.

      Basically, I’d suggest:

      1. Be (technically) opinioned and make it visible. Often, it’s not your boss you need to impress (as they see your work every day), it’s your boss’ boss. If you have a reputation within the company as a guru in something, it’s easier for your boss’ boss to “see” that you’re bringing “value” outside of you day-to-day tasks.
      2. Bring visibility to these (side quest) discussions. At one company, I created a chat room to use as a sort of “technical self-help”(for all Engineers) and any DMs I got, I would ask them to funnel the discussion into the chat room. I asked them to do it “so others can find the answers to similar questions” and more importantly “to bring visibility to these discussions”. You, your boss, your boss’ boss can see how much time you invest in these topics and they can see that this help does not come for free.
      3. If your not meeting your goals (or are stressed out) , due to these side-quests - tell your boss. Explain (as early as possible) that project X will slip if you keep focusing on unblocking others and let them decide what to do. If you followed-up with Point 2, you’ve got concrete evidence to justify where your time is being spent.
      4. When people ask you “what are you doing?” (like during your Stand Up). Do not answer “nothing” or “supporting others”. Be detailed, mention the actual technical topics (and if you’ve got this chat room, reminding yourself is much easier).
      5. Last bit, which might not be helpful. If it’s the same questions or some fundamental misunderstandings that your often answering: maybe offer a Dogo/training for anyone who’s interested. When you offer it, shout it from the highest tree top - it’ll go far in establishing yourself, in the company’s eyes, as a guru (even to those who don’t understand the topic) and it’ll (helpfully) reduce the amount of questions in that topic.