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

If you see yourself as a software developer instead of problem solver, you tend to solve all your problems by writing code. In many cases problems can be solved by adjusting processes, improving culture, education or just by learning to use the current tools in more efficient ways.

Heh. It's much easier to write a kludge and patch it 500 times than perform a culture change at my place. I'll get rewarded for "fixing" the application and be seen as valuable in the former, and quite easily despised in the latter.

Solving technical problems is, unfortunately, usually far easier than solving people and political problems.

Computers do what you tell them to, most of the time.

"Developer" rather than mere "coder" should mean you're aware of the full import of the system from requirement to end user deployment and production. Sometimes it does.

Enter the insane notion of separating developers from end users. You have sales and managers talking to customers, then writing you a half-assed specification that's broken and illogical because they're not trained in noticing general ideas behind specific points. sigh.

To be fair, extracting coherent requirements has pretty much always been the problem.

True, but it's good to at least have someone deeply technical on the discussion too, just for the ability to come up with generalizations and - after presenting them to the customer - to confirm whether they're sound, or whether the customer has a completely different model in their head.

It's easier to do that with the customer than with the spec - specifications can't talk back to you.

Applications are open for YC Summer 2021

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