From software developer to where?
-
Ditto :-D - I've been a software engineer since 1978 (embedded systems for the automotive industry) and can not think of anything else I would want to do. 'After' for me would be retirement (in ten years or so).
Me too - in about 10 12 years. I've been doing this a little over 30. I think I'll be spending more time in the cockpit of a Cessna - don't get to do it enough right now. -CB ;)
-
Leeland Clay wrote:
I've been a programmer since I was 12.
Wow! Impressive.
Leeland Clay wrote:
don't get me wrong...ANYONE can learn how to sling code...but a true programmer looks at what they do as art. You can't learn that. It becomes part of you. I've seen a LOT of people go through classes and learn to program and enjoy doing it...but didn't last.
True to a point. I suppose I am an "anyone" that learned how to code ... and I enjoyed it for awhile. And no, I don't really anymore. But being a perfectionist at everything I do in life still makes me strive to the absolute best. Eloquent code my professor used to call it. To do it correctly, or not do it at all.
Leeland Clay wrote:
If you want my honest advice on what to do next...look inside. What makes you happy??? Whatever it is, do it.
While this is awesome advice, and I'd love to take it myself ... if you have bills to pay and kids to feed -- it's not gonna happen. Cuz there ain't no way I can support my family greeting people at the greasy spoon down the street and pouring coffee all day! (Sad yes, but I was the most happy in life just waiting tables! :))
I understand the whole issue of needing to support a family. Something you could look into tho is getting into restaurant management. I've heard of some pretty nice salary's when you get into the actual manager position (depending on the size of the restaurant). I would like to add that you may not be one of the "anyone". You stated that you were a perfectionist and you strive to do the best. That is definately a needed characteristic for programmers. If I had to guess at your situation, I think you're more frustrated/bored than ready for career change. And THAT is as normal for geeks as you can get. I was having a conversation this morning with a work collegue and that was the topic. Basically it amounted to the fact that a lot of corporations tend to mold people to the positions they have. IT people don't mold too well :). I don't know your exact circumstances, but this may be your situation. If that's the case, spend time on your own (weekends/late nights/whenever) and study something that you can't do at work. Personally, I do game programming. I don't consider myself a game programmer...but I have a lot of fun doing it. That gives me the artistic outlet where I get to choose the outcome and reduces the stress in my life so that I can handle the box my job puts me in. I will also add that I have a different view than most on my career. I don't look at a job as a career. I look at as an assignment. I have several entries on my resume that are around 1 year in length. Most people see that as a bad thing...I see it as a good thing. When you consider that I only leave a position when I have reached the absolute limits that the position offers (knowledge and experience) then it shows that I provide maximum return to an employer in a very short amount of time. You may be ready for a change of employment...something to remind you of the challenge and satisfaction that being a developer gives you. Since I babbled on this long, I close with this. IT (all aspects of the community) is what you make of it. The best part of being in IT is that there's so many different options to choose from...you can make your career whatever you want it to be :)
-
Ditto :-D - I've been a software engineer since 1978 (embedded systems for the automotive industry) and can not think of anything else I would want to do. 'After' for me would be retirement (in ten years or so).
Code or death? I am not sure which would be preferable some days... Today is one of those days and it is only 09:30 on the left coast. It's a Monday. When I was in school, I took some kind of interest/disposition test offered by the University Career Placement office. My test results pointed toward software development or research science. You might look around and see if you can find a similar service offered by someone in your area. That might give you an insight into area(s) you had not previously considered.
-
Hi all, I need some advice. I've been a software developer for the last six years. I've progressed to development manager within that time and that for me still involves a lot of programming. I feel it's time for a change. What do poeple do after software development and how do they go about doing it? Thanks for your time Sion
I am personally more on the technical side of things, so for me growing into the Architect role proved more practical (I never wanted to manage people and/or projects). There's obviously still programming involved in that, but a lot more "design meetings" and telling other junior programmers how things should work (or be written). Architecture is a very demanding role, as you have to "see the big picture" - sometimes wrong architecture decisions are not discovered till later in the game (sometimes years), and the right ones will always be remembered by your employers. There are several ways to get into such a role - me personally being on the .NET side I chose the MCSD.NET certification which does seem to open a lot of doors (not the easiest cert but worth it). Either way try to ignore those negative comments ("there's only death after programming"), since from my experience there's a lot more to do after "death" ;-) Hope this helps :) .leON.
-
If you even consider not being a software developer, then you shouldn't be one. I, and I suppose many others here, wouldn't consider anything else, it's what we do, we do it for fun even when we're not being paid. If you're that type get out now. Even if I became rich and bought a Carribean island I'd spend too much time inside at a computer.
PIEBALDconsult wrote:
Even if I became rich and bought a Carribean island I'd spend too much time inside at a computer.
That's true to some extent, yet I wonder if you'd have internet on that island? Without a real connection it might get pretty boring quite fast ;-) .leON.
-
Stack and Heap???!!! Everything was in assembler 'back then". I didn't start using C (on the job anyway) until about 1989. These were eight bit micro-controllers (think Motorola 6800, 6802, 68hc11) with about 10k to 16k of ROM space with only about 1k - 2k of RAM to work with (sometimes less). We thought about memory usage in BITs not KBytes. The good 'ole days...what ever happened (OSes that take 2 gig or more of disk space...sigh) :-D
That sounds great, oldskool rules ! I am myself in the automotive branch, what have you been programming back then, if I dare ask ?
Constantly "Saving the day" should be taken as a sign of organizational dysfunction rather than individual skill - Ryan Roberts[^]
-
I am personally more on the technical side of things, so for me growing into the Architect role proved more practical (I never wanted to manage people and/or projects). There's obviously still programming involved in that, but a lot more "design meetings" and telling other junior programmers how things should work (or be written). Architecture is a very demanding role, as you have to "see the big picture" - sometimes wrong architecture decisions are not discovered till later in the game (sometimes years), and the right ones will always be remembered by your employers. There are several ways to get into such a role - me personally being on the .NET side I chose the MCSD.NET certification which does seem to open a lot of doors (not the easiest cert but worth it). Either way try to ignore those negative comments ("there's only death after programming"), since from my experience there's a lot more to do after "death" ;-) Hope this helps :) .leON.
-
That sounds great, oldskool rules ! I am myself in the automotive branch, what have you been programming back then, if I dare ask ?
Constantly "Saving the day" should be taken as a sign of organizational dysfunction rather than individual skill - Ryan Roberts[^]
My actual first "embedded" job was in 1983 and was non-automotive. I did the firmware for a 6802 based dot-matrix printer which was used with a 6809 based cash-register used in the parking industry (I also worked on the cash-register software). Before that I wrote games for the TRS-80 (Z80 assembler and 6809 assembler) and business software (point of sale and inventory control in BASIC) My first automotive job (1985) was writing a high-speed fiber optic vehicle network protocol (1 megabit - very fast at the time) for a 68000 processor using the 1553 chip set. I've also written software for diagnostics tools used in dealerships (68hc11 and 68332 based), 68hc11 based automatic climate control systems (several versions), 68hc11 based air-bag controllers, 68030 based check sorter (used in the banking industry), mpc823 based voice recognition system (used to control other modules in the vehicle like radio, cd player, etc), NEC 78k0 based heated/cooled memory seat controller. I've worked at all of the (used to be) Big Three and several tier 1 suppliers. Mostly contract work (shortest was 6 months, longest was 7 years). I will be starting a new job in a bit developing end-of-line and in-circuit testers for use in manufacturing plants (mostly automotive). ( maybe I should have just posted my resume - it would have been faster ;) ) What area do you work in?
-
That sounds great, oldskool rules ! I am myself in the automotive branch, what have you been programming back then, if I dare ask ?
Constantly "Saving the day" should be taken as a sign of organizational dysfunction rather than individual skill - Ryan Roberts[^]
BTW - I still remember my first two programs on the TRS-80 - the obligatory "hello world" program and a screen saver (sort of) that drew random patterns of lines on the screen using the graphics characters. The first time I ran it (the screen saver) I thought "WOW - I wrote that". I've been hooked ever since. It started out as a hobby and then I found out that people would actually PAY me to play with computers...life is good. I don't often write software "after hours" anymore but my love for computers has not subsided.
-
Hi all, I need some advice. I've been a software developer for the last six years. I've progressed to development manager within that time and that for me still involves a lot of programming. I feel it's time for a change. What do poeple do after software development and how do they go about doing it? Thanks for your time Sion
Pasting in the Google query (( slashdot "lifetime in IT" )) will find the Slashdot article of 09-May-2007 "Where to Go After a Lifetime in IT?". Or the direct link is http://ask.slashdot.org/article.pl?sid=07/05/09/1728252[^] Also if you type just the word GOOGLE into the CNN-Pipeline(Free Trial) search-box, you will find the 18-may-2007 three-minute video "Life inside Google". This video echoes many of the code-project comments - at the 2:40 mark the reporter muses "With all this food, and all those other benefits, I wonder if one could leave the Company ?" Brett Crosby, Senior Marketing Manager, Google responds "That's a great question, I don't know if I could work anywhere after Google. I think after Google you either have to retire, or kinda go into startup mode."
pg--az
-
Hi all, I need some advice. I've been a software developer for the last six years. I've progressed to development manager within that time and that for me still involves a lot of programming. I feel it's time for a change. What do poeple do after software development and how do they go about doing it? Thanks for your time Sion
Don't leave out the technical sales reps. I have a friend that sells software to the school system and makes double what I do! Another related field is the application engineer. They are more customer centric, and don't get stuck in their chairs for quite as long as we do. Some companies product engineer's are also ex-software developers (espeically for software products). The product engineer focuses on some of the market trends, and tries to steer their products in the right direction before and during development, and then acts as a liason between sales and marketing and engineering during and after a product is released. Best of Luck! Jeff Weichers Lead Software Engineer Schweitzer Engineering Laboratories