7) Don't call people engineers when the appropriate term is "developer" or "programmer"
Personally I think engineer is a better term than "programmer".
Things a Non-Engineer Should Know Before Founding a Web Startup
11–20 of 52 posts
Re: Things a Non-Engineer Should Know Before Founding a Web Startup
#127) Don't call people engineers when the appropriate term is "developer" or "programmer"
Personally I think engineer is a better term than "programmer".
Re: Things a Non-Engineer Should Know Before Founding a Web Startup
#13Re: Things a Non-Engineer Should Know Before Founding a Web Startup
#14Earlier quoted context omitted.
Personally I think engineer is a better term than "programmer".
I disagree. I don't find many similarities between what I do and what a "real engineer" does. I do not consider myself an engineer; I write software. Nowhere in the 18 years I've been doing this for money have I met anybody that could explain what software engineering really is. Without a definition, the term to me is meaningless.
That's what they'll teach you at engineering school. Not everyone who is writing software is engineering.
Re: Things a Non-Engineer Should Know Before Founding a Web Startup
#15Earlier quoted context omitted.
Personally I think engineer is a better term than "programmer".
Engineers precisely specify a problem and then build a solution that's correct to within a tolerance. I'm afraid I don't see the resemblance to programming.
Re: Things a Non-Engineer Should Know Before Founding a Web Startup
#16"Non-engineers are not 'designers' by default." Amen to that. This would be a great subject for its own post.
Re: Things a Non-Engineer Should Know Before Founding a Web Startup
#17Re: Things a Non-Engineer Should Know Before Founding a Web Startup
#187) Don't call people engineers when the appropriate term is "developer" or "programmer"
Re: Things a Non-Engineer Should Know Before Founding a Web Startup
#19Earlier quoted context omitted.
Personally I think engineer is a better term than "programmer".
Engineers precisely specify a problem and then build a solution that's correct to within a tolerance. I'm afraid I don't see the resemblance to programming.