|
'Cause chicks dig programmers.
|
|
|
|
|
thought that be obvious
dev
|
|
|
|
|
?
.-.
|o,o|
,| _\=/_ .-""-.
||/_/_\_\ /[] _ _\
|_/|(_)|\\ _|_o_LII|_
\._. |\_/|"` |_| ==== |_|
|_|_| ||" || ||
|-|-| ||LI o ||
|_|_| ||'----'||
/_/ \_\ /__| |__\
|
|
|
|
|
Nothing ever reaches "Code Complete" IMHO.
Pendin Approval
|
|
|
|
|
I can't believe I am admitting this publicly: I think enjoy running down bugs and fixing them or changing the design slightly such that there is no need to use the problematic code. Especially the particularly difficult ones. Especially when there is a noticeable improvement to user experience. Fixing bugs will never replace fresh code, but it's the best way to rapidly restore a sense of accomplishment while still being useful to the forward momentum of the project.
Regards,
-B
"[F]reedom isn't a licence, it's responsibility." [David Gerrold, Author's Note in "The Man Who Folded Himself", 2003, p. 119]
|
|
|
|
|
and Writing the first code as well.
If something was designed and started correctly, the most difficult part of the work is almost done
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpfull answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Does really everyone paint by numbers and stay within some framework? Nobody here working on a project that's to 90% or more own code? No more building something that nobody else built before?
Sent from my BatComputer via HAL 9000 and M5
|
|
|
|
|
In the PLC-Programming, I need to code 90% of the programm on my own, creating personalized functions for specific tasks. I have build my own "bibliothek" over the years. But even though I continue chancing my own functions to make them better or to make them solve new problems.
Personally I prefer it, it gives me much more satisfaction to know that something is working thanks my very own work.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpfull answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
.... because I'm doing almost all phases.
Nuclear launch detected
|
|
|
|
|
because the question is "What is your favourite phase of software development?", not "What are all the phases of software development that you do?"
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
|
I assume you employ a two phase development methodology.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
... getting paid, my personal favorite.
|
|
|
|
|
If I start early on the main development cycle. If I'm jumping in at the end, finding ways to break my coworkers code is much more fun than tying up all their loose ends.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Actually, the best part is allocating functionality between hardware and software at the beginning, then integrating the two to make them play nice together. But neither was listed; I don't suppose many people do that sort of thing anymore.
Will Rogers never met me.
|
|
|
|
|
Roger Wright wrote: the best part is allocating functionality between hardware and software at the beginning, then integrating the two to make them play nice together.
I work in the Medical Diagnostic sector, we do that kinda stuff.
|
|
|
|
|
In the Cranking out code phase it satisfies the inner drive to create and get er done.
|
|
|
|
|
Improving design of a specific part of the system that grow over time and shows symptoms of needs for change, refactoring and when done, watching the resulting masterpiece in action. Just love it!
|
|
|
|
|
Favorite part is new solutions to old problems/methods - followed by approving nods from all who gaze, worship, and offerings.
Why else would anyone do it ?
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "As far as we know, our computer has never had an undetected error." - Weisert | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
I'd worked many years in maintenance area and I have to say: It sucks!
It is a endless task to make the product work as expected!
Fabiano
|
|
|
|
|
I work with a few developers which all they do is maintenance. It is because they don't have the skills to start anything new. They have to have examples of what works within the framework and then make small changes.
There are times when I like maintenance because it is quick and easy but I wouldn't want to do it all the time.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
What? There's usually nothing "easy" about it. It's the thrill of the hunt, the problem solving, the satisfaction of making something work correctly or more efficiently which most developers seem to be not very skilled at doing. I've often been called in to finish up a developer's coding and make the application work as it was intended after the developers say it's done. Sure we only make small changes when doing maintenance but the hard part is figuring out where to make the change in someone else's code with little documentation or help.
|
|
|
|
|
98% of the work in 2% of the time
2% of the work in 98% of the time
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpfull answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
what about the sipping coffee phase??
as if the facebook, twitter and message boards weren't enough - blogged
|
|
|
|
|
Naaaah!
What about the getting blamed phase?
|
|
|
|