It's not like being a plumber or electrician where you learn once and can make a living all your life
What are some things you wish you knew when you started programming?
71–80 of 102 posts
Re: What are some things you wish you knew when you started programming?
#72The true language of computing is mathematics, and its power and beauty are masked to those who cannot speak it. Programming languages are powerful tools for communicating ideas and encoding the language of mathematics . You can use these tools to shovel bits around without understanding the language, but you won't be able to see or say much unless you become fluent. Creative expression comes with fluency, and fluenc…
Any recommendations of how to get at this as a self-taught programmer? I've picked up books on combinatorics and discrete math, but I still feel very far removed and don't know how to really take an interest and make the connection.
Re: What are some things you wish you knew when you started programming?
#73> 7. You don’t need 5 monitors. No, but more than one can work wonders for productivity if you are looking up documentation while coding, so you don't have to constantly alt-tab and forgetting where you were.
I think this one is really a horses-for-courses situation. For me, my current setup of two 2560x1440 monitors plus a 15" laptop is absolutely optimal - I can spread a load of stuff out everywhere, flip between a few spaces, and just generally be super-productive. I can still be productive working from just the laptop in a coffee shop, but I feel very constrained and find myself shuffling windows around to get stuff d…
To chime in anecdotally as a one-screen guy, for me it’s all about being able to unplug my laptop, switch locations, and not feel like my workflow’s crippled. I don’t like feeling anchored to my desk, or even the office as a whole.
Re: What are some things you wish you knew when you started programming?
#74Earlier quoted context omitted.
Any recommendations of how to get at this as a self-taught programmer? I've picked up books on combinatorics and discrete math, but I still feel very far removed and don't know how to really take an interest and make the connection.
See https://news.ycombinator.com/item?id=13904881
Thanks!
Re: What are some things you wish you knew when you started programming?
#75> 7. You don’t need 5 monitors. No, but more than one can work wonders for productivity if you are looking up documentation while coding, so you don't have to constantly alt-tab and forgetting where you were.
I think alt-tab is just a poor mechanism. With fast-switching virtual desktops, I find that the advantages of multiple monitors are quite small, though I still prefer to have two.
Re: What are some things you wish you knew when you started programming?
#76That unless you are in a pure code monkey position, programming is at most, 30% of the job and there is an array of skills that have nothing to do with programming that when mastered, will give the impression that you are an expert programmer.
I have some idea what you're hinting on but no entirely. Im in my 3rd year in and have seen a lot of bullshiting. Should I just learn to start bullshiting?
Is everything other than programming, "bullshitting"? Far from it. I am referring to a multifaceted spectrum of skills, no different than one every other non-technical professional has to contend with. Linguistic skills, logical fallacies (recognising other peoples' bullshit), arguing pro and contra, team dynamics, business knowledge (if you're in line of business software, which most of us will be in), testing (a science in itself)... and yes, the softer skills such as marketing yourself and trying to present your work in the best possible light.
I would also recommend learning how politics function in the workplace, if only so you can defend yourself from other peoples' black magic.
Re: What are some things you wish you knew when you started programming?
#77Anyone already said English?
Re: What are some things you wish you knew when you started programming?
#78Have anyone already said English?
Re: What are some things you wish you knew when you started programming?
#79Besides all the good technical advice already mentioned here I'd like to add some things I find very important, as I'm watching over the career progress of 2 junior developers.
Take VERY good care of your mental and physical health. Do not overwork yourself. It's a marathon and you will overcome most challenges with time and discipline. You don't have to be a genius/prodigy.
Don't put too much pressure on yourself - and it's hard not to due to all the praising of highly successful programmers - but nobody is an overnight success.
Enjoy your time off.
Re: What are some things you wish you knew when you started programming?
#80Earlier quoted context omitted.
"Chesterton's fence is the principle that reforms should not be made until the reasoning behind the existing state of affairs is understood." In the matter of reforming things, as distinct from deforming them, there is one plain and simple principle; a principle which will probably be called a paradox. There exists in such a case a certain institution or law; let us say, for the sake of simplicity, a fence or gate er…
Chesterton's Fence is a great example of why code comments are critical. If the code is doing something that isn't immediately obvious to a programmer on a deadline, there should be comments explaining why it's there. "Go away and think" just means the programmer who wrote it couldn't be bothered to take a couple of minutes to be clear, resulting in later programmers wasting hours or days (or worse) re-discovering th…
> "Go away and think" just means the programmer who wrote it couldn't be bothered to take a couple of minutes to be clear
I haven't had the luxury of working with a lot of experienced veterans, but I've seen and been burnt by rookies who couldn't be bothered to read code other people wrote or written without their favorite framework/language. No amount of comments would deflect those types.