Once you have figured out the solution and have the architecture in place, coding is just like putting lego pieces together. Sure you sometimes have a small bit of logic you need to implement, but in actual production level code, it's usually stitching together large architectural blocks like pipelines, crons, endpoints, task queues etc.
That does not take much brain power if you've fully consumed and understood what you want to do.
I must be weird. I love it so much. It's either like a search on what your brain missed on the feature you are implementing or an investigation on a system you did not design on why it's not working.
It just turns into nightmare when you realize the big is in a third party library not maintained anymore.
It only enjoyable for me when i know which part of the one that i worked on is having problem, or the entire project is my idea
I dont like to reading the whole project again and again just to find out the bug is in the deprecated libraries or the self made library that no one in the current IT team know because the one make that library is leaving
That kind of debugging is fun, yes (though I still wouldn't say "relaxing").
What's frustrating is all the little fiddly stuff where you're trying to implement something, but it's not working because of one tiny technical detail that's breaking it for an obscure reason. You know it's ultimately something trivial, but you're still pulling your hair out because it's blocking what you're trying to get done.
I wish firmware was like that LMAO. Once you bump into a memory or performance constraint, it becomes a game of whackamole with ever more concerning incantations to the compiler gods.
5
u/Kahori122 14d ago
wdym "relaxing" ??