Parts of my job that I enjoy: - Designing systems - Writing elegant code - Learning new things - Solving interesting problems - Sharing knowledge
-
Parts of my job that I enjoy:
- Designing systems
- Writing elegant code
- Learning new things
- Solving interesting problems
- Sharing knowledgeParts of my job I don't enjoy:
- Reviewing other people's code
- Debugging systems I'm not familiar with
- Blindly using poorly documented interfaces
- Dependency hell
- Being forced into the latest fadAI enthusiasts: "What if I told you I've solved one of those lists for you?"
@tojiro this is like me and copywriting, archiving, and documenting stuff.
The joyless ghouls want to deprive us all of even the smallest amounts of joy.
-
Parts of my job that I enjoy:
- Designing systems
- Writing elegant code
- Learning new things
- Solving interesting problems
- Sharing knowledgeParts of my job I don't enjoy:
- Reviewing other people's code
- Debugging systems I'm not familiar with
- Blindly using poorly documented interfaces
- Dependency hell
- Being forced into the latest fadAI enthusiasts: "What if I told you I've solved one of those lists for you?"
I enjoy reviewing other people’s code. Either I learn something, or I get to teach them something (often both in the same PR), both of which are fun. Emphasis here on ‘people’. I don’t learn from a machine that regurgitates median-quality output, and it doesn’t learn from my comments.
-
Parts of my job that I enjoy:
- Designing systems
- Writing elegant code
- Learning new things
- Solving interesting problems
- Sharing knowledgeParts of my job I don't enjoy:
- Reviewing other people's code
- Debugging systems I'm not familiar with
- Blindly using poorly documented interfaces
- Dependency hell
- Being forced into the latest fadAI enthusiasts: "What if I told you I've solved one of those lists for you?"
@tojiro really, so you say you like to learn new things? But first couple of things in your don't like to do list is review other peoples code and debug unfamiliar systems, sounds like you don't like to learn new things as that ain't the attitude of someone who likes to learn new things.
-
@tojiro I think notably, doing the List 1 items well, rather than outsourcing them to the slop machine, beyond being enjoyable, rewarding, and resulting in better code, reduces the List 2 misery for everyone else.
-
Parts of my job that I enjoy:
- Designing systems
- Writing elegant code
- Learning new things
- Solving interesting problems
- Sharing knowledgeParts of my job I don't enjoy:
- Reviewing other people's code
- Debugging systems I'm not familiar with
- Blindly using poorly documented interfaces
- Dependency hell
- Being forced into the latest fadAI enthusiasts: "What if I told you I've solved one of those lists for you?"
@tojiro great summary of the madness .
-
Parts of my job that I enjoy:
- Designing systems
- Writing elegant code
- Learning new things
- Solving interesting problems
- Sharing knowledgeParts of my job I don't enjoy:
- Reviewing other people's code
- Debugging systems I'm not familiar with
- Blindly using poorly documented interfaces
- Dependency hell
- Being forced into the latest fadAI enthusiasts: "What if I told you I've solved one of those lists for you?"
@tojiro my experience has been that AI helps with a mixture of those two lists (and certainly doesn’t “solve” any of them completely). E.g. LLMs seem to pretty adept at dealing with dependency hell, or at least getting them untangled a lot more quickly than I can myself.
-
Parts of my job that I enjoy:
- Designing systems
- Writing elegant code
- Learning new things
- Solving interesting problems
- Sharing knowledgeParts of my job I don't enjoy:
- Reviewing other people's code
- Debugging systems I'm not familiar with
- Blindly using poorly documented interfaces
- Dependency hell
- Being forced into the latest fadAI enthusiasts: "What if I told you I've solved one of those lists for you?"
@tojiro I rarely ever got to do anything at work from that first list even before AI
-
@tojiro
Reviewing other people's code and debugging unfamiliar modules is where we grow the most though.My advice to new programmers is always "read other people's code! Do it regularly, with the goal to understand how it actually works. Step through it in the debugger!"
@StompyRobot @tojiro Not wanting to put words in Brandon's mouth, but I think the crucial part is, he's not saying he wants AI to do the second list instead of the first. AI could just not do either of them.
Speaking for myself: I enjoy the same things and dislike the same things, but I will gladly continue doing the things I dislike (in part because as you say, there are positive things to be gained from doing them) but why on Earth would I want AI to do the things I enjoy the most?
-
@StompyRobot @tojiro Not wanting to put words in Brandon's mouth, but I think the crucial part is, he's not saying he wants AI to do the second list instead of the first. AI could just not do either of them.
Speaking for myself: I enjoy the same things and dislike the same things, but I will gladly continue doing the things I dislike (in part because as you say, there are positive things to be gained from doing them) but why on Earth would I want AI to do the things I enjoy the most?
In the best of worlds, we get to pick which parts we do!
A hobby woodcarver might use a knife where an industrial process would use CNC, and that's OK!
Note that society doesn't pay me to "do the bits I enjoy" though. They pay me for robust, working software, as quickly as possible, and the models can help achieve that, when guided.
-
Parts of my job that I enjoy:
- Designing systems
- Writing elegant code
- Learning new things
- Solving interesting problems
- Sharing knowledgeParts of my job I don't enjoy:
- Reviewing other people's code
- Debugging systems I'm not familiar with
- Blindly using poorly documented interfaces
- Dependency hell
- Being forced into the latest fadAI enthusiasts: "What if I told you I've solved one of those lists for you?"
@tojiro arguably they did solve "reviewing other **people's** code" too
-
In the best of worlds, we get to pick which parts we do!
A hobby woodcarver might use a knife where an industrial process would use CNC, and that's OK!
Note that society doesn't pay me to "do the bits I enjoy" though. They pay me for robust, working software, as quickly as possible, and the models can help achieve that, when guided.
I didn't think the original post was talking about what you or me are paid to do...
I'll just end the discussion here because I feel we're on vastly different ends of the spectrum. Have a nice day!
-
Parts of my job that I enjoy:
- Designing systems
- Writing elegant code
- Learning new things
- Solving interesting problems
- Sharing knowledgeParts of my job I don't enjoy:
- Reviewing other people's code
- Debugging systems I'm not familiar with
- Blindly using poorly documented interfaces
- Dependency hell
- Being forced into the latest fadAI enthusiasts: "What if I told you I've solved one of those lists for you?"
@tojiro same same
-
R relay@relay.mycrowd.ca shared this topicR relay@relay.infosec.exchange shared this topic
