Skip to main content

Good programming practices


Over the past few days, I have been pondering over the fact that despite having a good hold on OOPs concepts and apply them while writing code to solve a particular use case, I am still not writing good code.


I have been coding for almost 6 years now. 2+ years of professional coding. When I was in college, I was a wild programmer solving programming contests, DS problems. What I mean is that I only coded to solve the problem, did a lot of dirty coding. I never bothered if the code can be reused, if someone else or I myself can understand it if I looked at it after a few days. I did have a good habit of writing comments. 

When I joined work, I learned many different aspects of how the code was written. Many facts were taken into consideration like code maintenance, reusability, testing etc. I still remember a co-worker who told me if you need to write 10 lines of beautiful code, you should have seen 1000s of lines of amazing code. Due to the pressure of getting things done, I hardly got much time to appreciate the beauty of the logic written wholeheartedly.

I was going through few blogs about best programming practices. Thought it would be good to share them. 

This one is my favorite. Very informative and well-articulated blog post. Will you give a good perception of standard principles and how one has to think before starting to write code.
http://williamdurand.fr/2013/07/30/from-stupid-to-solid-code/

This one talks about how to think and work with best practice methods to be a good programmer.

This one is for professional coding. More technical details to be kept in mind. 

PS: Other than these practices, learning about version control is key to quickly get a hang of things when you get to work. I would suggest learning GIT. You will eventually learn VCS but learn how it is done, why it was done like that will help appreciate the beauty of it even more. 
Few places to start off can be https://www.atlassian.com/git/tutorials - detailed explanation.
https://try.github.io - for practice.
There are abundant video tutorials available about VCS, GIT etc. You can go through them as well. 


Comments

Popular posts from this blog

Concurrency in Go - Visualization

In this blog, let us discuss a program to visualize concurrency in Golang. Reference and source: Program 1: import " fmt " import " time " func main () { var Ball int Ball = 5 table := make ( chan int ) go player (table, 1 ) go player (table, 2 ) fmt. Println ( " mainstart: " , Ball) table <- Ball time. Sleep ( 1 * time. Second ) endres := <- table fmt. Println ( " mainend: " , endres) } func player ( table chan int , playernumber int ){ for { ball := <- table fmt. Println (playernumber, " : " ,ball) ball++ time. Sleep ( 100 * time. Millisecond ) table <- ball } } /* ---------------------------------------------------------------------------------------------------------- Explanation: Please try to visualize on your own before reading the explanation. We will name the two goroutines that are called as player1_goroutine ...

Cycling to Dommasandra - 25km circuit

The following blog post not only inspired me to go for more cycling trips and write regularly because of some valuable, loving comments from friends, it also motivated many of my friends to try it out. https://rkinsideout.blogspot.in/2017/10/the-one-where-raj-went-for-cyclingfirst.html I and my close friend Padma whom I have known from my school days decided to go for cycling. The following week was a Diwali week and most of our friends' had already started leaving to hometowns. We decided to do it anyway. I chose a circuit behind Kadubeesanahalli, Sarjapur as I knew it would be pleasant and also have seen people cycling in these places. The Circuit It was a pleasant ride as it was cloudy was most of the time. From Panathur to Sarjapur road, there were more vehicles on the road, but after Carmelaram, there were fewer people on the road. The road condition also was good till Dommasandra with few patches here and there. Since the road was good, the bigger vehicles were spe...

Python run watchdog along with a flash app

The pre-requisite for understanding this blog post would be the following post. Please go through the following to set the context to understand what is discussed in this post. https://rkinsideout.blogspot.in/2017/10/implementing-file-monitoring-script.html Problem : The flask app was running and was responding to a bunch of curl commands. This was single process thread that was working. When the watchdog api was integrated and initiated with the flask program, the problem was that the watchdog thread was started and the flask app was never started. It was started only when the watchdog thread ended. Since we want both the threads to be running, the watchdog process has to run in the background and the flask app to should run normally so that both functionalities are available for use. Python thread and threading are the options available. The "thread" starts a thread and waits for it to complete before proceeding with the rest of the flow to get execute...