Live data from Hacker News

Ask HN: For those programming 10+ years, what do you wish you knew 4 years in?

news.ycombinator.com

41–50 of 538 posts

Re: Ask HN: For those programming 10+ years, what do you wish you knew 4 years in?

#41
"Clever" usually ends up being a negative word when it comes to programming solutions. "Elegant" and "simple" are far more important. Keep searching until you find a solution that feels elegant and simple. If you're sure there is none, only then write clever solutions.

I also wish I had known to buy some Bitcoin.

Re: Ask HN: For those programming 10+ years, what do you wish you knew 4 years in?

#42
post #12

- Don't stress about code coverage metrics. - Don't use the next big thing before actually understanding the benefits only because someone else tells you to. (Looking at you, Angular and Docker!) - Stay away from programmers who have strong opinions about certain things. Most of them can't back them up with skill.

- Don't use the next big thing before actually understanding the benefits only because someone else tells you to. (Looking at you, Angular and Docker!)

I'm curious, what do you not like about Docker?

Re: Ask HN: For those programming 10+ years, what do you wish you knew 4 years in?

#43
Separate the code you do for work (delivering a product/service) from the code you use for learning and experimenting.

Keep your work code as simple as humanly possible.

Do your experimentation elsewhere (using the time gained by keeping your work code simple).

Your future-self, your co-workers, and your client will be grateful.

Re: Ask HN: For those programming 10+ years, what do you wish you knew 4 years in?

#45
post #36

If I could go back in time and give myself advice it would be: 0) Nothing is too hard to do, no matter how much those doing it might seem like towering titans many levels above you, or how out of your reach it may seem. Nothing is too hard, there are only things that take time, and things that take more time. If you put in the work, those titans will be your peers before you realise it. Of course, you can't do everyt…

Regarding 2, how do you suggest I avoid "spinning my wheels and learning nothing"? Over the last 6 months I've becoming increasingly aware of this problem with me, but I don't know how to fix it.

Re: Ask HN: For those programming 10+ years, what do you wish you knew 4 years in?

#46

That shipping stable software that works and meets requirements is what people really want. In other words, what the non-tech business people want, or your customers want, is software that fixes their problems, makes their lives easier or makes them more money. It's easy for us programmers to become fixated on using a newer JS framework, a slightly tighter Java loop or the latest cool language. Took me a few years to…

I strongly agree.

However, there are special cases where you are exposed to a new technology which enables new outcomes.

I was fortunate enough to blunder into using the Web in '92 and Java in early '95 and they were tools where the "how" did matter quite a lot...

[NB I haven't touched Java in a dozen years or so]

Re: Ask HN: For those programming 10+ years, what do you wish you knew 4 years in?

#47
That you can learn anything the way you are learning programming - by reading, trying, failing, trying again, debugging, trying again... You want to have a successful software business? Learn business, not just programming! You want to grow your business? Learn marketing / growth hacking!

Re: Ask HN: For those programming 10+ years, what do you wish you knew 4 years in?

#48
~13 years in:

Spend your early career, to the maximum extent possible, in well-run organizations surrounded by supportive, skilled teams, so that you can optimize for skill growth and (secondarily at first, but growing over time) for individually attributable impact/ownership.

Honorable mention: AppAmaGooBookSoft hire mere mortals, too, and mid-career salary expectations at them are $300k.

Re: Ask HN: For those programming 10+ years, what do you wish you knew 4 years in?

#49
build it to work first, then refactor the code to be pleasant. You often learn so much about the problem while getting even a rudimentary spaghetti code implementation working that you couldn't possibly have designed a comprehensive set of objects/interfaces up front, so get it running first, take what you learned about the problem and update the code to be readable and well-designed.

Re: Ask HN: For those programming 10+ years, what do you wish you knew 4 years in?

#50
- Use stable tools(language, IDE, frameworks etc) with proven track record

- Use tools and programming language that you personally enjoy, not the one trending on tech sites like Hacker News

- Focus on mastering at least one programming language

Post reply on HN