I started programming computers when I was very young. Because of the skills I developed, and because of some connections I had, I got a very high paying job in the data processing department of the Livermore School District while I was still a junior in high school. (I was on independent study at the time.) I literally made more money than I knew what to do with, unfortunately.
A couple of years later, I had been talking to a girl online, who lived in Florida. We met a few times. I've never been all that good at the relationship thing, so this seemed important to me at the time, so I moved to Florida. Shortly after getting there, I learned Oracle PL/SQL and another language I can't remember any more in the course of a few days to get a job at Ceridian Benefits Services; in time I became one of their lead techs with a path into their software development department. Again, more money than I knew what to do with.
After about a year of this though, things weren't working out, and there was a part of me that felt starved. It was the part that enjoyed hiking, enjoyed being outside, enjoyed being fit and in good physical health. I also had a strong feeling that everything up to this point had been too easy for me, that I wasn't getting as much out of life as I wanted to.
So I quit.
I moved back to California and resolved to spend the next few years starting over, completely from scratch; I wanted to take the hardest possible path through life for the next few years. (Boy, I had no idea what I was in for.)
I got into rock climbing, and then got a job as a climbing instructor. I had the opportunity, through my style, personality, will, and determination, to influence people around me. I made a lot of friends, many of whom I'm still friends with. I got to feed the outdoor side of my personality for a while. The job didn't pay much though, and eventually I fled, in debt, to a job in the retail part of the outdoor industry, in another part of the state.
During this time I didn't use computers, unless it was as a cash register or inventory system. For a period of a couple of years, I was completely disconnected from the internet, computers, toys, and gadgets. I learned how to fix cars, I chased sheep down the street, I climbed a lot, and I wandered around.
I'm back in computers now, obviously. It took me only about a year to catch up to the changes in the industry, and I'm one of the leading consultants in my area now, with a successful business of my own.
But, I'm really, really, really glad I took that road. It taught me so much that I couldn't have learned by staying behind a computer desk all day long. It taught me how to relate to people, for one. It taught me how to maintain some balance in my life, and how to pay attention to the needs of my spirit. (My girlfriend, who's reading this over my shoulder -- she's really patient with my need to hear myself talk! -- is reminding me that it's also how I met her, which is probably the best part of all. :-)
So my main point, in so much as I have one, is that abandoning your core skill in an area, and putting yourself in over your head for a while, can lead to some really valuable experiences. You don't need to worry about whether or not you'll still be able to get back in later, or re-acquire old skills; they'll come back, in time. Don't worry about that at all.
> It taught me so much that I couldn't have learned by staying behind a computer desk all day long. It taught me how to relate to people, for one.
The topic of relating to people always fascinates me. Would you say it is more about not facts but sharing feelings? What would you want to tell and teach your future son or daughter about relating to others? Thanks in advance.
OK, so, I've always been kinda cerebral, so communicating with people was something I had to "figure out". I'm not so much that way any more, but I do remember most of what I did to learn it.
It's definitely more about feelings than facts -- purely factual statements make a lot of people turn off to you -- but it's also about empathy. Not a new-age touchy-feely kind of empathy, but merely the ability to quickly understand the other person's habits, backgrounds, emotions, and personality. Think of it as learning to communicate in a different language, like speaking Russian to a Russian.
I studied some psychology, and although on the whole I think it was not terribly valuable, it did help me typecast people a little bit faster. For example, I tend to notice whether a person talks about what they think, or what they feel. If they say that they feel like x or y is right or wrong, then they're talking from an intuitive, emotional standpoint, and being all cerebral around them isn't going to get you very far.
There's also body language, the kinds of jokes a person tells, the sorts of phrases they use, and the dialect of language they use. I don't for example talk to boulderers the same way I'm talking now ... unless I want them to laugh at me. :-)
It started out as something I had to think about and study, but now it's intuitive and I don't think of it the same way anymore. It's just something I do.
I think this is a really valuable thing for other people to do; it would help communication between people a lot. There would be fewer misunderstandings.
Or, as my much-more-personable-and-outgoing girlfriend who again is reading over my shoulder says, "Well, yeah, it teaches you how to listen."
It's mostly inarticulable and learned through experience. If you're having trouble in this area, you'd probably benefit more from someone who can function as a coach to motivate you when you're down and to talk things over with, as opposed to looking for some kind of purely theoretical explanation.
I have to agree with Hexstream here (2 downvotes really?). A pithy overgeneralized saying proves nothing. Nearly every occupation benefits from a worker who can learn fast: lawyer, doctor, architect, CEO, salesmen, stock trader etc...
This is not specific to programmers and it is imaginable that a slow learning programmer with domain specific knowledge has value.
The most important aspects of a great programmer are:
The ability to learn what users need.
The ability to learn how a how a system works.
The ability to learn the cause of a bug.
The ability to learn from mistakes.
And the ability to solve complex problems.
Domain specific knowledge has some limited value but flexibility of thinking is far more important.
While fast learning per se is an asset in any field, however, in many occupations learning seems to be taken as a necessary evil that merely makes you wish you could do things like you used to and go on like that. You get trained to be something and when your field changes, you're forced to learn something new and you only do it then.
Programmers on the other hand—well, their job is to learn new stuff. Sometimes it's a new codebase, sometimes it's a new framework or library or language or protocol or a set of tools but there's always something new. The ultimate new thing is writing a program that hasn't existed before: everything is new. And even that new stuff doesn't have value per se, it's just a prerequisite for a programmer to "get things done". Stuff gets into the fashion and stuff becomes obsolete, but the programmer is riding on the front wave.
Not only good programmers have to be able to learn, they have to be able to learn fast. Programmers can't afford to take a six-month course to learn something new. If you can't learn new stuff and successfully map out the diffs of how it relates to stuff you already know, you're out soon.
As someone pointed out, while being able to learn also means that the programmer has undoubtedly learned a lot, I still argue that the value is indeed in the ability itself. A junior guy with the good programmer aptitude and ability to learn can bump himself into shape in a few years of time. Another programmer who has already learned a lot but who has lost the willingness to learn anything new is toast sooner than that.
Learning is implicit in the job of a programmer. When your job is to circle around the boundaries of unknown, it is something that you can't avoid.
I think the biggest reason why absorbing new knowledge quickly is a must when you are a programmer is that you are working for other people to be more productive in what they already know how to do, and if you can't understand their 'domain specific knowledge' as they try to impart it to you then you will have a hard time implementing something that will make them happy.
Yes, and what's more, if you have the ability to learn really fast and yet haven't accumulated much knowledge yet, one might wonder if you aren't lazy and wasting your potential.
he's a ceo type who attacked "job hoppers" as the worst kind of employees / "never hire them". this ties into the incident with calacanis labeling a gen-y ex-employee who had the audacity to quit his job a "flake"/"trophy kid".
i genuinely hate suster and calacanis. they're a big part of what makes me want to leave this fucking industry.
So stop reading them. That's the easiest way out, you get some time back that you can use in more productive ways too, and you lose absolutely nothing.
i should have added "and their type". a type i can't seem to avoid in my professional life.
confronting their mentality (by reading what they write, by reading what others write about what they write) feels productive. more productive than cultivating a kind of detachment towards 50+ hours of every week of my life.
but maybe it isn't - i'll give this a try. thanks.
Nice that you "genuinely hate me" given that you don't even know me. Very easily to "hate" people online you've never met. Harder in person where we don't easily fit some stereotype you have in your mind.
the specifics of your chronology really matter to me. i read this with a lot of personal interest, and i want an as clear as possible picture of what is possible.
17: data processing department; 19: florida; 20: quit; 22: returned to computers ?
what phase of the industry did all of this happen in? it seems like you've managed without a college degree?
I pulled up my resume to figure this out, since I kind of suck at anything time-related.
17 (almost 18): data processing department, starting in 1996; 20: Florida, in Summer 1999; quit almost exactly a year later, at 21; got my first computer job again at 25, in 2004. So it was actually a 4-year gap (!).
I left the computer industry just months before the big dot-com crash, but I was really burned out by then, and predicted the crash anyway. (IPOs had gotten completely out of control.)
And no, I don't have a college degree or much in the way of a college education at all, unfortunately. I'm really not proud of that, but I haven't been disciplined enough for college until more recently, and now I'm too busy and have other goals. I would never brag to anyone that "I've gotten this far without a college degree"; I'm not fond of that trend these days, and I do think that having at least some college education is very important.
That sounds good, but I worked hard enough to get a job in my field that pays me enough to live comfortably and have a good college savings plan for my daughter. What advice for those of us who did not have outstanding early success, good savings and obviously immense talent?
Hah! Uh ... I'm not at all qualified to ever give out advice to anyone else, especially someone I'm not very familiar with. So I have none!
Part of the misfortune with making money early on is that I never learned how to manage it, or save it, so I had no savings within a few months of leaving Florida. Having savings would have made a lot of the struggle much easier, but I don't think I would have learned as much, either.
I honestly would not say I have "immense talent"; that makes me kinda uncomfortable, actually. I'd say I have average talent, and immense determination, if anything.
Ah, but I'd take immense determination and (supposedly :) ) average talent over immense talent and low determination any time of day.
I had a classmate at high school and then at university that was the brightest student I ever saw at math. He could prove theorems in his sleep, and often did a different proof than the one taught "just for fun" (and giving teachers headaches).
Sadly his parents were quite rich and also a troubled family, so he went into recreational drugs, partying and D&D. Last time I saw him, he still hadn't finished university and had accomplished nothing with his life (well, he'd had a lot of girlfriends and partying AND D&D, so maybe he hadn't "wasted" time from his point of view)
That reminds me of the opening scene of 'idiocracy'.
I didn't downvote you, but I think that there is something missing here. Nobody that has ever brought a child in to the world had absolutely everything in order. And even if they thought they did they would have soon found out that it was not the case.
Then there is the period (pun not intended) between conception and delivery, in which a lot can change.
Waiting for the 'perfect time' is the best way to guarantee that you will never have children, there never is a perfect time, there will always be one more thing to fix.
Instead, if you want children, go for it while you are young, adaptable and have tons of energy. Worry about fixing problems if and when they appear. Try to do the best you possibly can and if you fail at something try to do it gracefully.
That is not a call to go and procreate if you for instance are not able to feed your kids or take care of them, but let's not overdo it on the having everything in order, that's a complete illusion.
My parents had 'everything in order' when they got me and my sister, fast forward 6 years and they had a very messy divorce, there are countless examples like that. And there are plenty of counterexamples too, of people that had a pretty tough life, decided to have children and simply did an amazing job of creating a place for them in the world.
"Then there is the period (pun not intended) between conception and delivery, in which a lot can change."
In the roughly three years between when I was conceived and shortly after my sister was born, my parents went from having 2 jobs and no kids to having no jobs and 2 kids. 1981-82 was a harsh recession.
Instead, if you want children, go for it while you are young, adaptable and have tons of energy.
I can appreciate the logic in that, but I'd caution anyone against jumping into a commitment of that magnitude before they've achieved some minimum threshold of maturity.
To illustrate my point, the rate of divorce declines rapidly as the age when married increases. In my experience, the same factors that contribute to a successful relationship also prepare (to the small degree that preparation is possible) a person for the utter, absolute responsibility and sacrifice that is parenthood.
i appreciate your answer, which i think is the best kind of answer people generally give.
but i want to ask you to consider something without any incredulity about my seriousness:
if you had not been born, you would not be bothered by not existing. and when eventually your parents die, they would no longer be bothered by not having had children.
> but i want to ask you to consider something without any incredulity about my seriousness:
Ok, that's fine with me.
> if you had not been born, you would not be bothered by not existing. and when eventually your parents die, they would no longer be bothered by not having had children.
Ah, ok, I get it now. Ok, I've 'considered' it, now what?
It's a bit too philosophical for me, you could ask anybody to 'consider' that and they would most likely land on 'but that isn't how it happened'.
Asking someone to consider some alternate reality and what their position would have been in that alternate reality is difficult stuff, at a minimum you'd have to concede that you can't really consider any 'alternative universes' simply because this is the one we've got.
So, in this universe, I exist, I'm happy I do and my parents, even though they probably made a wrong decision or two did have two kids.
The line of reasoning you are pursuing leads to either a very empty planet or to a planet with different people, two random specimens of which could be having this exact same conversation on a nodesloc called latest.zjoiner.com.
Ah, the void of non-existence is certainly filled with emptiness. It's what happens to the living that matters, though. Put another way, is Schrödinger's cat alive or dead? Does it matter if you don't intend to open the box?
The author said "live a _comfortable life_ and save for daughter's college". He chose _not_ to live a comfortable life and he should be chided for this.
Even if he could not save for his daughter's college, there are always other options available: scholarships, working while attending college, starting a community college and transferring (I did this for undergrad and paid my way through graduate school).
I voted you up (because your question deserves attention), but "only families with two six digit incomes and significant savings should have children" (what you need for a "comfortable life" while saving for a college educate) is a very scary argument to make. Note, I am _not_ saying families shouldn't hold off on children until basic financial situation is stable: you should still be able to provide a healthy life for yourself and your children, etc...
for the record, i don't think families with two six digit incomes should have children either. they're existence is dependent on the lives of people who do not earn six digit incomes, and so they are guilty of just as much misery in this world.
> for the record, i don't think families with two six digit incomes should have children either. they're existence is dependent on the lives of people who do not earn six digit incomes, and so they are guilty of just as much misery in this world.
That's a very odd comment. Two six digit incomes is a family of two engineers (2-5 years into their career) in Silicon Valley. Two $120,000-$150,000 incomes in Silicon Valley means "can afford a single family home, as long as both spouses are employed".
"They're" (I think you meant their) existence is not dependent on the lives of people who do not earn six digit incomes, amongst them are also people (doctors, engineers, scientists) who are making the lives of less fortunate much less miserable.
That also describes my parents and would very likely describe my own family (I've been earning a six digit income since two years out of college), so it's not something extra ordinary.
your existence is very much dependent on the lives of people who do not earn six digit incomes. take a good look at 99% of the objects you depend on. take a good look at 99% of the labour you depend on.
Because until you have children, you may think you have all your affairs in order, but once that baby comes, everything is out the window. The down votes are almost certainly from parents.
I did hang-gliding and spent a year building wooden boats. It's interesting how doing a deep dive into something totally different helps giving perspective on things.
I started programming computers when I was very young. Because of the skills I developed, and because of some connections I had, I got a very high paying job in the data processing department of the Livermore School District while I was still a junior in high school. (I was on independent study at the time.) I literally made more money than I knew what to do with, unfortunately.
A couple of years later, I had been talking to a girl online, who lived in Florida. We met a few times. I've never been all that good at the relationship thing, so this seemed important to me at the time, so I moved to Florida. Shortly after getting there, I learned Oracle PL/SQL and another language I can't remember any more in the course of a few days to get a job at Ceridian Benefits Services; in time I became one of their lead techs with a path into their software development department. Again, more money than I knew what to do with.
After about a year of this though, things weren't working out, and there was a part of me that felt starved. It was the part that enjoyed hiking, enjoyed being outside, enjoyed being fit and in good physical health. I also had a strong feeling that everything up to this point had been too easy for me, that I wasn't getting as much out of life as I wanted to.
So I quit.
I moved back to California and resolved to spend the next few years starting over, completely from scratch; I wanted to take the hardest possible path through life for the next few years. (Boy, I had no idea what I was in for.)
I got into rock climbing, and then got a job as a climbing instructor. I had the opportunity, through my style, personality, will, and determination, to influence people around me. I made a lot of friends, many of whom I'm still friends with. I got to feed the outdoor side of my personality for a while. The job didn't pay much though, and eventually I fled, in debt, to a job in the retail part of the outdoor industry, in another part of the state.
During this time I didn't use computers, unless it was as a cash register or inventory system. For a period of a couple of years, I was completely disconnected from the internet, computers, toys, and gadgets. I learned how to fix cars, I chased sheep down the street, I climbed a lot, and I wandered around.
I'm back in computers now, obviously. It took me only about a year to catch up to the changes in the industry, and I'm one of the leading consultants in my area now, with a successful business of my own.
But, I'm really, really, really glad I took that road. It taught me so much that I couldn't have learned by staying behind a computer desk all day long. It taught me how to relate to people, for one. It taught me how to maintain some balance in my life, and how to pay attention to the needs of my spirit. (My girlfriend, who's reading this over my shoulder -- she's really patient with my need to hear myself talk! -- is reminding me that it's also how I met her, which is probably the best part of all. :-)
So my main point, in so much as I have one, is that abandoning your core skill in an area, and putting yourself in over your head for a while, can lead to some really valuable experiences. You don't need to worry about whether or not you'll still be able to get back in later, or re-acquire old skills; they'll come back, in time. Don't worry about that at all.