Posted on 07/05/2023 9:43:38 PM PDT by SeekAndFind
Oh, dear God, that is precious!
...but now we have the “Agile” methodology, so who needs to spend time on requirements and design? Just get busy writing the code ;p
People actually believe that.
People are really bad at formally defining requirements.
It's a lot of fumbling around in the dark and discovering what has changed since the project was started. Formal definitions are frequently wrong and always incomplete. Our verbal and written languages simply do not allow otherwise. Our thinking patterns do not allow otherwise.
We do OK by taking a few steps at a time, then looking around.
I started in FORTRAN but then quickly moved to C. My last language was Java. I still write in Java on the rare occasions I code. What I liked about COBOL was it’s ability to call sub routines. I didn’t see that in other languages until FORTRAN 4. Well there was Basic’s gosub but Basic was very difficult to organize. I first paying job was writing Basic code back in the late 70’s. Thankfully my next job introduced me to FORTRAN.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.