Programming professionally
-
What would you do if you couldn't program professionally anymore to make a living?
I've actually been there. After burning out from this job at the end of the last century, I became a fishing guide and professional tournament angler. I've since been dragged (kicking and screaming) back into the development world, but I have to say that I like having money again.
You are here - through no fault of mine!
-
What would you do if you couldn't program professionally anymore to make a living?
Programming already is my fall-back career. In real life, I was a chemist - computers an entertaining tool. About all that's left that I know how to do (that isn't hard work) is taking pictures of kids. Either that, or a gigolo. Maybe I should try to take full advantage of my keyboard abilities and become a cashier at "Trader Joe's".
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"How do you find out if you're unwanted if everyone you try to ask tells you to stop bothering them and just go away?" - Balboos HaGadol"It's a sad state of affairs, indeed, when you start reading my tag lines for some sort of enlightenment?" - Balboos HaGadol
-
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.
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.
-
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.
Wouah! Now that comes from the heart!
kirsty pollock wrote:
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.
You should go watch yourself a good ol' schwarzy' movie, and you'll be quick and fit in no time again! Or maybe time to write a book or start a thesis...
-
Wouah! Now that comes from the heart!
kirsty pollock wrote:
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.
You should go watch yourself a good ol' schwarzy' movie, and you'll be quick and fit in no time again! Or maybe time to write a book or start a thesis...
:-) I've thought about a book/paper. Maybe I should - as it'll probably take a good few years before anybody else gets round to it. (unless it already exists... or someone else is now inspired to do it)
-
What would you do if you couldn't program professionally anymore to make a living?
Fashion Model. Is that part of UML?
-
I'd roam the Texas hill country absolutely naked and make a name for myself...
"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/2001Would you do that by foot, horse or motor bike?
-
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!!
I've been there for the last 3 years... I guess I don't have any choice but to howl at the moon :| Though I would prefer not to do it naked on a roof. Perhaps I'll have sense enough to go out in the woods when I finally go insane. More than likely the ulcers will get me first. X|
S.Nowlin ----------------------- I'm a Techwriter Monkey -- handy, just less useful than the Bathroom Monkey.
-
What would you do if you couldn't program professionally anymore to make a living?
Either teach, farm or do building construction. Teaching would be the most psychologically satisfying, the other two are for more physical needs.
-
What would you do if you couldn't program professionally anymore to make a living?
Drool on myself. Wait for supper. Grab the nurse's breast.
-
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?
Well, if I couldn't program professionally any more I'd *like* to get some additional pilot ratings and fly for a living. However - there really isn't much money in that and I'm probably too old to work that market now so I'd probably drive a tour bus or something. -CB :)
-
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