3 ms·
This is an advice article for engineers written by two people who are not engineers. That's not necessarily bad, it's good to have outside perspective. But I di
by reidjs 5y ago
This is an advice article for engineers written by two people who are not engineers. That's not necessarily bad, it's good to have outside perspective. But I didn't find the article particularly helpful. It makes some strange, vague analogies to watersheds and doesn't give much actionable advice. This article feels like an advertisement for this company's workshops or seminars.
- znpy 5y agoHi, I'm calling BS on your reply. One of the authors (Karen Sun) is the CTO of a tech company. Also I had the chance of working with her (for her, really) and I can tell you that A) she's definitely an engineer and B) she knows her way around code and stuff.
- reidjs 5y agoI'm sure she's very intelligent and is probably great at coding. All I meant by that comment is that she is not currently a software engineer by title, she is a CTO, and the stuff mentioned in the article may be more relevant to founders/CTOs.
- database_lost 5y agoSorry, but being an engineer is different than knowing your way around "code and stuff". Being an engineer is also different than being a computer scientist or programmer. The authors studied arts and mathematics, but that didn't stop them from starting the post by making it look like its written by engineers: "Early in our careers as engineers, we’re told to invest in technical skills."
- MattGaiser 5y agoThe links of the author names go to LinkedIn and Karen Sun is definitely technical. Heavily founder type technical so I suspect that skews the advice in that direction, but still.
- pxeger1 5y agoYeah, I think[?] I agree with the point this is making, but the watershed "analogy" is quite a stretch. This article is not very well-written. ...and I'm not even sure if I agree, because it's quite hard to extract the actual point