|
Been coding since 1977....started on punch cards, went up to punch tape. First computer was a PDP11 compatible....had to enter bootstrap code in using toggle switches.....therefore learnt machine code first, then went to basic and then C....miss machine code.
As they say old programmers never die, they just de-compile !
|
|
|
|
|
I have about 10 years experience and already am sick of it.
It's not the learning (on the contrary) or the deadlines, but the stupidity of managers who refuse to listen to anything you say. You tell them what is wrong, you tell them why and how, but still they cling on to some superior feeling they know best (and at best try to convince you with a vague argument which (s)he just invented).
There are plenty of good managers, but often they don't last long.
|
|
|
|
|
I had 40 years of it starting in 1966, and that was the main problem throughout my career. And I'm sorry to say the worst offenders were Americans who were managing the UK team that I was part of. Fortunatley I knew plenty of Americans who felt the same way.
|
|
|
|
|
Thanks to all who replied, some interesting stuff & i've read them all  . One thing about the 80+ hours is that i've had my own software business since 1991, and to compete with bigger companies have needed to react faster and produce better stuff, so its myself who decides this to launch products quickly, meet deadlines or keep promises (even when the customer has moved the goalpost). my strategy to do what's necessary has provided me an excellent living and kept my families head above water where many business's have failed, and for the most part have loved what I do, but Im not sure if I want to keep doing the same when i'm 60 so looking for a challenge as there's only so much golf I can play lol.
Thanks again
Bob
|
|
|
|
|
Wow ... this read like I could have written it! I, too, have been 'round the block a few times in this field (38). I started just a couple years before you did. ('76). It's been a cool ride, no?
I share your sentiment about moving into management. I feel that it's for the birds, honestly. You've heard the saying: "Those who can't do, manage!" I'm an avid Dilbert fan; the "pointy-haired boss" being the spitting image of a boss I had some years back.
Like you, I still enjoy coding (and also like you a LOT of my work is troubleshooting). As for actual development, I'm spending considerably less time doing that now. My main function with my existing company is the support and troubleshooting of our code. We were bought out about 5 years ago and the parent company needs me to keep it running while they transition our client base to their product. As it is a pretty large system with many clients I'll probably be doing that for quite some time yet. I'm in no hurry to get into another big development project to be honest.
On my own time I write systems for small businesses that could not otherwise afford it. My current project is automation of a co-op farm that we participate in. I do that in exchange for a share in the farm. I also have several programs I've written for automating things for myself which I maintain and improve as I need new features. I tinker with those things as I have the time & inclination. To me, coding was never really about money (I mean, yeah, I had to make a living but I think you understand). It's nice to just write when I feel like it and experiment without having to worry about whether someone else will like it or not.
I'm finding that more and more of my time is being devoted to bike rides, building a chicken coop, stuff like that. I was pretty passionate about software development for a real long time but I'm slowly transitioning away from doing that all the time. Someday maybe (if my health holds up) I'll go drive a bus or do something that doesn't involve burning my brain out. 
|
|
|
|
|
I recently started taking violin lessons again so that if (when?) I get tired of coding, I can hopefully join an orchestra 
But while the challenges remain, along with the thrill of solving them, I don't think I'll get tired of coding quickly
Open plan offices, red tape and poor project planning/management, on the other hand... 
|
|
|
|
|
Started coding in grade 3 (81-82) on a TI-99 4/A, though at the time that was mostly from the coding magazines. That was what started it all though. Years later moved onto the C64, then PC. Still love it, but not every day. I still have had weeks of 80+ hours, but not with the same fervor that I did when I was younger! What I tend to enjoy more is the system analysis and design and then passing that on to others to bring the ideas to life.
|
|
|
|
|
Just don't attempt a career in writing
|
|
|
|
|
|
Touché - although that's really what I'd like to do!
|
|
|
|
|
I generally don't bother too much on here today gone tomorrow forum posts but I've had articles published in the past (mainly about poker) and been paid for them which was great, but writing is an underpaid occupation and hard to make money at bearing in mind the time it takes, but I did dabble a bit for fun and uploaded some stuff to my blog site that I don't bother much with now, if you have nothing better to do and want to kill a short while have a look at www.winbase.info. GL
|
|
|
|
|
How I wish that I shared your experience! I spent 28 years working as a contractor (good pay; no benefits) and ended up going on total disability in 2008. But the love of coding remains strong within me and I am always downloading the latest and greatest trial software.
Bruce Baker - brucebrookebaker@yahoo.com
|
|
|
|
|
I took BASIC and COBOL on a PDP-11 when I went to community college back in the mid 70s. I bought an Apple 2 when they first came out while working on a 4 year degree. Between the Apple 2 and Pascal I was hooked. I was studying electrical engineering at the time and learned a little about assembly language by punching hex codes into an 8080 development board. As far as programming goes, I never looked back. Graduated in 1978 then went on for an MSCS and have been doing embedded programming since 1980. I also owned a TRS80 Model 100 which was one of the first (the first?) portable computers. It had built in BASIC and 32K or so of persistent storage, even had a text editor and some simple business apps built in. Unfortunately what used to be tremendous fun for me is now just a way to earn a living. I'm going to retire soon and hopefully start doing it again for enjoyment instead of for pay.
|
|
|
|
|
ahhh the TRS-80. my first PC was a video genie which was a trs-80 copy, cassette tape for storage, and 8k I think. if you wanted to expand to 32k you had to buy an external unit the size of a shoebox that had its own power supply lol. those early days of little memory have always stayed with me and im sure have helped me to write concise and reusable code which i try to do to this day - happy days !! GL
|
|
|
|
|
I did my first program (a simple calculator) when I was 6 (1986), on a Sinclair Z80 with Basic... It was even stored in a DataSette.
That's how I started in math...
I'm on a Fuzzy State: Between 0 an 1
|
|
|
|
|
Plug boarding in 62, everything else after that...6500's,8080's & up, Sys36,4381/etc...
At 70 still at it so I still remember what it was that I was doing. OO&MVC.. starting to get complicated..
|
|
|
|
|
Plug boarding in 62, everything else after that...6500's,8080's & up, Sys36,4381/etc...
At 70 still at it so I still remember what it was that I was doing. OO&MVC.. starting to get complicated..
CBW
|
|
|
|
|
My first coding experiences were back in 1980 when I was 10, and after that I never stopped.
I've been working as a software engineer since 1989, and in 1994 I founded my small software house, which is still doing great.
So, I've been coding for 34 years overall, 25 as a professional.
Not bad. 
I still have tons of fun and keep getting those blissfull experiences where you are stuck to your keyboard, immersed in the wonderful universe where you are The Creator, and hours go by while the outside world is just a faint echo from far away.
In my case, the frustration comes more from the managerial part of my job, which unluckily cannot be put aside, especially since I'm the owner of the software house...
I am and will always be a technician and a geek, and although I am not that bad as a manager (but only cause my company is so small!  ), I still feel like all the time I spend in meetings, presentations and such is just wasted. I feel the same about the time I spend driving when I have to visit a customer (this is a very small amount of my time, luckily - thanks God for teleservice and global communications!  ).
I realize this is just a very subjective point of view, and that's not wasted time all. It's actually time spent in order to allow my company to prosper and let me do what I like best: coding.
Still, that's how I feel. If I ever had to be forced to a managerial-only role, I think I would slowly wither and die!!! 
Having said all that, I can understand your frustration, since by what you say what's wearing you out is not your job as a coder itself, but rather the fact you are forced to work in a very stressful environment. I wish you a very good luck and hope your situation gets better. I sure know it would wear me out too!
In theory, there is no difference between theory and practice, but not in practice. - Anonymous
A computer is a stupid machine with the ability to do incredibly smart things, while computer programmers are smart people with the ability to do incredibly stupid things. They are, in short, a perfect match. - B. Bryson
|
|
|
|
|
I have the record. I started in 1960 with UNIVAC working on the 1st computers for NAVY ships CIC operations.
Still coding at 77 on Vari-lite moving lights. (Lots of steper motors.)
Larry
|
|
|
|
|
You Sir DO have the record as far as i'm concerned, having started a year before I was born lol. If I push it I can say I started on programmable calculators a year or so before computers, either 76 or 77, cant remember exactly, but I take my hat off to you
|
|
|
|
|
I'm 64 and I have been doing this for 40 years. I currently specialize in the Microsoft .NET development environments.
I know what you are saying about so many new technologies coming out but a lot of it is just fluff that does nothing to really benefit the developer or the user.
In this vein, I find MVC and its many outgrowths to be one of the biggest problems facing an industry that in the corporate environments often require very complex interfaces. You can do this with MVC but why bother when you will get similar performance with ASP.NET Web-Forms and only half the effort?
Many of these new technologies are being hyped by the younger crowd who I have found have little knowledge as to how to design complex systems, which is demonstrated by mixing MVC paradigms with such development processes such as Agile, neither of which have moved the rate of project failure a single digit down from its consistent high of around 70%.
As to the passion; well I am wearing out but not because of the technologies or the work. I just can't take working with so many incompetent technical managers any more. Technical managers don't give a wit about proper software design paradigms and are willing to throw any crap against the wall just to get something done, while many users are left in a lurch without proper requirements development since long ago the industry shed the positions of systems analyst and business analyst as it was thought to be "cheaper" to let the developers do everything.
Well we know how that is working out...
I would be interested in any and all comments (just no profanity please...)
Steve Naidamast
Black Falcon Software, Inc.
blackfalconsoftware@outlook.com
|
|
|
|
|
I began coding in 1971 with a part-time job while in high school (long story). My first language was Fortran, then Assembler for 15 years, on to C for 10 years, next to Cold Fusion, and now VB.Net and C#. I still enjoy coding and have resisted going into management for that very reason. I could make more money supervising people and spending hours in meetings, but I would not be happy. I've seen more than one technician follow the management route and end up a bad manager. I realized a long time ago that I did not want to become one of those statistics.
It has been many years since I put in 80+ hour weeks to meet deadlines. Those types of hours are passion killers and usually indicate a problem with project scope/timeframe, management, or even that you're being taken advantage of (in my opinion and experience). A word about "passion"; Merriam-Webster defines it as "a strong feeling of enthusiasm or excitement for something or about doing something". I wholeheartedly agree with this definition. Employers on the other hand, tend to define it as an all-consuming desire to work in complete disregard of one's personal life or health. This is a mistake.
As for the new languages, frameworks, operating systems, etc., some of them are examples of "everything new is old again". But my approach is to be informed about the new fangled gadgets, keep watch on where the industry is headed, and select whatever interests me or might further my career.
I don't know of an occupation my programming skills could be transferred into. I was a dancer many years ago, but at the age of 60 I live in fear of falling and breaking a hip so I think that dream will remain just that.  I'll likely remain that old, crusty, programmer in the corner cubicle for several years to come.
|
|
|
|
|
Hi Ed
thanks for replying, I cant believe how many people have done so lol - I replied earlier to someone explaining that i've had my own small software business for 20+ years and on occasions i've had to put in long weeks sometimes for months on end, 6am to 9pm which makes 80hrs small potatoes at times when ive been writing commercial systems to compete with larger companies and ensure my survival, which I think has worked out quite well. my last large commercial system took years to develop and I got no revenue from it during that time as well as having fee earning work to do, so couldn't hang about too much and had to drive hard to achieve my goal, but im seeing a lot of benefit now I suppose.
GL
Bob
|
|
|
|
|
I graduated in Physics in 1966 and went to work for Boeing in Seattle acquiring and reducing data from wind tunnel tests, calculating lift and drag, measuring noise from directional mics.
Next stop was working on the OS at Prime Computer.
Long story short, I've been writing code since I was in college and still am. Today, storage is king and I'm deep in iSCSI, Fibre Channel and Windows integration. I still write code every day, every week.
StCroixSkipper, aka Scott Moreland
|
|
|
|
|
Got started learning programming just before high school in 1969, after high school was a computer operator that rewrote programs to make them faster and easier to use (the "systems programmers" had no concept of time/motion), first professional job was in 1976. First published programs in 1980 (game cartridge) and then Apple II utilities in 1982. (I'll let you do the math)
Worked 100+ hours/week doing conveyors because we couldn't program the conveyors (each was unique) until they were built and client expected to use it shortly after. I wrote a table driven universal carton tracking system in FORTH that new manager didn't understand and he declared future programs were to be written in "C" to be "commercial." I would have written a simulator so we could do simultaneous development during construction, but idiot manager insisted on being an idiot. He thought job was 8 to 5. Out in the field he got to experience his first 12 hour day (clients expect you to cover all three shifts) and boy was his butt dragging at the end. Cheer up, I said, just wait for your first 36 hour day and yes, there will be 48's as well. Because of him (and a big raise) I left and he didn't last much longer. I still miss that job. Required everything I knew and a little bit more besides to keep it fun and challenging.
I love my current job as a manager that gets to program. A previous job where I was accidentally left in charge had no time to program in.
Still work on outside projects on weekends to learn stuff regular job does not currently use, but twice now, the knowledge acquired from the outside projects have been applied at work and saved the company vast sums of money.
I do not plan on retiring.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
