|
Coding is my life. I love it. Happy coding frnds
|
|
|
|
|
And not troubleshooting build issues, or wrestling with git, or figuring out how someone broke the installer...
But I still love cranking out code even after 30+ years.
|
|
|
|
|
Repetitive work kills me a little every time
I do not fear of failure. I fear of giving up out of frustration.
|
|
|
|
|
Mohibur Rashid wrote: I do not fear of failure. I fear of giving up out of frustration.
I like your signature very much.
In order to tomorrow,come on!
|
|
|
|
|
thank you
I do not fear of failure. I fear of giving up out of frustration.
|
|
|
|
|
Coding is fun, if you're in a good and smart team, more fun. But sometimes it's luck, you can't always work with a harmonious team...
|
|
|
|
|
I enjoyed a lot developing software on different platforms. But, working on the same subject are, oh boy I don't want to even think about it.
If you've never failed... You've never lived...
|
|
|
|
|
not so much
Create installers with InstallShield: NO
Support old software with vs 2003 and no hardware to test: NO
Use GIT: No
...
I'd rather be phishing!
|
|
|
|
|
Don't get me wrong, programming is one of my hobby and also how I make a living out of it. Still coding is not fun. Would you say solving a differential equation fun? You get the satisfaction when it is completed. However, I enjoy more building something more physically like a shed or a bike from scratch.
|
|
|
|
|
Good point ... I voted simply "NO", because fun can be associated with ".. an enjoyable distraction, diverting the mind and body from any serious task ...". Sure there is a sense of enjoyment in programming but calling it fun is perhaps way too much
|
|
|
|
|
While if I was given a week to do whatever I wanted to do my first choice would not be to code the days and nights away, it would be likely more like something related to my music or traveling around exploring the world around me, visiting friends. I don't 'like' coding THAT much to say that I do it for fun, but as a vocation I find it challenging and engaging and THAT what I desire most in a vocation so it is what I prefer.
|
|
|
|
|
What if you're building software to dig ditches...?
|
|
|
|
|
I'm probably one of the few people here who has dug ditches and written code for a living so I'll try to evaluate the digging ditches vs writing code question:
Fun factor: Not much in it, to be honest. Digging ditches allows you to think about whatever you like whereas writing code makes you think about writing code. There are distinct disadvantages to both. Verdict: draw.
Money: Generally slightly better when writing code. Verdict: coding.
Health impact: Digging is bad for the back, coding isn't great for it. Coding ruins the eyes. Digging is great for general exercise, coding really, really isn't. Verdict: digging ditches.
Work/life balance: Digging ditches: You turn up, you dig ditches, you go home. Coding: You turn up, you write stuff, someone decides that what they asked for wasn't what they wanted and you're there 'til tomorrow morning. Verdict: digging ditches.
Prestige: People's eyes don't glaze over when you tell them that you dig ditches for a living. Verdict: digging ditches.
Self-fulfillment: You dig a ditch and someone fills it in a while later. You write some code and someone replaces it a while later. Both tasks are utterly ephemeral and, to paraphrase the immortal words of Morrissey, you know that you'd feel more fulfilled making Christmas cards for the mentally ill. Verdict: dead heat.
Final score: Digging ditches 3 Coding 1
The other key advantage to digging ditches for a living is that no-one asks you to fix their lap-top - let's count that as a goal in injury time and call it 4-1 to the diggers.
Slogans aren't solutions.
|
|
|
|
|
|
PeejayAdams wrote: Digging ditches: You turn up, you dig ditches, you go home. Coding: You turn up, you write stuff, someone decides that what they asked for wasn't what they wanted and you're there 'til tomorrow morning. Verdict: digging ditches. Well, no. I am paid the very same amount, corresponding to 40 hours/week, regardless of how much over-time / quality work I do. So I wake up, code, go home. For me it would be 2-2.
DURA LEX, SED LEX
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
I just hate having to do boilerplate code, over an over. Before you flame me, I'm not talking about boilerplate that can be automated.
Usually usually happens when I have to develop CRUD's, Data models and Factory methods. So boring and repetitive, requires the use of exactly one neuron to accomplish and all the other neurons keep distracting the one neuron from doing the job.
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson
Our heads are round so our thoughts can change direction - Francis Picabia
|
|
|
|
|
There's nothing else in life I ever want to do than build software.
(Let the flaming begin.)
/ravi
|
|
|
|
|
When I code for myself it's like painting the Mona Lisa. I have a vision in my head and just go for it. It's why I got involved with it to begin with. But at the job it becomes a constant battle with idiots over non-sense.
|
|
|
|
|
Agreed. I find myself in the same boat.
When you are dead, you won't even know that you are dead. It's a pain only felt by others.
Same thing when you are stupid.
modified 19-Nov-21 21:01pm.
|
|
|
|
|
I enjoy coding the most when there are challenging works. Else i try to innovate and see what I could do with the piece of code i am writing. And most of all I am paid for Coding
|
|
|
|
|
|
+ Coding at work, on projects I can choose myself:
It's rare but it happened. I enjoyed when I had to optimize the rotations of buffers with SIMD, or apply a Look Up Vector to a buffer as fast as possible with SIMD (I didn't enjoy the headaches though, but it counts like an hangover). I also enjoyed developing a brand new algorithm to reliably find a particular feature in the images we process, which used a mix of image math operators and optimizations with both SIMD and linearization of pointer arithmetic.
DURA LEX, SED LEX
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
Solving the problem in my head is fun.
Coding the solution is grunt work.
Just my two cents.
YMMV.
|
|
|
|
|
Seeing the numbers dance...
|
|
|
|
|
Vivic wrote: Solving the problem in my head is fun.
Coding the solution is grunt work.
You maybe need to change your dev tools. Personally I like to code with Visual studio 2015.
|
|
|
|