Actions
Forum Thread Details
  • Replies 6 replies
  • Subscribers 481 subscribers
  • Views 700 views
  • Users 0 members are here
Related

10 ways to improve your programming skills

squadMCU

Even though, this is more oriented to web development, we could take some ideas:

1. Learn a new programming language

2. Read a good, challenging programming book

3. Join an open source project

4. Solve programming puzzles

5. Program

6. Read and study code

7. Hang out at programming sites and read blogs

8. Write about coding

9. Learn low-level programming

10. Don’t rush to StackOverflow. Think!

 

 

Read the complete entry at AntoArts

Parents

  • Here, here @DAB. I agree with everything you said plus shobhitkukreti advised. I've had the pleasure (wink, wink ....) on trying to 'fix' poorly documented code. I spent a majority of the time just trying to figure out what the original developer was doing ... and thinking. I always remember this and try to build code on the premise; "What if someone else has to fix or work on this". That has always been a good guide and earned me 'kudos' later.

     

    Not only that but I had to ressurect an old project that was 8 years old and port it to a different controller. I was immensly glad I had a ton of documentation (in both source, header and readme files). I didn't even need the books I had on file for reference (altho I did look at them).

     

    If your want to build your reputation, like it appears DAB has, you'll want to become known as the guy who documents his code well.

     

     

    PS: Check out Jack Ganssle's site. He has a good starting reference for coding guides, tools and general knowledge.... www.ganssle.com

Reply

  • Here, here @DAB. I agree with everything you said plus shobhitkukreti advised. I've had the pleasure (wink, wink ....) on trying to 'fix' poorly documented code. I spent a majority of the time just trying to figure out what the original developer was doing ... and thinking. I always remember this and try to build code on the premise; "What if someone else has to fix or work on this". That has always been a good guide and earned me 'kudos' later.

     

    Not only that but I had to ressurect an old project that was 8 years old and port it to a different controller. I was immensly glad I had a ton of documentation (in both source, header and readme files). I didn't even need the books I had on file for reference (altho I did look at them).

     

    If your want to build your reputation, like it appears DAB has, you'll want to become known as the guy who documents his code well.

     

     

    PS: Check out Jack Ganssle's site. He has a good starting reference for coding guides, tools and general knowledge.... www.ganssle.com

Children
No Data