Ask Slashdot: What Do You Wish You'd Known Starting Out As a Programmer?
snydeq writes: Most of us gave little thought to the "career" aspect of programming when starting out, but here we are, battle-hardened by hard-learned lessons, slouching our way through decades at the console, wishing perhaps that we had recognized the long road ahead when we started. What advice might we give to our younger self, or to younger selves coming to programming just now? Andrew C. Oliver offers several insights he gave little thought to when first coding: "Back then, I simply loved to code and could have cared less about my 'career' or about playing well with others. I could have saved myself a ton of trouble if I'd just followed a few simple practices." What are yours?
What Do You Wish You'd Known Starting Out As a Programmer?
How to program, I guess.
"Our two-party system is like a bowl of shit looking at itself in a mirror." - Lewis Black
That people who use spaces for indentation are just WRONG. :)
I like you, Stuart. You're not like everyone else, here, at Slashdot.
Going by my wife's experience, I can suggest a better way to discourage somebody from learning to code. It's called Java.
I write sci-fi for metalheads
SF still sucks, depending on which side of the glory hole you sit.
Copyright (c) 1990 - 2014 Dice. All rights reserved. Use of this comment is subject to certain Terms and Conditions.
Assembly on a 68000 is easy. In my days, we had to build our own opcodes from rocks, uphill, in the middle of winter. Good thing we had onions on our belt though, because that was the "in" thing back in the olden days. ...what was I talking about?
Get free satoshi (Bitcoin) and Dogecoins
Unions are not that hard to understand. You see, unions have layers, just like ogres.
Get free satoshi (Bitcoin) and Dogecoins
It seems like it might work better to say, "San Francisco still sucks-- which might not be so bad, depending on which side of the glory hole you sit."