Don’t let him in the club.

Undersigned, Prompt Engineer.

The boot camp morons usually don’t make it past six months in my experience

Professional engineering is really about implementing processes and procedures that create reliable and dependable systems. Ultimately it’s about responsibility and risk management. Being an engineer has nothing to do with understanding or implementing technology or technical details and specifications (unless you are in an extremely junior level engineering position). That work already has another title: that’s called being a technologist (and there ain’t nothing wrong with that title and that work).

Very, very, very few technologists (including self-taught programmers, computer scientists, and even some engineering grads) have, or even understand the skills needed to manage technical risk, simply because those skills are not part of any of those curriculums and the licensure required to be recognized to conduct those activities. It requires knowledge, training, and certification specifically, not just a university degree or x years on the job. Of course, it’s not the sort of distinction that the general public understands by “engineering” since the public kind of just takes the act of technical risk management for granted.

Conversely, it’s perhaps also why the number of engineers with hands-on skills is shockingly lower than we expect: using technology is not on the engineering curriculum.

But yeah, just because the general public confuses technical skills with engineering doesn’t give you, lacking all three of : an accredited engineering degree, an engineering licence, and perhaps most importantly, malpractice insurance, licence to call yourself an engineer.

Not following this one. Are we talking about dual booting or is this some military thing that I’m too non-combatant to understand?

Computer science is not engineering. Neither is software engineering.