Hillel Wayne wrote a really excellent well researched article about software engineering compared to other forms of engineering a few years ago. It necessarily goes into a lot of this stuff but what emerges is that these definitions are regulatory and historical debris.
You don't need medical board or a bar to certify or constrain professional behavior and those organizations may not constrain as much as you assume anyway. The reasons we do have those institutions is as much a matter of historical accident as any modern need for it, and the reasons we don't have it for other high impact fields is pretty much an accident too.
And in a lot of the world software engineering does have professional certification and standards of practice. They still ship adware and racist loan denial algorithms too.
[–] jimbokun 1 day ago
[–] matkoniecz 1 day ago
[–] echelon 1 day ago
Every part of your existing job is transforming before your eyes.
If you cling to definitions and static roles, you're going to have a bad time.
[–] eikenberry 1 day ago
[–] SpicyLemonZest 1 day ago
[–] robot_jesus 1 day ago
[–] Der_Einzige 1 day ago
[–] tptacek 7 hours ago
[–] echelon 1 day ago
Systems design, architecture, database fundamentals, a bit of SRE. That matters. Not coding and syntax and toy problem solving with data structures and algorithms.
[–] SpicyLemonZest 1 day ago
My own experience is that coding, syntax, and some kinds of toy problem solving are important skills to use AI coding tools most effectively. I routinely get PRs these days whose descriptions seem plausible but are clearly wrong from a glance at the code, and I've had times when I'm unable to communicate to someone why a PR is wrong because they're not able to form a sufficiently detailed mental model of what it's doing.
[–] austin-cheney 1 day ago
[–] dcss_gardener 1 day ago
[–] Der_Einzige 1 day ago
Your definition would include Chiropractors as a profession. Such scum of the earth deserves nothing but contempt with extreme prejudice.