Programming professionally
-
What are the signs of getting burned out? Getting tired of being (approximately) 10 years ahead of the curve (in my personal case, 'Agile' type development, ORM/data layers, frameworks, TDD/Unit testing frameworks/continuous integration - I've written my own tools for them all... since back when I was at uni in the 80's...) Realising it's only the illusion of change that we have in development. Realising that you are writing the same damn apps over and over - whilst the tech changes under you so fast that you actually are no better/faster at actually delivering a working product. Being tired of running to stand still - if you study really hard *in your own time* you can just about stay as good as you were after about 5 years in the biz. In the few areas where there is design continuity, being tired of seeing all the same mistakes made all over again... (dreadful database design, over-engineering, under-engineering, 'hacking' to meet a time schedule, lack of client involvement, premature optimisation, optimising without metrics). Seeing the whole arena move in what seems like rather pointless directions - e.g. making web apps act like WinForms apps (except slower) by dint of much complex autogenerated code, seeing the database side engulfed by new tools with their own syntax and learning curve - none of which is necessary if you knwo the SQL and a programming language, seeing the proliferation of a kind of thinking that wants to do everything by ever-more config files - rather than the tool actually designed for the job (i.e. a standard programming language that everyone can follow). Knowing that going for architect only distances you so fast from the tech that you'll be out of touch even faster - and even less useful. Knowing that *WE* made it this way - we wanted a pure mertiocracy, we (when we were young) wanted a field where age and experience didn't matter so much as quickness and cleverness. Being just tired of it all.
kirsty pollock wrote:
Realising it's only the illusion of change that we have in development. Realising that you are writing the same damn apps over and over - whilst the tech changes under you so fast that you actually are no better/faster at actually delivering a working product. Being tired of running to stand still - if you study really hard *in your own time* you can just about stay as good as you were after about 5 years in the biz.
Interesting - I've thought many times exactly the same thing.
kirsty pollock wrote:
Seeing the whole arena move in what seems like rather pointless directions - e.g. making web apps act like WinForms apps (except slower) by dint of much complex autogenerated code, seeing the database side engulfed by new tools with their own syntax and learning curve - none of which is necessary if you knwo the SQL and a programming language, seeing the proliferation of a kind of thinking that wants to do everything by ever-more config files - rather than the tool actually designed for the job (i.e. a standard programming language that everyone can follow).
Again ... I've thought the exact same thing. I've been watching our product move "to the web" and have constantly asked myself "why is this necessary"? I do see the point of being able to get to an application from "anywhere" but I've never cared for the web as an application platform myself. Perhaps that's why I prefer to stay in the low-level business logic. I've written some web GUI code - and even with all the sophisticated tools available I absolutely hate the whole POST/GET, programming inside a browser model. I think all this is partially why I don't do this as a "hobby" any more. Part of it is because I've been at it for over 30 years and am simply tired when I get home and don't feel like working any more. -CB
-
Don't forget, he's my bitch and he does what I tell him to do.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001:laugh: :laugh:
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
-
What are the signs of getting burned out? Getting tired of being (approximately) 10 years ahead of the curve (in my personal case, 'Agile' type development, ORM/data layers, frameworks, TDD/Unit testing frameworks/continuous integration - I've written my own tools for them all... since back when I was at uni in the 80's...) Realising it's only the illusion of change that we have in development. Realising that you are writing the same damn apps over and over - whilst the tech changes under you so fast that you actually are no better/faster at actually delivering a working product. Being tired of running to stand still - if you study really hard *in your own time* you can just about stay as good as you were after about 5 years in the biz. In the few areas where there is design continuity, being tired of seeing all the same mistakes made all over again... (dreadful database design, over-engineering, under-engineering, 'hacking' to meet a time schedule, lack of client involvement, premature optimisation, optimising without metrics). Seeing the whole arena move in what seems like rather pointless directions - e.g. making web apps act like WinForms apps (except slower) by dint of much complex autogenerated code, seeing the database side engulfed by new tools with their own syntax and learning curve - none of which is necessary if you knwo the SQL and a programming language, seeing the proliferation of a kind of thinking that wants to do everything by ever-more config files - rather than the tool actually designed for the job (i.e. a standard programming language that everyone can follow). Knowing that going for architect only distances you so fast from the tech that you'll be out of touch even faster - and even less useful. Knowing that *WE* made it this way - we wanted a pure mertiocracy, we (when we were young) wanted a field where age and experience didn't matter so much as quickness and cleverness. Being just tired of it all.
"Realising it's only the illusion of change that we have in development" So very true! The moment I realized this was the case ( a year or so ago), my love for programming crested.
-
What would you do if you couldn't program professionally anymore to make a living?
Since I write web apps, Internet marketing would be my choice alternate profession. Heck, it's my choice for a primary profession, I'm just not there yet. It's a nice step back from the technical side of programming websites, while still being involved in the Web and making a ton of money too.
-
What would you do if you couldn't program professionally anymore to make a living?
-
What would you do if you couldn't program professionally anymore to make a living?
I'd be a Mathematician. It strikes me as a very similar profession. :cool:
-
What would you do if you couldn't program professionally anymore to make a living?
-
What would you do if you couldn't program professionally anymore to make a living?
-
What would you do if you couldn't program professionally anymore to make a living?
Either carpentry (cabinet making in particular) or teaching.
Paul
-
when the only things you do are: wake up, eat, program, eat, program, eat, go to sleep...dream about programming...repeat...
Steve _________________ I C(++) therefore I am
"Wake up" check "eat" check if (DayofWeek.IsMorning) "program" check "eat" check" if (DayOfWeek.IsAfterNoon) "program" check "eat" check "hang out with friends family, enjoy anything not technology for the next 4 hours" check "go to sleep" check if (DayOfWeek) "dream about programming" check Going through your list i almost thought i was in danger, thank god for my daily 4h break.
-
What are the signs of getting burned out? Getting tired of being (approximately) 10 years ahead of the curve (in my personal case, 'Agile' type development, ORM/data layers, frameworks, TDD/Unit testing frameworks/continuous integration - I've written my own tools for them all... since back when I was at uni in the 80's...) Realising it's only the illusion of change that we have in development. Realising that you are writing the same damn apps over and over - whilst the tech changes under you so fast that you actually are no better/faster at actually delivering a working product. Being tired of running to stand still - if you study really hard *in your own time* you can just about stay as good as you were after about 5 years in the biz. In the few areas where there is design continuity, being tired of seeing all the same mistakes made all over again... (dreadful database design, over-engineering, under-engineering, 'hacking' to meet a time schedule, lack of client involvement, premature optimisation, optimising without metrics). Seeing the whole arena move in what seems like rather pointless directions - e.g. making web apps act like WinForms apps (except slower) by dint of much complex autogenerated code, seeing the database side engulfed by new tools with their own syntax and learning curve - none of which is necessary if you knwo the SQL and a programming language, seeing the proliferation of a kind of thinking that wants to do everything by ever-more config files - rather than the tool actually designed for the job (i.e. a standard programming language that everyone can follow). Knowing that going for architect only distances you so fast from the tech that you'll be out of touch even faster - and even less useful. Knowing that *WE* made it this way - we wanted a pure mertiocracy, we (when we were young) wanted a field where age and experience didn't matter so much as quickness and cleverness. Being just tired of it all.
You old guys are depressing... I "wanted" to excel to a architect status but now i think I'll just keep updating code generators with the latest technology and run that for 15 min and bill for 6 hours. Then i won't have to come onto a post about great jobs and depress the new guys with how empty their future will be. Jordon.
-
What would you do if you couldn't program professionally anymore to make a living?
-
wolfbinary wrote:
I'm wondering what the signs are
When you dread getting out of bed in the morning because it's a work day... When you feel the need to cry yourself to sleep at night, or self medicate with alcohol... When you dread Sunday evenings because Monday is the start of the working week... When you sigh instead of get excited by having to work late, again...
-------------------------------------------------------- Knowledge is knowing that the tomato is a fruit. Wisdom is not putting it in fruit salad!!
GC.Collect(this.Life, this.CurrentJob); // ;P
peace & serenity
-
wolfbinary wrote:
I'm wondering what the signs are
When you dread getting out of bed in the morning because it's a work day... When you feel the need to cry yourself to sleep at night, or self medicate with alcohol... When you dread Sunday evenings because Monday is the start of the working week... When you sigh instead of get excited by having to work late, again...
-------------------------------------------------------- Knowledge is knowing that the tomato is a fruit. Wisdom is not putting it in fruit salad!!
-
What would you do if you couldn't program professionally anymore to make a living?
The only thing I've done lately besides programming is night auditor at a hotel (glorified front desk clerk), and I'd kill myself if I had to do that again. I got good grades in accounting and economics in college (4.0), so I'd probably become a CPA. I've also enjoyed writing training manuals and teaching classes, so that's an area I'd consider as well. Of course, I'd still be a closet programmer at home...
Meddle not in the affairs of dragons, For you are crunchy, and good with mustard.
-
What would you do if you couldn't program professionally anymore to make a living?
-
What would you do if you couldn't program professionally anymore to make a living?
I love development but if I had to leave I'd probably get a job in construction, like an Office Space thing. After being cooped up all day long in an office with glowing monitors it would be nice to be doing some heavy labor at 6am in the brisk air and later the sunshine. I'm sure I'd find some sore muscles that I forgot were even there, but it would be nice. Granted I live in Southern California. I don't think I'd look so fondly at waking up at 4am just to work all day in the rain.
-
What would you do if you couldn't program professionally anymore to make a living?
wolfbinary wrote:
What would you do if you couldn't program professionally anymore to make a living?
Holy mackerel, this is a long thread. I'd go into porn. Of course, that is if the porn industry needs another hairy dude like Ron Jeremy and one less blessed, sigh. I guess my acting nick name could be my screen name?
Any suggestions, ideas, or 'constructive criticism' are always welcome. "There's no such thing as a stupid question, only stupid people." - Mr. Garrison
-
What would you do if you couldn't program professionally anymore to make a living?
I would still program as a hobby. Professionally, I would shift to assisting my wife raising meat goats. We have a nuber of herd improvement ideas, but do not have the time to implement them. Success in this venture requires multiple generations of goats.
-
This is so true it hurts! Spent 10 years as an "Architect" now have spent the last 2 catching up with develpment. Thank God it is just the same ol stuff with new names.
Where do you start? I used to consider myself highly qualified with C, Assembler, C++ etc, but that was like 10 years ago. My last IDE was MS VC6. Then I became a designer/algorithmeter. Now, my office is being shut down. Where do I go to get started programming again? I have still don't know what .NET really means. REALLY!