Skip to main content

The successful developer

6 replies [Last post]
jseltzer
Offline
Joined: 2003-06-12
Points: 0

I've learned one thing about successful developers. They aren't necessarily the smartest. They're the quickest to make decisions. Indecision is a killer to the development process. Successful developer's find the shortcut solutions. They don't reinvent the wheel. They copy. They finish on time and the managers love them for it.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
jseltzer
Offline
Joined: 2003-06-12
Points: 0

When I say copy, I'm talking about using existing project code that's available to you. More often then not, if you think you need to write it yourself, you haven't looked long enough to find something that's already written for you. Code that's been around for a long time is code that works.

riccardocossu
Offline
Joined: 2005-09-22
Points: 0

I agree, although I wouldn't use the word 'copy'; resuse is quite a different thing and I think it's most often than not a very good way to make things work.
There's one thing that keeps many developers from using other's work in their projects: to effectively use a framework or a library you have to study it and it takes time spent 'not doing anything'. Many developers simply hate doing this.
Ideally I would spend all of my time working to create the best framework ever, although as a professional I need to get the work done, so it's good news if someone's already done what I need!

fachim
Offline
Joined: 2005-08-24
Points: 0

Hey guys,

i read the topic it was great, i agree with all of you. since we have different level and condition in developing work. so we have different way on solving it.

for they who just starting to code, do practising and typing all the code is helpful. its good, its can help you to mastering, remember the concept, use and implementations.

for they who have been expert in coding, its a good way to copy some code for time saving as long as it will not raising some bugs.

to write the code and clean coding is better, but sometime we have to do fast and deadline time is up and copying is the way, but dont forget to check the integrity and make sure the quality is the first priority.

regards,

fachim

vieiro
Offline
Joined: 2003-06-11
Points: 0

Sssshhhhh. Don't speak up. I have a dozen well-trained monkeys copying-and-pasting as mad ...

(I couldn't resist) ;-)

Now, seriously. Is there any relationship between "finishing on time" and "quality of product"? What is the most important for you?

And for your business?

Cheers,
Antonio

Message was edited by: vieiro

gerrit_jvv
Offline
Joined: 2005-09-26
Points: 0

I agree that decisions can kill a project, but if you just copy and paste code, you can endup with alot of spageti code. Of course you would finish parts now, but then what happens when something changes? you have to re-do everything. Errors? bugs? if bugs appear in a 10 000 lines of copied code, you would have no idea where they are and how changing them would affect the rest of the program. (My project in total contains over 100 000 lines of code //not counting libraries used)

I would rather go for steady pase development at which in each stage you design, implement and test.

I'm not saying re-inventing the wheel, but copy and pasting is not desired. Code re-use should only be done via Components, Inheritance or Aggregation e.g. (COM+, Beans, Classes) and not copy and pasting.

gerrit_jvv
Offline
Joined: 2005-09-26
Points: 0

Spelling correction (Indecision not decision)