There are lots of similarities currently within software engineering and mathematics and a lot of analogies which apply to Software engineering apply to mathematics and vice versa.
> At least for now someone still has to decide what to prove and why. Like why are you trying to prove that thing to begin with? Presumably it's a step along some journey, right? Maybe the journey is where you need to start deriving your satisfaction from, then.
Beautifully said. I had been thinking about the same thing and the analogy b/w CS and mathematics and these were some that I had found:
1.) to prove/disprove from the proofs that OAI created, you needed an mathematician to do so and OAI had to withdraw three mathematical proofs.[0]
But it was only because an expert within the field could verify if it was true or not, I feel as if software engineering is the same as well. We are/can be paid to prove/disprove if a software is working as intended or not.
2.) for someone to be that said mathematician who disproved it, he had to learn the basics of mathematics and multiple branches of it to then perhaps specialize in one thing that he most strongly resonated with and within all this learning, there was some struggle definitely involved. They had to learn algebra etc.,
this analogy can also extend to how we teach children algebra/calculations and other things even though we have had calculators for a long time, yet, we teach children how to do calculations because it is still valuable enough and either teaching maths can help them perhaps in future make a mathematician or it can help them be less reliant on simply calculators and more confident on on the spot calculations and help them within this skill.
As knowing calculation has become the norm rather than exception, even though we have calculators. In fact knowing how to do calculation by hand can perhaps better help you write a problem to calculator. Knowing the technical aspects of CS can help you express a problem to AI with much more depth and effectiveness as well.