![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
I don’t think it’s bad, in fact I wonder the same. These are my colleagues because it’s the same path I took - I now work developing self-driving cars (I slowly transitioned from aerospace to manufacturing automation to robotics) and it’s the most rewarding job I’ve ever had, and it feels very much like engineering. I don’t care if I’m not a “manufacturing engineer” anymore; I really like my job and I like my title to reflect somewhat accurately what I do, but that’s the extent I care about it.
I believe so. I have some roles in my team I’m hiring for, that have reading code and fixing small bugs as one of the requirements, but not developing code from scratch. (It’s a sort-of field engineering role).
We do test for both things (treating the “developing code from scratch” as bonus points rather than a strict pass/fail) and some people can find and fix bugs in a couple minutes, but are incapable of writing some basic python to iterate through prime numbers and store them in an array.