Hacker News new | ask | show | jobs
by Alex-Programs 483 days ago
Practice.

Question whether what you're doing is the right way, or the easy way.

Participate and observe discussions. Learn by osmosis.

Refactor. Question your earlier assumptions. Which were correct, which weren't? What mistakes were foreseeable in retrospect? How would you do things differently?

Often the starting process of a refactor - working out what you'd change - is about 50% of the learning and 25% of the effort of actually doing it.

That said, I'm 18, I'm going through this process as well. There's a big difference between making something work and making something work properly.

1 comments

> There's a big difference between making something work and making something work properly.

In the real world is there? You make money by making things work not making things work properly.

Median tenure is like 2 years or thereabouts. In most cases you’re going to be long gone by the time any cost of not doing things The Right Way come due (if they ever do).

That said, I’m 45. I’d rather work with people who get things working rather than people who insist upon getting things working properly.