|
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.
|
|
|
|
|
For a profit, around 5 years, but I love to code, so probably I would be doing it till the end of times (or my life, whichever comes first...  )
|
|
|
|
|
I've been coding for a living for 41 years this July. I loved it for about the first 30 but then the world changed somehow. Maybe I just got old. Anyway, I also arrived at the point where it just seemed pointless to keep learning new programming stuff. I have hobbies but I just don't have the time for them as long as I'm working. The gig I'm on now is the last one. When it's over, I'm retiring so I can do all the stuff I want to do without programming. Oh, it only took me ten years to discover that working more than 40 hours a week is a loser's game. There's no way you will get that time back and you miss out on a lot of more important stuff when you are working that much. In all those forty years, they kept trying to turn me into a manager but I refused. There's no way I would do that when I could stay coding.
|
|
|
|
|
Since 1964: so 50 years.
COBOL, Focal, Fortran, ALGOL, PL/1, APL, Basic, Burroughs Assembler, Datapoint Databus, IBM Assembler, Intel 8088/8086/..., Perl, Dialog, Ksh/Csh/Bash, Javascript, PHP, C#, ...
Now mostly: Perl, Bash, Javascript, PHP, C#.
Lots of others to learn for fun on the weekends. I am interested in them all ...
"Courtesy is the product of a mature, disciplined mind ... ridicule is lack of the same - DPM"
|
|
|
|
|
Coded first program in 1966. Solved Shrodinger Wave Equation given boundary conditions using Fortran which we had to learn on our own to do the homework for Physics class at Miami University.
Since have programmed in assembly (mainframe and PC), PL/I (mainframe and PC), Cobol, Basic (original and later versions), Turbo Pascal, Delphi, Delphi Prism, RemObject's Oxygene. And dabbled in others including C#, Modula II, Ada, etc.
I prefer the Algol derived langugages. Don't much care for C and its derivatives.
Made a spreadsheet program for the mainframe in PL/I which IBM marketed and made $10 million from.
|
|
|
|
|
At least once a day since I arrived here. 
Anyway, greetings from Fieni.
|
|
|
|
|
Are you in Romania?
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Da.
Moved my wife and kid here this week.
I'll follow in a few years...after I get tired of the peace and quiet at home.
|
|
|
|
|
GenJerDan wrote: At least once a day since I arrived here
And - oh wait you are not in the tropics!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I'd be surprised if this isn't a Leslie, but Super Planet Crash[^]
If you don't think any of the places below are really that great to live in, design your own solar system.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|
|
Totally unrealistic - them orbits ain't elliptical (Yes - I know some pedant will say that a circle is s special type of elipse)
=========================================================
I'm an optoholic - my glass is always half full of vodka.
=========================================================
|
|
|
|
|
Psh. A circle is a special type of ellipse.
|
|
|
|
|
Why are they even orbiting? There is no gravity to keep them in position. If there was, it would have been an elliptical orbit.
Overlapping orbits and overlapping celestial bodies does no damage to system. Funny.
|
|
|
|
|
What do you think the big yellow thing in the middle is? 
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
Well, if there was any gravity in that yellow thing, orbits would be elliptical.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
