What makes a good developer?

  • Patuence is a virtue when it comes to being a developer.

    I have actually had people tell me that i have become more patient the more development work i do.

    I have meet a lot of bright people who throw their hands up when things get sticky and they cant find the answer right away on the web.

    I also knwo that i have spent hours and what seems like days trying to find the one fix to the esoteric bug that i have in my code.

    just my 2-cents

  • oh boy, the serious hat just got put back on...

    What you are saying is persistance. Yes, that is something that does help.

    Cheers,

    Crispin

    Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!

  • Don't really agree with that one dalecorry.

    In my opinion, being a good programmer does not depend on (development) language.

    Language is pure syntax and features. Real skill is situated in other subjects : translating user requirements, patience, ...

    Of course, it helps if you master a development language or two . Me personally, I started out with C. Have done some stuff in Java, C++, (Visual) Basic, Delphi, ASP, PHP (and SQL of course ).

    Takes some time (and a lot of failed compiles ) getting used to syntax. And a whole lot of refactoring .

    BTW pleeeeaaaaase, someone get that serious hat away from me ...

  • Well, I'm not sure about that. Learning and mastering languages was the very first thing they impressed upon us in my Masters level Structured Programming Languages class.

    Anyway, for grins and giggles, refer back to my earlier posting from today of VB code:

    What Makes a Good Developer? Logic or Intelligence?

    'Original code by Dale Elizabeth Corey. Do not use this code without owner's permission or else your nose will fall off.

    Private Sub Definition_Of_Developers ()

    Dim Good_Developer as String

    Dim Logic as String

    Dim Intelligence as String

    Dim Cup_of_Java as String

    Logic = "I am a "

    Intelligence = "genius!"

    Cup_of_Java = "Beer!"

    If Me.Boss = "Looking"

    Good_Developer = Logic + Intelligence

    Else

    Good_Developer = Cup_of_Java

    End If

    Me.Answer = Good_Developer

    End Sub

    ==================================

    Form Results

    Boss: Looking

    Answer: I am a genius!

    Boss: Not Looking

    Answer: Beer!

    Edited by - dalec on 06/12/2003 7:58:08 PM

  • To add what was said, a solid understanding is a must in a language.

    Many many times I have found someway of doing something by find a new native function.

    If you understand the logic involved, it's just new syntax and methodology you have to learn. (Most of the time).

    I have chopped and changed between some languages and all the is required is patiance and a help file. oh, and plenty "coffee"

    Cheers,

    Crispin

    Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!

  • Hi NPeeters,

    quote:


    In my opinion, being a good programmer does not depend on (development) language.

    Language is pure syntax and features. Real skill is situated in other subjects : translating user requirements, patience, ...


    agreed with that. Programming 'happens' in the brain. The algos are originated there. The programming language is just a tool to express yourself, whatever it might be.

    quote:


    BTW pleeeeaaaaase, someone get that serious hat away from me ...


    Ok, you've asked for it....

    After killing Crappy yesterday by laughing, here's another attempt.

    http://www.flamjam.com/spank/ (personal highscore is about 150 mph, after some discussions with senior management)

    http://www.skop.com/brucelee/index.htm (takes some time to load)

    and that VERY sophisticated ...

    http://www.alltooflat.com/geeky/elgoog/

    Have fun!

    Cheers,

    Frank

    --
    Frank Kalis
    Microsoft SQL Server MVP
    Webmaster: http://www.insidesql.org/blogs
    My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

  • Frank, is it not to early in the morning for more techie humour?

    Not enough coffee in system yet!

    Cheers,

    Crispin

    Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!

  • quote:


    Frank, is it not to early in the morning for more techie humour?

    Not enough coffee in system yet!


    No, never!!

    Cheers,

    Frank

    --
    Frank Kalis
    Microsoft SQL Server MVP
    Webmaster: http://www.insidesql.org/blogs
    My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

  • OK, that helped a lot ...

    Hope my boss doesn't get in today

  • You'll be amazed how easily you get a new highscore

    quote:


    OK, that helped a lot ...

    Hope my boss doesn't get in today


    Cheers,

    Frank

    --
    Frank Kalis
    Microsoft SQL Server MVP
    Webmaster: http://www.insidesql.org/blogs
    My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

  • Spank has to be the best time filler!

    I got 711MPH. Anyone beat me?

    Cheers,

    Crispin

    Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!

  • quote:


    I once got into trouble during a code review by the client.

    My error handler was called Hell.

    In the code it read: On Error GoTo Hell

    Client lacked the sense of humour....

    Cheers,

    Crispin


    Well now, guess I need to update soem code here as that is pretty much what happens in the errors I catch.

  • What would be nice is you could alias common phrases.

    eg: Declare FU*K_OFF = GOTO Err_Handler

    If your code you could then have: ON ERROR FU*K_OFF

    Cheers,

    Crispin

    Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!

  • quote:


    Spank has to be the best time filler!

    I got 711MPH. Anyone beat me?


    No, didn't spank that fast ... yet

    Anyway, for those that don't have a lot on their hands for the moment (Crappy ??? ), here's a combination of your old-time favorites : pong and tetris. Enjoy...

    http://www.vlees.web1000.com/flash/smash.html

  • Ok, I will be serious.

    1) A good developer should be proficient in at least one programming language tht relates to what they do. They may know several more bu they should be good (if not great) at at least one.

    2) Time estimates should be increased by a factor of 4 to allow for other issues and to come in under time (most always) and be considered a god. This is call the Scottie process by those in the know here. But when it comes to projects I do this and folks believe I perform miracles.

    3) A developer must be willing to put their foot down even if could mean a backlash. For instance if your boss commits you to a project in 1 month but you know it will take 6 say it and make a note so when they ask in a month why not done you can remind them they got you in the fix.

    4) If you deal with customers directly a good developer must be able to talk their language and present concepts in a way they will understand.

    5) A good developer should make good notes (especially in their code) to make it easier on others and themselves when they have to review their code.

    6) Good develoeprs must be willing to expand their knowledge and learn new ways, experiement and explore possiblities in coding.

    7) And finally a good developer must be able to take the slumps and still keep a calm front going especially with the customer and never use negative statements (can't, won't, no, etc) but instead build the relationship by using sidestepping words for stuff you have not accomplished (will be looked into, researching possibilites, work on alternate solutions where limitations arise). This creates a positive reenforcement that your customers needs are important to you.

    All that said here was an error trap that got me in trouble with a customer once.

    If it was an error

    msgbox "Doh!" 'Error occurred

    if bad input

    msgbox "Why you little." 'Bad user input

    if not in a place I would have expected the code to fire

    msgbox "WhooHoo!" 'Why am I here.

    I generally streamline my messages later but accidently released one without the corrections.

Viewing 15 posts - 46 through 60 (of 96 total)

You must be logged in to reply to this topic. Login to reply