3 ms·
Why not? If someone hires you to be an engineer and you succeed, then go for it. In the end I think what matters most in what you call yourself is the confidenc
by jlas 13y ago
Why not? If someone hires you to be an engineer and you succeed, then go for it. In the end I think what matters most in what you call yourself is the confidence you have in your skills.
- afandian 13y agoBecause 'Engineer' is a regulated / protected term in a lot of places. You can get in big trouble calling yourself an 'engineer'. There's a whole debate about this. http://en.wikipedia.org/wiki/Software_engineer#Use_of_the_title_.22Engineer.22 http://en.wikipedia.org/wiki/Software_engineer#Use_of_the_ti...
- kamjam 13y agoI take your point, but I think it depends on where you work. I used to be a "web developer", I still consider myself that (I don't particularly care what my title is tbh). When I started job hunting a few years back companies (in the UK) were advertising for "Software Engineers". I didn't want to sell myself as subpar so my job titles got rewritten on my CV to help market myself. At some point, the term "web developer" got associated with people just "messing around" with non-serious tech, scripted languages for example were seen as for people just starting out and not serious, whereas any serious "software engineer" would use OOP, design principles and frameworks. This is amongst people I worked with, so by no means a reflection of whole industry.
- afandian 13y agoCertainly it does. I used to be a Software Engineer. I'm now a Developer. I've got a new job lined up where I'm going to be an R&D Programmer. I'm still the same person (although the work will be slightly different in each case). I wasn't prescribing either way, I was just answering your question.