Live data from Hacker News

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

news.ycombinator.com

141–150 of 538 posts

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

#141
post #131
post #81

Earlier quoted context omitted.

I followed the call of an employee with 10yrs more experience than I have and he proposed we move our infrastructure towards docker containers for easier deployment / management. Generally containerization of our app was a good step at this point, but we made the mistake to also put redis / postgresql into docker, which obviously is an stupid idea if you're trying to scale things. On top of that, docker networking wa…

Thank you for the thorough reply!

:)

It was a nice exercise to put our struggles w/ docker into a coherent point.

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

#142
post #113

Earlier quoted context omitted.

> Work somewhere where software is the main product So a software company as opposed to working in an IT department - programming and solving problems that really _aren't_ interesting? That's one of the main things I crave these days (and I think it would make a big day-to-day difference) is to work at a software company as opposed to a company who leverages software.

It's even a money/salary issue. There is a huge difference between the CEO seeing you as someone who makes money for the company as opposed to just being an expense.

>It's even a money/salary issue.

Does this mean that you salary isn't increasing, or that you aren't valued at all?

I'm curious how most people receive or handle (or if raises are even a thing)

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

#143

Work somewhere where software is the main product and not just a cost center. You can learn a lot quickly if you do cutting edge things with people who care about technology and not just cost. Solve real world​ problems. Doing elegant things is very difficult because the real world is much more convoluted than theory. Do a few things in depth. Don't jump at the latest thing every few months.

