I am not a Software Engineer
huronbikes.mataroa.blog
I am not a Software Engineer
1–10 of 12 posts
Re: I am not a Software Engineer
#2I too am not a SWE. This confuses a lot of SWEs, recruiters, interviewers, etc.
My domain used to have a name, but that name got changed to something that has the word AI in it. And I don't really identify with that either, although I use parts of that.
Hacker (in the HN sense, obviously) actually captures fairly perfectly how I approach using computers/tech.
Good piece for those with such an identity crisis to re-find the word for it.
Re: I am not a Software Engineer
#3Re: I am not a Software Engineer
#4We need people like him.
We also need pragmatic efficient generalist software engineers who have a get shit done / FAFO mindset, accept the probabilistic nature of this enterprise and focus on what customers really need
(Hint: your customers don’t care about your beautiful TDD OOP SOLID DRY code)
Re: I am not a Software Engineer
#5Re: I am not a Software Engineer
#6If you don’t like AI then you should find a niche in software development that may still require rawdogging. I think kernel development and making hand crafted libraries are good options.
Product engineers will be more exposed to AI.
Re: I am not a Software Engineer
#7I don't know where he lives, but I am Canadian so I find it laughable that someone with a few-week bootcamp and a few years of on-the-job coding experience can call himself an engineer in the USA. In Canada "engineer" is a title with serious requirements and responsibilities. I don't see the Bay Area coder crowd rushing to take responsibilities like "if the bridge I design falls, I can be sued and/or lose my license.…
Re: I am not a Software Engineer
#8Throwing around vacuous accusations like this dilutes the effect of flagging real exploitation.
Re: I am not a Software Engineer
#9I don't know where he lives, but I am Canadian so I find it laughable that someone with a few-week bootcamp and a few years of on-the-job coding experience can call himself an engineer in the USA. In Canada "engineer" is a title with serious requirements and responsibilities. I don't see the Bay Area coder crowd rushing to take responsibilities like "if the bridge I design falls, I can be sued and/or lose my license.…
I find the American version far more attractive to my ideals. No fake credentials whatsover. And who ends up making better software? Americans.