The point I was trying to make was not "enjoying the process for the sake of it", but paying attention and spending effort on the journey created better software at the end.
When you look at older software, most of it was higher quality than the things we have today. A web site contained more information in a more readable way, more features in a smaller footprint. Same for native applications.
Now we slap what we found online together and calling it done. Everything is sparse, takes ages to load, centuries to submit and everything is so disconnected and async that some simple features are straight out impossible.
This is what fixating on the destination brought us. I dare you to download something you purchased 3 months ago via a 4096 character S3 link they have sent you, and double dare you to ask customer support for a new link. I'll bet that with a 80% chance they have no way to verify your serial number, even.
Have people completely forgotten how to read? I'm saying your analogy between software and math is completely, irreconcilably flawed. I don't need to read the rest of your screed because this is a thread about math not software.
I see.
Somebody said that lowering the bar is not good. Somebody else asked for examples, and I provided an example. So, if you want to be pedantic, that doesn't track well, because what I answered was not about mathematics.
If you want something about mathematics, computation is mathematics, as software is. So, my example tracks the same way in mathematics.
Finding solutions without understanding its parts or the path is equally detrimental to mathematics as it is detrimental to software.
Maybe you need to read a bit slower and think along the way. Using AI too much blunts critical thinking skills in some, as I read.
What was the end of the proof thing you mathematicians use, was it "Q.E.D."?
Q.E.D.
> computation is mathematics, as software is. So, my example tracks the same way in mathematics.
brother i already addressed this literally in my first response to you: the reason software went to shit is because it became commodified (ie a thing produced in a factory) not because it's computational nor because the bar got lowered. seriously read my whole original reply again and see whether you really disagree before just re-asserting your rant on SWE.
> Finding solutions without understanding its parts or the path
you didn't read the post at all did you? it's emphatically about deep understanding over blind results.
> Using AI too much blunts critical thinking skills in some, as I read.
irony