> Work somewhere where software is the main product and not just a cost center. This is THE big difference between S/W dev and IT. For 20 years I worked in the former, and for the past 10 in the latter. No question about it: IT is hell. Theirs is a never-ending mission to reduce the cost of moving data and being "compliant" with often-meaningless ever-excessive corporate standards (and forever meaningless MBA/CIO fad…

"senior mgt. compels the CIO to adopt meaningless surrogate goals because IT's actual mission isn't sexy enough. So for the next six months IT adopts "Platforms" or trains half the staff in Six Sigma, or outsources, or insources, or promotes of whatever other CIO groupthink initiative is in vogue at the moment."

That describes exactly the IT department in my company.

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

#144
post #113

Work somewhere where software is the main product and not just a cost center. You can learn a lot quickly if you do cutting edge things with people who care about technology and not just cost. Solve real world​ problems. Doing elegant things is very difficult because the real world is much more convoluted than theory. Do a few things in depth. Don't jump at the latest thing every few months.

> Work somewhere where software is the main product So a software company as opposed to working in an IT department - programming and solving problems that really _aren't_ interesting? That's one of the main things I crave these days (and I think it would make a big day-to-day difference) is to work at a software company as opposed to a company who leverages software.

You want to be in a profit center, not a cost center.

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

#145

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…

This. Make your _business_ case, not a technical case. This applies to software engineering, security engineering, etc. The above comment does not absolve you from doing cool things, it's just that the cool things should align with business interests. No yak shaving. Sometimes writing a one-off script will take 30 minutes, and doing it by hand will take 10. Do it by hand.

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 them.

I realize this is essentially the foundation of creativity, but I have a hard time justifying doing these things as I take a very long time to execute anything.

So, the ideas file themselves away - and surface when I'm trying to design actual things I'd like to build. And I get horribly distracted with doing X or Y a certain way, or I get carried away with how I can build Z out like this or that idea I had two years ago...

My problem is focus, I think, and mental partitioning, which I'm not good at. Does anyone have any suggestions for how I can do that?

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

#146

I spent a long time never bothering to master semi-advanced text editor or ide features. Like really simple stuff like moving forward/back by a word at a time, deleting a word at a time, hopping to next/prev brace/paren, renaming globally, doing everything without needing the mouse, multi-select etc. You can go even deeper and get into deep VIM style skills but there are many very easy things to learn that let you do…

Okay, so as someone who is less than 4 years into programming what are the key common shortcuts(not they're actual hotkeys just which ones are used the most) to learn for semi-advanced text editors and IDE's?

EDIT: thanks for the advice guys, I use Jet Brains range of IDE's for school cause free licensing and I'm using VS for my summer internship. I'll look into emacs though, thanks for the suggestion!

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

#147
Learn how to work with other people effectively (not just programmers, but PMs, finance types, legal experts, etc.) Took me like 15 years to be any good at this at all.

Get exposure to customers. Try to get involved with decisions involving them. Many companies actively discourage engineers from having customer contact; this is bad, IMHO.

Get exposure to the financial side of whatever industry you're in. You don't need to do official work, but definitely make sure you understand how your company makes money and what its risks are. (Do a start-up or two; this will give you a visceral feel for what money is worth assuming the places you work at are run well).

Read a paper a week (e.g., something from usenix or the ACM, or whereever). Sites like The Morning Paper (https://blog.acolyer.org/) are pretty good; the thing is not to get caught in a rut.

If you're doing IT work, get involved in dev work. If you're doing dev work, get involved in IT. These feed pretty heavily off of each other and operational background will boost your engineering skills as much as coding skills will help your IT work.

Things I wish I'd studied harder, earlier: Statistics, practical aspects of databases and SQL, at-scale networking [didn't exist when I was a sprout], practical aspects of operating systems implementation (the stuff they didn't teach you in your course at school), maybe the first six months of an EE course . . . I could go on for quite a while. The good news is that there's no way you'll run out of stuff to learn, not in your entire career, and it's all (usually) applicable at some point.

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

#148

Earlier quoted context omitted.

Also there are differences in further employment perspectives. I mean if you have a problem to solve and you have a choice to use some old tech that you already know, but it is going out fashion, and some new one, then the choice of the newer one improves your employability in the future. For example, I guess in 2000 there was not that much people with 5 years of experience of using Java in production, but those who…

That is true and can be a problem when recruiters just keyword match technologies from your CV. When I've recruited I've always tried to assess the candidate on ability to get things done rather than knowing a specific framework. I'd look at how deep their knowledge goes and see if they can ship stuff - if they've been using jQuery but I need React then I'm not too fussed if they've shipped quality products using jQu…

[deleted]

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

#149
post #84

I've been coding professionally for 20 years, a lot of the comments below are legit, but I figured I'd add one or two more: - As many people point out, the languages don't matter - something better and newer will come along, and you'll need to adapt, but that's not where programmers provide value - they provide value in understanding how to solve the problems that the business side is facing. It's easy to find someon…

>To me, the most important thing, is to try to work for an organization where you are the dumbest person in the room. It might sound counter intuitive, but if you are the smartest person there, who are you going to grow from?

In my experience, this can go either way. I worked for an organization where our team were the "lowest" in rank. The end result was:

1. Everything boring gets piled onto you because those senior to you have "better things to do to earn their high salaries"

2. You don't learn much from doing boring things.

3. There are enough boring things in an organization that if you want to take on more challenging work, you'll burn out (they expect you to keep doing the boring stuff - it's mission critical).

4. They were really not interested in your growth. When you hire a janitor for your business, you do not really care about his/her career growth. If you're in the bottom rung of an organization, they may view you as the janitor.

Occasionally people did rise, after an intense amount of effort. But most learned that the smarter move was to move to a different job.

Knowing where you are in the organizational picture is important. In my bottom-of-the-rung job, I solved more challenging problems that required more advanced knowledge than I do now. Yet I get paid more than those in my previous job, and career prospects are better.

We often fall into the trap of thinking solving challenging problems equates to better pay/career. But I suspect your position in the organization is as much a factor. When I changed jobs, I was no longer at the bottom, and I got to pass boring tasks to other teams lower than me.

My advice: From a career perspective, it's usually a bad idea to be at the bottom of an org (even if you have a PhD) - no matter how interesting the work.

Also, no matter how smart you are, if you're on the bottom, people won't listen to you. Simply by being a little higher in the org chart makes people listen to you.

Post reply on HN