Live data from Hacker News

Things a Non-Engineer Should Know Before Founding a Web Startup

blog.wepay.com

31–40 of 52 posts

Re: Things a Non-Engineer Should Know Before Founding a Web Startup

#31
post #29

Along with "don't pretend to be more technical than you are", I would add "Trust the engineer/dev/ux guy/programmer to do what you hired them to do". I had the experience (that I imagine a lot of people share) of being hired by a non-technical founder in a start-up, who then wanted to micro-manage and give input on every minute decision that went into the building of the UI, even to the detrement of the user experien…

That should actually be #7, I think - I'll add it if I get the chance. I started off like the person you describe, and I have since moved pretty far in the opposite direction.

I've not yet been in the management position, but I definitely don't think it's an easy thing to do. It requires the loss of some control, and putting your neck out on the line, but when you've hired the person equipped for the job, it's ultimately best.

Re: Things a Non-Engineer Should Know Before Founding a Web Startup

#33

"From what I can tell, nothing is more frustrating to an engineer than a non-engineer asking for something complex, and treating it like it’s trivial." Yes, yes, and more yes. When programmers say "possible," they mean before the heat death of the universe. That doesn't mean all possible things are automatically trivial, despite their apparent obviousness.

When programmers say "possible," they mean before the heat death of the universe.

I said possible, but I never agreed to that schedule!

Re: Things a Non-Engineer Should Know Before Founding a Web Startup

#34
post #6

Earlier 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.

You could describe programming that way too, though the "within a tolerance" would probably have to be about input coverage rather than output/behavior.

Re: Things a Non-Engineer Should Know Before Founding a Web Startup

#35
post #5

7) Don't call people engineers when the appropriate term is "developer" or "programmer"

If you apply cleverness to solve problems, you're an engineer. Engineering is the verb form of ingenious.

When you're talking about a profession though, engineer means something very specific. It means that you're trained and licensed and can be held legally responsible if whatever you're building should malfunction. Referring to your profession as an engineer when you don't meet those criteria is a bit disingenuous. It's akin to the difference between calling yourself a doctor because you went to medical school, and calling yourself a doctor because you got a PhD in english lit.

Re: Things a Non-Engineer Should Know Before Founding a Web Startup

#39
post #37

I did not see it in the post: who wrote this? It's in the first person, but I don't see any attribution.

me :)

I was wondering as well :) Maybe you could just slap on a different wp theme (one that shows the post author)?

Re: Things a Non-Engineer Should Know Before Founding a Web Startup

#40
post #33

"From what I can tell, nothing is more frustrating to an engineer than a non-engineer asking for something complex, and treating it like it’s trivial." Yes, yes, and more yes. When programmers say "possible," they mean before the heat death of the universe. That doesn't mean all possible things are automatically trivial, despite their apparent obviousness.

When programmers say "possible," they mean before the heat death of the universe. I said possible , but I never agreed to that schedule!

...let there be light?
Post reply on HN