3 ms·
Don't call yourself a programmer, and other career advice (2011)
- gnabgib 10mo agoPopular in: 2022 (245 points, 162 comments) https://news.ycombinator.com/item?id=34095775 https://news.ycombinator.com/item?id=34095775 2021 (71 points, 89 comments) https://news.ycombinator.com/item?id=28234937 https://news.ycombinator.com/item?id=28234937 2019 (570 points, 307 comments) https://news.ycombinator.com/item?id=21303181 https://news.ycombinator.com/item?id=21303181 2016 (154 points, 147 comments) https://news.ycombinator.com/item?id=12548043 https://news.ycombinator.com/item?id=12548043 2014 (102 points, 44 comments) https://news.ycombinator.com/item?id=8147008 https://news.ycombinator.com/item?id=8147008 2012 (51 points, 46 comments) https://news.ycombinator.com/item?id=4822015 https://news.ycombinator.com/item?id=4822015 2011 (1021 points, 270 comments) https://news.ycombinator.com/item?id=3170766 https://news.ycombinator.com/item?id=3170766
- throwatdem12311 10mo agoFunny, because in Canada “engineer” (the term used with zero abandon in TFA) is a regulated term and calling yourself an engineer in a professional setting when you are not licensed can get you a nice 50k fine. I’ve only met one programmer in my entire life who actually was licensed engineer. I call myself a “computer systems architect and implementation specialist”, which won’t get me in trouble and uses buzzwords that mostly describes my day-to-day at my own $DAY_JOB. But come on, let’s be real - I’m a programmer.