@nicemicro @BrodieOnLinux my experience with software development at universities says that we are still far away from even that being engineering.
University Profs / Postdocs / Assistants know a lot in their field, and make great stuff, but I've seen a lot of projects/people whose domain knowledge is on point, but their general software development process isn't all that great.
@yrlf @nicemicro @BrodieOnLinux the Computer Science program at my university taught the basics … of computer science. Might get you a start at an academic career or a taste of professional software development. But the quasi-commercial software lab in my school that had contracts with clients is where I learned how to work as a programmer.
Students: if you're in a coding boot camp right now -- great! You're probably okay. Computer Science? Get an internship. Now.
@progo my friends who got Comp Sci degrees are either working at the university or are doing the more esoteric parts of programming, like statistics on large data sets in the finance industry. Those guys earn much more than my Software Engineering graduate friends who develop "traditional" commercial software though.
But that's just a small sample in my friend group.
@yrlf @BrodieOnLinux in the corporate in-house software realm where I work, it's about the money. It's more cost effective to make mistakes and fix them than to do things the military or NASA way with the whole system proved correct before users ever see it.
Of course this "iterate with real users until it works" is not "engineering" IMO. I never liked having the term being used for this activity.
@BrodieOnLinux YES!
I was saying that the other day…
https://boop.city/@progo/114175410460543407
Linkedin wants me to call myself a software engineer. I've never once delivered a solution and said "I've already proved this is functional AND correct." I don't feel like an engineer.
Any of you all software engineers out there notice that on Linkedin the only thing that matches for the "I'm open to positions in …" field is "software engineering"? I remember 10 to 15 years ago, Linkedin had a SERIES of all-passwords data breaches. I think "engineering" is a stretch, to label what we do in general. I am not an engineer. I've never built a software system where I could say ahead of time "this will work. it is correct, and I have proved it."