It is different if people around you have good social skills on top of tech skills, but many people are not like that. A contact with community is important for motivation and having possibility to work with good quality people is indispensable. However, much of important learning happens when they are not in the room and they can not take control of keyboard and tell you solutions to problems before you had the chance to think.
What are some things you wish you knew when you started programming?
11–20 of 102 posts
Re: What are some things you wish you knew when you started programming?
#12Re: What are some things you wish you knew when you started programming?
#13 side effects are bad
code should follow data
it won't do what you intend until you've verified it
solve the problems you have, not the ones you anticipate you will haveRe: What are some things you wish you knew when you started programming?
#14Value your work, even if you think you are "still learning". I spent way too much time on under-market salaries writing good code. I wish someone had told me I could be earning 5x whilst still at uni.
Re: What are some things you wish you knew when you started programming?
#15Focus on maintainability above speed, terseness, or perfection. Worse is better (Your plans/thoughts on any matter are strictly inferior to your thinking after putting it into practice, so do not plan too much. Instead, experiment.
Re: What are some things you wish you knew when you started programming?
#16Re: What are some things you wish you knew when you started programming?
#17Use an IDE, not VIM
Re: What are some things you wish you knew when you started programming?
#18Staying at work longer won't help you produce more and better code. Sleep and exercise will.
People who get angry about technical choices like what framework to use or what coding style or how tightly to enforce rules will flame out. Don't be that person.
If you think you need to rewrite it from scratch, think again. Look up Chesterton's Fence.