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

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

news.ycombinator.com

Post reply on HN
Print view View original

261–270 of 538 posts

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

#261

Post by mmphosis »

"4 years in" I am not sure what "in" means, but I started getting paid for programming in 1984. So, what do I wish I knew in 1988?

I think you already said it: "I'm also realizing there's SO much more to learn."

Don't stop learning. It was probably around 1988 when someone suggested I look into Lisp and I dismissed the comment at the time, although I did look into AI. I do wish I had known more about Lisp, not necessarily programming in Lisp, but just the knowledge of the concepts that come out of learning Lisp: garbage collection, stacks, lists, trees, macros (not the terrible C macros I was using at the time but Lisp macros), parsing, code generation, profiling, the benefit of programming in a more functional way, and I am probably missing a lot of things here I take for granted. Don't stop learning.

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

#262

Post by kexari »

ravenstine wrote: post #247

Everyone's code basically sucks, including yours. The boundary between a beginner and a coding rockstar really isn't very great unless you are getting into the realm of computer sciences, like machine learning. Learn from your seemingly smarter peers, but don't idolize them. Chances are they will leave the company long before you do, and you will figure out that their coding skills aren't all they are cracked up to b…

Totally agree on the personality and grooming points you made. You need to be good at making people know exactly what you have achieved. Shout about it on slack, fire up google docs and write some brief documentation on a new feature you implemented. Others within the company won't be actively looking at your contributions. They will notice who stands out, who is taking initiative and touching base regularly. Unfortunately this trumps true programming talent in startups - EVEN if you are one of the gods.

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

#263

Post by pjmlp »

pacaro wrote: post #193
scarface74 wrote: post #68

I have been developing professionally for 20 years and I'm in my early 40s. What I've learned: * Salary compression is real: most companies are not going to keep giving you raises to match what the market would give you for your skills. They would rather you leave and take all of the institutional knowledge with you than pay you the amount you could get elsewhere. Even if that means hiring someone else at market valu…

Having to move to get promoted is frustrating and real. Within large companies you can usually move to another team (how hard this is varies), but it is typically required that this be a lateral move, which then slows velocity, whereas changing companies would not normally be a lateral move. I'm cautious of the word "Architect" — even though I've had it in my job title in the past, and still believe that it can mean…

Lateral moves inside a large company are a good way to improve a CV.

It is easier to get "hired" for new technology stacks because some people in the company already know you, instead of random HR guy that doesn't care about technologies used in side projects, only what was used on your very last project at work.

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

#265

Post by jrumbut »

ransom1538 wrote: post #215

13 years. 0) Money. the big money is in projects that need help. E.g. CEO during your interview: "The last lead programmer flipped me off and our accounting system in small talk is broken." That's hard. But that is where money is. 2) errors happen. Do tdd - so you can go to that concert. 2) Be the go to guy. If someone needs something you better be able to help. Brushing someone off creates office enemies and will re…

I really like this response because it is helpful and practical but not overwhelmingly cynical or Machiavellian. You can do well by doing right in this field!

I think a corollary to 0 is that if an organization is in trouble it will usually find a way to always be in trouble. It's human nature to think a crisis is always almost over, often it's only beginning.

For sure, taking over a troubled project is a great and honest way to make money, and I love sorting out tangled messes where the original developers have all left (hit me up if you've got one, email in profile!), but just make sure that the problem wasn't a chaotic or toxic work environment.

People and their interactions are more important than events and circumstances in terms of creating an environment. Some teams run on crisis and others run on collegiality. The direct and indirect benefits of a positive work environment are tremendous.

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

#266

Post by antoniuschan99 »

qaid wrote: post #201
i336_ wrote: post #145

Earlier quoted context omitted.

Here's my problem. I'm not particularly prolific, so the number of ideas I have far outweighs my execution so far. This is mostly due to ADHD and other issues which I'm working on fixing, and while contextually relevant is not my point. This lack of prolific-ness means that I have a literal tower (it's rather intimidating) of wanting to build cute but objectively not so useful routines simply for the sake of building…

Your "problem" sounds different the one I currently deal with. My current solution is to have a backlog and spending time to prioritize them. I'd focus on my top priority, and continue writing down new ideas as they come into my mind. When I finish with the top priority, I re-evaluate to find out where the recent ideas fit in. I'd also look into reading about the agile methodology. If you're like me, ideas come in ve…

Like the work you deliver to your boss or client, there is a Final Product.

And yes, Agile is the best, because it's of the mindset that the Product is iterative!

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

#268

Post by antoniuschan99 »

gm-conspiracy wrote: post #234
qaid wrote: post #201

Earlier quoted context omitted.

Your "problem" sounds different the one I currently deal with. My current solution is to have a backlog and spending time to prioritize them. I'd focus on my top priority, and continue writing down new ideas as they come into my mind. When I finish with the top priority, I re-evaluate to find out where the recent ideas fit in. I'd also look into reading about the agile methodology. If you're like me, ideas come in ve…

Also, "freeze" your "features" at versioned levels for each project. If you want to add or alter something, that would be a new project. Otherwise, you will never finish a project.

eg. "Sprints" in Agile

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

#269

Post by bitL »

MaybiusStrip wrote: post #260
bitL wrote: post #56

There is no future in software development as a job. Move to a management position quickly, network, make friends with decision makers, don't spend too much time on crafting your skills, your reward for perfection will be more insane work and crazy interviews where one part not 100% done kicks you out. Work on your appearance, kiss up, lift, dress properly, use anti-aging cosmetics, make cool looking hairstyle, wear…

This is like reading advice from an alternate reality. Almost all the VPs, senior managers, principals, etc. that I've encountered in my career are poorly-dressed nerds, not ring-wearing, macho douchebags. If you are a politician in software, you will eventually get found out by someone competent and get the boot. The only way you can succeed as a politicking fraud is to hop jobs every-time the people around realize…

I agree it's a pathetic existence, which is why I am stating it plainly here as our field is becoming exactly as "any other field" quickly. You'd be surprised what goes on behind the scenes at the top level of most tech companies... Most boards of directors are comprised of non-tech members, bringing their own distortions everywhere. The only force we had was the pace of innovation, and that is no longer happening so massively in software as we reached the end of Moore's law, and only few bright spots are still on like AI/ML/robotics where companies can't afford to cross the "bozo event horizon".

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

#270

Post by scriptkiddy »

avaer wrote: post #15

- Keep it simple, stupid. Advanced is not a compliment. - Languages and frameworks don't matter. There's a closed set of concepts they're all reusing. Especially if it's hot shit: that means someone mined ideas from 30 years ago. - Most problems tend to fall not to cleverness, but to compute power and the right glue. See previous two points. - Everything is a tradeoff, everything is a moving target. Programming is ab…

I like this. No bullshit. Straight to the point. Solid advice.
Post reply on HN