I still research my code issues for hours on endless websites instead of asking AI
shrug
I still research my code issues for hours on endless websites instead of asking AI
shrug
@stux that is very inefficient.
@Mellivora I am enjoying it so don’t really matters 😁
@stux you must be a masochist.
@Mellivora @stux Funny, I was going to say the same thing about you.
@Mellivora @stux Still better than asking a resource-guzzling plagiarism bot.
@Mellivora@im-in.space Efficiency is just a capitalist requirement.
@Mellivora@im-in.space It really annoys me how lots of coders are prompting themselves into redundancy in the name of efficiency.
It's the only way to be sure.
@jaywink Also learning a LOT and discovering a lot of new stuff in the process 💪
@stux@mstdn.social This 💯
@stux Human, you are a good human.
That's because you are AWESOME 👏
@stux Some day AI will stop working, but all the things we learned will remain because we passed on the knowledge.
@stux same here
@stux
Yeah, but doing that makes you learn too much and knowledge is dangerous.
Yes, skills. Terrible things those. No need for them anymore. Stay safe, stay cozy.
@stux Being independent from expensive online services and actually know how to write code is essential. It also trains the brain in a positive way and makes you more satisfied by feeling success.
Programming is also much more than typing stuff. It's happening in your brain and is using intuition that no machine has.
Have much fun. You're doing the right thing.
@stux Exactly my way of working, added to a lot of code-reading / debugging. Deeply understanding the technology, problem and code helps writing better, faster and safer code. And it’s nice to feel the thrills when the job is finally done.
@stux I recently did a python script that took me three times what I thought it would, but since it's been a couple years since I did any programming at all, I know that happens.
Still, I enjoyed the struggle and relearned stuff, as a bonus I had that satisfaction of seeing it do precisely what I wanted with as few lines as possible.
As I read somewhere here in the fedi, knowledge requires friction in order to be absorbed.
@stux I find that if I can't find a solution myself on like the first try, the chatbots also have no clue and will usually just output some remix the documentation for something else with some of the words I used.
@stux I spent a few days last week determining how to best abuse FasterXML's Jackson to convert a flat JSON structure to a very different list of structured objects based on the field name (another custom annotation to indicate a setter method and a few hundo annotations, and a configured ValueInstantiator to build the structure from a value and the deser context). Sure, there's POJO to POJO mapping, but that sucks and is way more code to maintain than just deserializing directly into our types.
@stux
I guess you're just a better person than the rest of us.