Software Development: The Great Equalizer
-
Hmm. At the risk of being flamed, I'm going to comment here. I ran the traditional route. I majored in computer engineering at Wright State[^], graduating with a bachelor's degree in 1984. While I was a sophomore in early 1980, I started working as a part-time programmer. I also filled slots during that period as a system manager (VAXen) and as a technical writer. In the ensuing 40 years I have worked with all kinds of folks with different backgrounds. One of the best programmers I ever worked for had a degree in physics. Another guy didn't have a degree but was a phenomenal embedded developer with a meticulous style that, ten years after he retired, makes his code still some of the easiest to maintain I've ever seen. I worked with a college-trained programmer who had enviable credentials, but wrote the sloppiest, most bug-ridden sh!t code I've ever seen. After he left, I spent over a year rewriting everything he wrote on my product, as I got tired and pissed off over the constant bug reports. Another college grad wrote decent code but was an elitist and couldn't be bothered to document it or make it easy to use. Based on my experiences, I can make the following observations: A college education does not guarantee that you'll be a great developer. What is does is give you a broader and deeper skill set than you're likely to have if you're self-trained. As an example, the fantastic embedded guy I mentioned? His only data structure was an array. He knew about linked lists, trees, and all sorts of other things, but they weren't tools he could use comfortably. College educated folks think that grants them a certain level of expertise, often over the self-trained developer, that may or may not be warranted. Practical experience obtained through self-training is great, because you don't have preconceived notions about how something's going to go while you're learning it. Since you're self-motivated you tend to work harder when learning something new, and pay more attention to the nitty-gritty details. That said, it also means that there can be potholes in the road that you might know intuitively from the education that you'll miss entirely if your experience hasn't included it. Many self-trained folks also have a chip on their shoulder about it, and disparage the education as needless academic fluff. My point is that both paths to expertise have value. Choosing one over the other is a mi
What makes you think your post could get flamed? It was interesting to read about your experiences, and your observations make sense. I would say that programming is always mostly self-taught. University can inform you of techniques (data structures, parsing, state machines...), but it's mostly a case of the more code you write, the better you get, so long as you strive to make your code easy to maintain and evolve instead of just dropping it once it works.
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing. -
Hmm. At the risk of being flamed, I'm going to comment here. I ran the traditional route. I majored in computer engineering at Wright State[^], graduating with a bachelor's degree in 1984. While I was a sophomore in early 1980, I started working as a part-time programmer. I also filled slots during that period as a system manager (VAXen) and as a technical writer. In the ensuing 40 years I have worked with all kinds of folks with different backgrounds. One of the best programmers I ever worked for had a degree in physics. Another guy didn't have a degree but was a phenomenal embedded developer with a meticulous style that, ten years after he retired, makes his code still some of the easiest to maintain I've ever seen. I worked with a college-trained programmer who had enviable credentials, but wrote the sloppiest, most bug-ridden sh!t code I've ever seen. After he left, I spent over a year rewriting everything he wrote on my product, as I got tired and pissed off over the constant bug reports. Another college grad wrote decent code but was an elitist and couldn't be bothered to document it or make it easy to use. Based on my experiences, I can make the following observations: A college education does not guarantee that you'll be a great developer. What is does is give you a broader and deeper skill set than you're likely to have if you're self-trained. As an example, the fantastic embedded guy I mentioned? His only data structure was an array. He knew about linked lists, trees, and all sorts of other things, but they weren't tools he could use comfortably. College educated folks think that grants them a certain level of expertise, often over the self-trained developer, that may or may not be warranted. Practical experience obtained through self-training is great, because you don't have preconceived notions about how something's going to go while you're learning it. Since you're self-motivated you tend to work harder when learning something new, and pay more attention to the nitty-gritty details. That said, it also means that there can be potholes in the road that you might know intuitively from the education that you'll miss entirely if your experience hasn't included it. Many self-trained folks also have a chip on their shoulder about it, and disparage the education as needless academic fluff. My point is that both paths to expertise have value. Choosing one over the other is a mi
Yeah I'm not even trying to say my route was ideal. Hell, I don't even know if I could reproduce it if I had to do it over again. It's just what I had in front of me. That's not to say that it's better than going to school. :)
Real programmers use butterflies
-
Yes different times indeed. Turns out that a couple of guys in my unit were gay, one highly decorated and even wrote a book. I was totally unaware he was gay, it would not have made a difference to me but at the time the military was very anal about such things and he probably would have been ostracized and booted out?
The less you need, the more you have. JaxCoder.com
-
I have a similar background but not wired like you. What I mean by that is I understand that people who fancy writing compilers (parsers) are a special breed. I'm pin level hardware savvy and have done some assembly early on but when I read your tech posts my head just spins I have no idea where you've been. That's a compliment. I was the last of 5, punk ass lead guitarist that had electronics in high school but wanted to build flangers and delays more than motors and study diode drops. My parents gave me 3 choices on day in my junior year A: Get your grades up. B: Join the military or C: drop out of school and we'll set you up in an apartment and you an get a job and a roomie to pay for it all. Duh. So I got a job soldering for a waterbed heater company in So. Cal where we lived, then an data acquisition company where I started as a line inspector but once they got wind of my electronics knowledge (resistor color code memorization mostly) the put me in the test tech group. You job hopped for advancement then then the last stint was sr. engineering tech at Emulex when DEC roamed the earth. All the while I was fascinated with coding but have never done it professionally. After Emulex my wife and I bugged out to Summit County Colorado to ski a lot but there is no real jobs to be had in the tech sector in a resort town at 9800 feet in the sky. So we opened a pc shop that went great guns but now just gets along. I do some personal life enhancing code that helps my wife with her new gig as a business consultant. She was a 4.0 student and is the real brains of the two of us but detests the idea of herself coding even though she can unravel the snarliest ms exchange issues, has had enough. I'm doing an MVC AspNet POS program right now for a side job I fell into selling retail products. That keeps me entertained. The tech sector is a great equalizer. Nerds arise! :thumbsup:
Ron Anders wrote:
when I read your tech posts my head just spins I have no idea where you've been
I take that as a challenge to become a better writer. I don't want my stuff to be arcane. I'd like to bring a little witchcraft to everyone. So I'll keep trying, and maybe one of these days I'll figure out how to make my stuff accessible to most people. :)
Real programmers use butterflies
-
I grew up kinda hard, with untreated mental illness and spent some time on the streets as a homeless teen, got my GED as a result and never went to college. But I had hacked around on computers, programming since I was 8 years old. When I was 18 I went from being homeless to moving in with my b/f in seattle and from there straight to Microsoft. I started taking senior and lead positions before I was 20. Outside of software development, for example when I moved from Seattle to rural Washington state where there were not development jobs I drove a cab, jockeyed cash registers, and even worked on a farm. I'm not qualified to do anything skilled but write software. I can't tell you how grateful I am that this industry values talent over credentials. I'd be in a very different position today if it weren't for that. I have a friend I grew up with who never launched into a software career despite us programming together but his primary interest is language so I guess I understand - I learned C++, he learned Latin. I have another friend who I came up with together and helped him get into development, and then he moved to NYC and got rich, and he has a similar background as me, except not crazy. None of these people have degrees. Both are ridiculously intelligent. But it makes me think, you know? I count myself fortunate, and I am grateful not just for me, but for anyone like me who found their way despite lack of opportunities and access to "white collar" work generally.
Real programmers use butterflies
Praise You. Keep up the good work !
Caveat Emptor. "Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
-
Yeah, there was DADT and all that. It just wasn't for me. I'm not the type. :)
Real programmers use butterflies
I just lived through it. At the time the draft was going on and my number was up so I enlisted. Probably saved my life, I went into communications instead of infantry and in 67 things over there were hot.
The less you need, the more you have. JaxCoder.com
-
I just lived through it. At the time the draft was going on and my number was up so I enlisted. Probably saved my life, I went into communications instead of infantry and in 67 things over there were hot.
The less you need, the more you have. JaxCoder.com
I'm glad it worked out for you in the end. Elephant knows it didn't for so many. :sigh: That war was just.. SMDH I don't know whether to say sorry or thank you. I have ... feelings about vietnam vets that sets them apart for me from other war vets. I won't get into it for risk of making this thread political, but you (and if not you then or at least many like you - i don't want to speak for you) deserved better.
Real programmers use butterflies
-
I'm glad it worked out for you in the end. Elephant knows it didn't for so many. :sigh: That war was just.. SMDH I don't know whether to say sorry or thank you. I have ... feelings about vietnam vets that sets them apart for me from other war vets. I won't get into it for risk of making this thread political, but you (and if not you then or at least many like you - i don't want to speak for you) deserved better.
Real programmers use butterflies
Thanks...yeah let's just leave it there.
The less you need, the more you have. JaxCoder.com
-
Thanks...yeah let's just leave it there.
The less you need, the more you have. JaxCoder.com
sorry I get emotional with certain things.
mov ax, [feelings]
xor ax,axThere. :laugh:
Real programmers use butterflies
-
What makes you think your post could get flamed? It was interesting to read about your experiences, and your observations make sense. I would say that programming is always mostly self-taught. University can inform you of techniques (data structures, parsing, state machines...), but it's mostly a case of the more code you write, the better you get, so long as you strive to make your code easy to maintain and evolve instead of just dropping it once it works.
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing.Greg Utas wrote:
What makes you think your post could get flamed?
My experience has been that some college-educated folks can be a little dismissive of the self-taught, and the self-taught are sometimes defensive as a result. Taking the middle ground means you disagree with most.
Greg Utas wrote:
the more code you write, the better you get
Very true. You learn the "why" of writing code in a particular fashion, as expressed in the mental scar tissue from excruciating debug sessions.
Greg Utas wrote:
make your code easy to maintain and evolve instead of just dropping it once it works.
That's been one of the great things about switching from defense contracting to commercial development. With defense contracting you wrote an application, delivered it, and you were done. I have commercial applications now that I've been developing, maintaining, and enhancing for 20 years. Going back to code you wrote 20 years ago can be a humbling experience :sigh: .
Software Zen:
delete this; -
Greg Utas wrote:
What makes you think your post could get flamed?
My experience has been that some college-educated folks can be a little dismissive of the self-taught, and the self-taught are sometimes defensive as a result. Taking the middle ground means you disagree with most.
Greg Utas wrote:
the more code you write, the better you get
Very true. You learn the "why" of writing code in a particular fashion, as expressed in the mental scar tissue from excruciating debug sessions.
Greg Utas wrote:
make your code easy to maintain and evolve instead of just dropping it once it works.
That's been one of the great things about switching from defense contracting to commercial development. With defense contracting you wrote an application, delivered it, and you were done. I have commercial applications now that I've been developing, maintaining, and enhancing for 20 years. Going back to code you wrote 20 years ago can be a humbling experience :sigh: .
Software Zen:
delete this;Gary R. Wheeler wrote:
With defense contracting you wrote an application, delivered it, and you were done.
I've never worked on defense contracts, but this still comes as a total shock. What customer who's happy with software never asks for another release with more features?! If these folks just issue an RFP to build the same thing again, with more features added, it would explain a lot about their budgets. Tell me I'm missing something here.
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing. -
I grew up kinda hard, with untreated mental illness and spent some time on the streets as a homeless teen, got my GED as a result and never went to college. But I had hacked around on computers, programming since I was 8 years old. When I was 18 I went from being homeless to moving in with my b/f in seattle and from there straight to Microsoft. I started taking senior and lead positions before I was 20. Outside of software development, for example when I moved from Seattle to rural Washington state where there were not development jobs I drove a cab, jockeyed cash registers, and even worked on a farm. I'm not qualified to do anything skilled but write software. I can't tell you how grateful I am that this industry values talent over credentials. I'd be in a very different position today if it weren't for that. I have a friend I grew up with who never launched into a software career despite us programming together but his primary interest is language so I guess I understand - I learned C++, he learned Latin. I have another friend who I came up with together and helped him get into development, and then he moved to NYC and got rich, and he has a similar background as me, except not crazy. None of these people have degrees. Both are ridiculously intelligent. But it makes me think, you know? I count myself fortunate, and I am grateful not just for me, but for anyone like me who found their way despite lack of opportunities and access to "white collar" work generally.
Real programmers use butterflies
-
Gary R. Wheeler wrote:
With defense contracting you wrote an application, delivered it, and you were done.
I've never worked on defense contracts, but this still comes as a total shock. What customer who's happy with software never asks for another release with more features?! If these folks just issue an RFP to build the same thing again, with more features added, it would explain a lot about their budgets. Tell me I'm missing something here.
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing.Greg Utas wrote:
I've never worked on defense contracts, but this still comes as a total shock
The last three years I worked as a contractor would appall you. One project, two years worth, developed a simulation that at completion was run for two weeks to accumulate some data and then shelved. A second project which took 18 months never ran at all, but delivery was accepted anyway. A third project I wrote a final report which was disseminated to interested parties and that ended it. While commercial development has its downsides, at least my stuff now gets used.
Greg Utas wrote:
Tell me I'm missing something here.
This was back in the 1980's so things may be different now. At the time though I read a report that claimed less than 2% of software created for the DoD (based on dollars spent for development) was still in active use 12 months later. Most of that was in deployed weapons systems and avionics. The rest of it was spent on hopeless MIS projects that tried to automate processes in a 'business' (e.g. defense) that deliberately let experienced employees leave, either at the 4 or 20 year mark. My running joke at the time was "I may be a whore, but at least I ain't cheap."
Software Zen:
delete this; -
What's GED ?
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
It's a high school equivalency "diploma" you can get via exam in lieu of finishing school. Part of the problem with me staying in school is there was a truancy law on the books which would have landed me in juvenile detention a lot because I wasn't able to show up for all of my classes every day because I had to worry food and a place to sleep. So to avoid jail, I dropped out. Basically it's a way to test out of high school so you're not quite as bad off as if you had just stopped going.
Real programmers use butterflies
-
I grew up kinda hard, with untreated mental illness and spent some time on the streets as a homeless teen, got my GED as a result and never went to college. But I had hacked around on computers, programming since I was 8 years old. When I was 18 I went from being homeless to moving in with my b/f in seattle and from there straight to Microsoft. I started taking senior and lead positions before I was 20. Outside of software development, for example when I moved from Seattle to rural Washington state where there were not development jobs I drove a cab, jockeyed cash registers, and even worked on a farm. I'm not qualified to do anything skilled but write software. I can't tell you how grateful I am that this industry values talent over credentials. I'd be in a very different position today if it weren't for that. I have a friend I grew up with who never launched into a software career despite us programming together but his primary interest is language so I guess I understand - I learned C++, he learned Latin. I have another friend who I came up with together and helped him get into development, and then he moved to NYC and got rich, and he has a similar background as me, except not crazy. None of these people have degrees. Both are ridiculously intelligent. But it makes me think, you know? I count myself fortunate, and I am grateful not just for me, but for anyone like me who found their way despite lack of opportunities and access to "white collar" work generally.
Real programmers use butterflies
Thank you for your post! It brought up such an interesting discussion and I feel truly humbled by the diversity of experiences that developers come from. Compared to what some of you guys have been through, my life seems the pinnacle of boredom: saw a book about a new thing called "programming" when I was 15 and, for some strange reason, decided that's what I do in my life. Luckily I found some guys who would pay me a decent wage for doing that. Many years later I still don't know to do anything else. Talk about being monomaniacal :laugh: .
Mircea
-
Greg Utas wrote:
What makes you think your post could get flamed?
My experience has been that some college-educated folks can be a little dismissive of the self-taught, and the self-taught are sometimes defensive as a result. Taking the middle ground means you disagree with most.
Greg Utas wrote:
the more code you write, the better you get
Very true. You learn the "why" of writing code in a particular fashion, as expressed in the mental scar tissue from excruciating debug sessions.
Greg Utas wrote:
make your code easy to maintain and evolve instead of just dropping it once it works.
That's been one of the great things about switching from defense contracting to commercial development. With defense contracting you wrote an application, delivered it, and you were done. I have commercial applications now that I've been developing, maintaining, and enhancing for 20 years. Going back to code you wrote 20 years ago can be a humbling experience :sigh: .
Software Zen:
delete this;The last time someone asked me to defend my lack of a degree was in an interview. I asked him to defend him getting one, given the way IT is taught in uni. Because it was at that point that I decided I really didn't want to work at Expedia. Gee, glad I didn't. They don't exist anymore. And I'm okay with that. When people have degrees, I am that much more careful about screening them for experience if I'm in charge of putting together a team, because I've had a lot problems with people coming straight out of college totally unprepared for working on a professional software team. They might know algorithms, but they don't necessarily understand all the coding techniques that you just pick up organically. With the self taught ones, after a few questions, the only thing I had to worry about was if they could work on a team. Problem is, they usually couldn't, so it became a matter of how quickly they could learn. Experience at the end of the day is what it all comes down to. Each path has its downsides, and I have my biases. I'm a black sheep developer. I'm creative, but not methodical. I'm not a math whiz, but I love language. I'm kinda a weirdo in any given dev house in terms of the sort of code I am good at and what sort of direction a project will take if I'm leading it. I like other black sheep. But there needs to be very few of them on a team for the team to be successful. The black sheep may or may not have went to school, but in terms of programming, they learned most of it themselves, and they don't do it like other people do. I value the "white sheep" professionally, especially when I'm putting a team together because they work well on teams and their work is reliable and consistent. Their creations are more easily understood by others as well, but my heart is not with them, if I'm being honest. More of them I've found, have come up in CS through academia. Now, those are just broadly general observations. People are complicated, and any attempt to boil them down is going to be silly on some level, but the above way of looking at things has served me professionally, so I stick with it. :)
Real programmers use butterflies
-
I grew up kinda hard, with untreated mental illness and spent some time on the streets as a homeless teen, got my GED as a result and never went to college. But I had hacked around on computers, programming since I was 8 years old. When I was 18 I went from being homeless to moving in with my b/f in seattle and from there straight to Microsoft. I started taking senior and lead positions before I was 20. Outside of software development, for example when I moved from Seattle to rural Washington state where there were not development jobs I drove a cab, jockeyed cash registers, and even worked on a farm. I'm not qualified to do anything skilled but write software. I can't tell you how grateful I am that this industry values talent over credentials. I'd be in a very different position today if it weren't for that. I have a friend I grew up with who never launched into a software career despite us programming together but his primary interest is language so I guess I understand - I learned C++, he learned Latin. I have another friend who I came up with together and helped him get into development, and then he moved to NYC and got rich, and he has a similar background as me, except not crazy. None of these people have degrees. Both are ridiculously intelligent. But it makes me think, you know? I count myself fortunate, and I am grateful not just for me, but for anyone like me who found their way despite lack of opportunities and access to "white collar" work generally.
Real programmers use butterflies
I don't think you can go that route today, there is too much focus on qualifications and too many get rich quick brats. I had a similar route except I am mentally eminently stable and grounded despite running away from a dysfunctional family at 15, working approx 20 different jobs till I discovered software in my 30s (in the late 80s). Worked as a consultant (quote, build and chase the invoices) till I worked out that contracting you did not have to do the fucking paperwork involved in running your own business. Ended my career as a highly paid and valued developer at one of Asia's top banks. Today that path is not possible. Have not coded in 2 years, it turns out I was a tart (please forgive the gender reference), only into it for the money.
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
-
Thank you for your post! It brought up such an interesting discussion and I feel truly humbled by the diversity of experiences that developers come from. Compared to what some of you guys have been through, my life seems the pinnacle of boredom: saw a book about a new thing called "programming" when I was 15 and, for some strange reason, decided that's what I do in my life. Luckily I found some guys who would pay me a decent wage for doing that. Many years later I still don't know to do anything else. Talk about being monomaniacal :laugh: .
Mircea
That's not that far off from how I picked it up, except i was a bit younger. My parents bought an Apple ][gs in 1986 and it came with a programming manual for Applesoft BASIC. I read it because I read while eating otherwise the act is boring. Not very mindful of me, but then I'm not a buddhist so it's fine. It converged with my problem of circuit building. I took things apart and made things with them but to do anything serious in terms of building gadgets required money i didn't have at 6 and 7 so software allowed me to build things without continually shoveling more money at Radio Shack.
Real programmers use butterflies
-
I don't think you can go that route today, there is too much focus on qualifications and too many get rich quick brats. I had a similar route except I am mentally eminently stable and grounded despite running away from a dysfunctional family at 15, working approx 20 different jobs till I discovered software in my 30s (in the late 80s). Worked as a consultant (quote, build and chase the invoices) till I worked out that contracting you did not have to do the fucking paperwork involved in running your own business. Ended my career as a highly paid and valued developer at one of Asia's top banks. Today that path is not possible. Have not coded in 2 years, it turns out I was a tart (please forgive the gender reference), only into it for the money.
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
hah it's fine. I'm not sure. The last four clients I've had didn't even ask for a resume. One of them scouted me from my articles here. Maybe I'm just being optimistic, but I think if you have talent and a little luck you can maybe still pull it off, even if the culture has changed. You may not be able to work at Microsoft anymore without a serious CV but I don't know - i'd like to think they'd still hire anyone that had the endurance for a 4 hour panel interview with whiteboarding. I've done that.
Real programmers use butterflies
-
I don't think you can go that route today, there is too much focus on qualifications and too many get rich quick brats. I had a similar route except I am mentally eminently stable and grounded despite running away from a dysfunctional family at 15, working approx 20 different jobs till I discovered software in my 30s (in the late 80s). Worked as a consultant (quote, build and chase the invoices) till I worked out that contracting you did not have to do the fucking paperwork involved in running your own business. Ended my career as a highly paid and valued developer at one of Asia's top banks. Today that path is not possible. Have not coded in 2 years, it turns out I was a tart (please forgive the gender reference), only into it for the money.
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
My first software job was 40 years ago. Curiously, my take is that it's easier to get a job without "qualifications" these days, though there's a lot of "certification" horseshite. But in 1981, everyone expected a degree. It might not be in computer science, because there weren't enough of us. But engineering, mathematics, or physics would do, especially if you'd done a bit of programming. I used to say that the problem with our software was that we had too many straight engineers, and it was comparable to someone landing a job designing circuits because they'd played around building speaker systems in their garage.
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing.
