Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. The Lounge
  3. When you learned how to really write code?

When you learned how to really write code?

Scheduled Pinned Locked Moved The Lounge
databasetutorialquestionhelpworkspace
25 Posts 12 Posters 6 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L Lost User

    I've been programming professionally for 33 years - and I still learn something almost every day. The day I think I know it all is the day I'll stop programming.

    ___________________________________________ .\\axxx (That's an 'M')

    P Offline
    P Offline
    programmervb netc
    wrote on last edited by
    #21

    Agreed I learn all the time but my real question is did you have the feeling when you started that you really did not know what you were doing but then after doing work for a few years you feel fairly confident about your skills. Humble Programmer

    L 1 Reply Last reply
    0
    • R Roger Wright

      The university tried to teach me FORTRAN, but I beat them to it, having found a book in the library on FORTRAN II before I started college. They taught me facts - math, physics, chemistry, electronics - but applying them in a logical, efficient manner I taught myself. When my employer asked me to program a new system, I asked, "what language and OS this time?" Then I taught myself both and got to work. Schools should teach a language or two, if only to get students used to debugging their own errors. But that should not be their primary focus; a language is just a tool, not a career choice. A focus on the basics - data structures, algorithms, problem definition and scoping, writing lucid requirements - should be fundamental. Languages change; the basics are eternal.

      Will Rogers never met me.

      P Offline
      P Offline
      programmervb netc
      wrote on last edited by
      #22

      I agree language is not very important it is logic and fundamental things that you will always use. Humble Programmer

      1 Reply Last reply
      0
      • R Rage

        programmervb.netc++ wrote:

        For example I had never used source control,

        programmervb.netc++ wrote:

        had never heard of bug tracking

        That is presently why I am giving config management courses in engineering schools.

        P Offline
        P Offline
        programmervb netc
        wrote on last edited by
        #23

        That sounds promising and progressive considering what many schools teach. Humble Programmer

        1 Reply Last reply
        0
        • D Dave Kreskowiak

          programmervb.netc++ wrote:

          and have a few statements that are near 200 lines of code.

          If you have to have a function/stored procedure that long, you REALLY need to look into breaking it into smaller pieces. Your definitely overlooking some opportunities to divide the problem up there.

          A guide to posting questions on CodeProject[^]
          Dave Kreskowiak

          P Offline
          P Offline
          programmervb netc
          wrote on last edited by
          #24

          I know the post is huge but that is what we are talking about so.... I went ahead and posted it in the DB forum. http://www.codeproject.com/Messages/3609635/Query-Improvement-Related-to-Lounge-Post.aspx[^] Any suggestions are welcome. Humble Programmer

          1 Reply Last reply
          0
          • P programmervb netc

            Agreed I learn all the time but my real question is did you have the feeling when you started that you really did not know what you were doing but then after doing work for a few years you feel fairly confident about your skills. Humble Programmer

            L Offline
            L Offline
            Lost User
            wrote on last edited by
            #25

            Hmmm - a long time ago to actually remember! I think after my first year I was confident enough in my programming abilities to stand up and be counted. I subsequently spent a LOT of time doing research (for example, I actually read through the COBOL manuals, and the OS manuals and learned loads of bits and pieces, which I could then incorporate into my software) The more I read, and experimented, the more I grew in confidence. If there was a Eureka moment it was when I started doing training - both for users and other developers. Having to explain things to others achieved two things; it made me double-check my knowledge, and it made me realise that I really did know more about software development than pretty much anyone else in the company.

            ___________________________________________ .\\axxx (That's an 'M')

            1 Reply Last reply
            0
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • World
            • Users
            • Groups