this post was submitted on 23 Jul 2023
133 points (97.2% liked)

Asklemmy

43402 readers
1297 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] intensely_human@lemm.ee 1 points 1 year ago (1 children)

I think the root cause is the complexity. I do a lot better in jobs where the situations might change but the rules don’t. In programming, everything is changing all the time and I can’t keep up. There’s no repetition and if you are repeating yourself you’re doing it wrong.

I need parts of the day when I’m not being creative within a formally strict environment. It takes too much processing power for my brain to do that, and it overworks me.

I know the root cause and the problem is solved because I’m working jobs that have complexity within the range I can handle.

[–] dexx4d@lemmy.ca 1 points 1 year ago

I think the root cause is the complexity.

Split the problem into manageable chunks, then attack the chunks. Apply recursion as needed.

This is part of a more senior skillset, as some times a senior will be breaking up the problem and assigning the smaller pieces to other devs.