Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Senior developers, what would you tell a younger you?

news.ycombinator.com

Post reply on HN
Print view View original

61–70 of 88 posts

Re: Ask HN: Senior developers, what would you tell a younger you?

#61

Post by typicalrunt »

GrinningFool wrote: post #45

* Some people will be hostile to you or your ideas. Maybe it will be personal, maybe not - but people can be ass-hats, so expect it. Don't waste a lot of energy on people who have no interest in exploring new ideas simply because they didn't come up with them. * there's always something to learn. You know that, but you'll lose sight of it. * look at the bigger picture, always * don't be afraid to ask questions, as ma…

Hmm, I'm replying to a comment... Oh well. :)

> you'll get paid more than you need to survive - so don't be an idiot with your money.

Adding to this is something to consider:

You will be paid more than you need to survive, but you will most likely survive longer than you will be paid. Make sure you save money for those times.

Re: Ask HN: Senior developers, what would you tell a younger you?

#64

Post by gt565k »

Deliver, deliver, and deliver some more.

And by that I mean be involved in projects from start to finish.

If you find yourself at a company for more than 2 years, and you've only worked on 1 boring project, it's time to look for new opportunities. Now, there could be multiple small projects as part of one big one, that's different, as long as it provides you value and helps you progress in your career.

The only way to progress as a software engineer and get a solid understanding of the SDLC[0] is to keep cranking out projects from start to finish.

There are far too many people that get stuck maintaining a project right out of college, and never experience the full SDLC.

The more projects you deliver from scratch, the better you'll be at estimating tasks, understanding risk, business priorities, etc...

[0] https://en.wikipedia.org/wiki/Systems_development_life_cycle

Re: Ask HN: Senior developers, what would you tell a younger you?

#65

Post by paulmooreparks »

* The technical decisions you make today will haunt you, or your replacement, for the next 20 years.

* Don't fall for the line, "We'll fix it later." It will never be "later," and the problems will never be fixed. Do it now, while it's cheaper.

Re: Ask HN: Senior developers, what would you tell a younger you?

#66

Post by AnimalMuppet »

tyingq wrote: post #62

If you have a family, strongly consider future you when you think about work-life balance decisions. I would gladly have traded off some of my career success for more family time...had I known then what I know now.

And be more mentally and emotionally present while at home.

Re: Ask HN: Senior developers, what would you tell a younger you?

#67

Post by AnimalMuppet »

There are toxic work environments. When you're in one, start looking and move to the first good alternative. Don't stay in something that's become a pit.

On the other hand, if you have a good situation (realistic management, decent pay, good co-workers), think very carefully before moving. Such situations are not all that common.

Re: Ask HN: Senior developers, what would you tell a younger you?

#69

Post by mywittyname »

jressey wrote: post #55

In the latter part of my career, I have focused more on mental health, happiness, and early retirement. The things below reflect that more than how to become 'great' or whatever. * Remember that people with non-software skills are probably just as smart and hardworking as you are * No matter how much more qualified you are than your coworkers, don't fight every battle even if they are always wrong * Actually read (do…

> * Remember that people with non-software skills are probably just as smart and hardworking as you are

And maybe/probably smarter.

One of the smartest people I ever worked with was a sales guy (gasp). The dude could spend 3 minutes listening to you explain something, instantly grasp the problem, have an idea of what the solution would look like, then communicate that to the customer in a way that made it look like we were doing them a huge favor. He had a non-technical degree and his background before joining our company was at a car dealership.

He once declared himself Master Lord Architect of All Things Technical after he figured out an issue to a problem in the span of a conversation that took three engineers the better part of a week.

I did not object.

Re: Ask HN: Senior developers, what would you tell a younger you?

#70

Post by cwisecarver »

* Learn how to learn.

* Admit when you don't know something and then rectify it (if it's interesting to you).

* A stable solution is better than the bleeding-edge solution.

* Smaller (simpler) is better. (KISS)

* Learn how to gauge technical ability in a conversation with someone and compensate for that on the fly. Non-techies will love you.

* 80hr weeks will not make the company love you. They will only make everyone else in your life dislike you. And eventually, the people at the company.

* Shop around. You don't have to take the job offers but keep interviewing. You learn as much about yourself as they learn about you.

* Find a problem-space you love and develop it. Tech is tech but business is business. Finding an area that you like to solve tech problems in will make you happy.

* Don't make technical arguments personal. Make your point, with facts, let them make theirs. Agree if you're wrong.

Post reply on HN