Hacker News new | past | comments | ask | show | jobs | submit login

So here's my problem with this. There is no bricklaying in software. If something is really repetitive and mind-numbing it should be automated. That is the difference between software engineering and engineering/construction—the computer does all the rote work.

I get that there are amazing semi-technical managers and UX people who add outsize value even though they don't code—I don't subscribe to the SV worship of "hard skills". However, SV is also full of jackass wantrepreneurs who think they don't need to learn how to code because their singular vision is so valuable. These "idea guys" are the antithesis of what it takes to build a successful startup, and I worry that defining Product Engineer this way just gives them another place to hang their hat and further their own preciousness.

"Engineer" should be reserved for someone who codes or at least administers technical systems hands on. I'm well aware that traditional engineering disciplines look down their nose at programmers for declaring themselves engineers with such informal practices, but nevertheless software engineering is a thing with its own challenges (in many ways more difficult than physical engineering due to the breadth of scale and lack of constraints). Why do we need to water it down when we already have terms like Product Manager or UX Designer?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: