11–20 of 176 posts
Don't call yourself an Engineer unless you are licensed to do so. Most states have a professional licensing board to oversee the practice of Engineering. Here's the link to the one in my home state of Indiana.[1] I've been a programmer, system administrator and a machinist. I've never called myself an engineer, and wouldn't want the criminal liability for doing so. I wouldn't call myself a "computer doctor" either fo…
>You are not defined by your chosen software stack: I recently asked via Twitter what young engineers wanted to know about careers. Many asked how to know what programming language or stack to study. It doesn’t matter. There you go. I generally agree with this point and many others in the article but when looking for a position the tech stack of a company you're interviewing with matters a whole lot. Using some older…
I see your point, but Facebook had large collection of code written in php(still is?), and they are far from having "lack of investment or interest in technology."
Don't call yourself an Engineer unless you are licensed to do so. Most states have a professional licensing board to oversee the practice of Engineering. Here's the link to the one in my home state of Indiana.[1] I've been a programmer, system administrator and a machinist. I've never called myself an engineer, and wouldn't want the criminal liability for doing so. I wouldn't call myself a "computer doctor" either fo…
Why would you give that advice when the job titles are all "xyz engineer"?
Earlier quoted context omitted.
I see your point, but Facebook had large collection of code written in php(still is?), and they are far from having "lack of investment or interest in technology."
To be fair back in the early 2000’s PHP was one of the best options.
Don't call yourself an Engineer unless you are licensed to do so. Most states have a professional licensing board to oversee the practice of Engineering. Here's the link to the one in my home state of Indiana.[1] I've been a programmer, system administrator and a machinist. I've never called myself an engineer, and wouldn't want the criminal liability for doing so. I wouldn't call myself a "computer doctor" either fo…
> Engineers in particular are usually very highly paid Cost Centers, which sets MBA’s optimization antennae to twitching disagree completely with this. I view scientists, engineers, programmers, and system administrators as a part of the profit center because they are intrinsically tied to value creation and value amplification.
>You are not defined by your chosen software stack: I recently asked via Twitter what young engineers wanted to know about careers. Many asked how to know what programming language or stack to study. It doesn’t matter. There you go. I generally agree with this point and many others in the article but when looking for a position the tech stack of a company you're interviewing with matters a whole lot. Using some older…
Not necessarily. Although many would consider C an older language, it's often the right language for the right job (e.g. network packet processing).
> Engineers in particular are usually very highly paid Cost Centers, which sets MBA’s optimization antennae to twitching disagree completely with this. I view scientists, engineers, programmers, and system administrators as a part of the profit center because they are intrinsically tied to value creation and value amplification.
For software companies, sure! Unless you're in DevOps or DevTools then you're a cost center again.
For an insurance company or restaurant, not as much. It depends on where the flow of money is.
Things are changing though, so this is less true over time as software continues to eat the world.
Boy this article is old isn’t it.