|
I know there are a bunch of book authors here. Nish Sivakumar and Tom Archer come to mind immediately. So do Christopher Duncan and Sacha Barber. I am sure there are many more.
Within you lies the power for good - Use it!
|
|
|
|
|
I started coding proper in 1983 when I got my first computer a 48K ZX Spectrum.
I wrote my first database engine which was able to save all of 12 records due to the lack of memory.
I now work as a developer and know what you mean about being a 'manager' - I have always been a 'technician' wanting to do the work myself rather than telling others how to do it.
My professional career started in 1990 when I cut my teeth as a COBOL programmer.
Also 80+ hour weeks sounds a bit much.
Having said that in a sense I am working most of the time as I am frequently thinking of how to solve issues when I am not working at the computer.
However I could never work 80 hours flat out. I find my 45 minute lunchtime walk is one of my most productive times when I am away from the computer thinking of how to solve particularly knotty problems.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
modified 17-Jun-14 16:33pm.
|
|
|
|
|
Well compared to the others (and you) I'v just started.
But still I had moments (the past 6 months) where I truly didn't like my job, but that's because I was doing more support / project management than programming (If I wrote 10 lines of code in the past 6 months not including this week, it's a lot).
But then I get a project in winforms / wpf and I start to enjoy it again.
Hell I even started to enjoy doing MVC (untill it all went down hell and the whole support / project management thing came up)
I'v had a few jobs in my professional life (not all programming but most) and I'v learned one thing, no matter what job you do or company you work for their will always be something that bugs you. All you can do is try to limit the amount of things that bug you.
Anyway my 2 cents (not worth that much compared to the experienced old guys around here). 
|
|
|
|
|
I've been coding since early 2010 (so more or less five years). I love it at 25, and hope I still love it at 52 
|
|
|
|
|
As I posted just last week, I've been at the same company (sort of) for 36 years.[^]
However, I had two summer jobs before that where I:
worked at the Jet Propulsion Laboratory (JPL) programming data analysis for the Viking Mars Orbiter, and then
did Operating System (TOPS-10/Tops-20) support at Digital Equipment Corp.
A positive attitude may not solve every problem, but it will annoy enough people to be worth the effort.
|
|
|
|
|
With 25 years of earning a living by coding I'm about ready to hang it up, as I didn't start coding till my mid 30s that make me an official old fart. The only time I would work 80hrs in a week is if it was self imposed and I agree with others that your PM needs to be sacked if you need to regularly work those sort of hours to meed deadlines.
After 10 year in the same, very lucrative, contract it is finally coming to an end and I am dammed if I can figure out what to do next. I enjoy coding and mentoring others but with the demise of Silverlight I have lost my web expertise and MVC is a dog so it will be either WPF or retire or a complete change.
I think I fancy being a small tour bus driver in one of the Oz wine regions.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
_WinBase_ wrote: I've been writing & supporting code for commercial and bespoke (mainly business) systems since 1978 on many different platforms and languages, and 36 years later I still love it, still do it for a living
Me too - coding professionally since Jan 1978.
I went through the project management stuff, became CIO, didn't enjoy it so went back to development.
In the meantime I qualified as a teacher (IT and Science) & would give my left nut to be able to stop working for the man and teach full time - but getting a full time teaching job in Australia is all but impossible unless you are a) willing to relocate to woop-woop or b) just graduating from Uni.
Was actually offered a 6 month teaching contract recently, and just had to turn it down, because I can't afford to gamble on getting work at Xmas time - and can't afford to just not work.
The passion I had tends to die when I am working for a company I don't'feel' for.
If I was braver, I'd give it up and teach, and work outside school hours developing my own stuff - but I'm not a gambling man!
Hopefully I can find a job, ideally with a small company, developing interesting software, where I can learn new things and enjoy the passion again... (I'm waiting for the phone call now!)
|
|
|
|
|
I feel much the same way. I've done all sorts of things since some mad maths teacher introduced me to programming in my sixth form (in 1972!), from working in a bar to senior management, but development has always been my first love.
It is noticeable how the same ideas and 'paradigms' keep re-appearing under different names or guises, but embody the same principles. (We've gone from Procedural, to Object Oriented, through Procedural again to Functional, and now we seem to be creeping back to a less dogmatic version of OO. TDD seems to have peaked, Agile likewise (and these after pushing out all the previous development methodologies that used to be so enthusastically embraced, even by government). I still like to think of myself as a Systems Analyst, as that is what I spend most of my time actually doing, in order to discover what it is the customer actually wants to achieve and with what equipment, but how often do you hear that term used these days?
If there's one thing I've learnt over the years, it is - in very simplistic terms - that programming is programming, all the other paradigms and methodologies are different (sometimes good, sometimes bad) variations on the syntactic sugar so often decried by proponents of one language about another!
I too have reached the point where, whilst still enjoying the work, I feel I would like to do something else, and I'm considering reverting to my original scientific path of chemistry...
|
|
|
|
|
Coding, as in writing a program, was not interesting beyond the first 3 years for me.
Though I occasionally wrote code for another 15 or more years, I found solving the problem (designing and architecting) more interesting. Once I knew how to solve the problem, I had no interest in writing the code.
|
|
|
|
|
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..
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
