Member-only story

Top Signs of a bad Python Programmer — Are you doing these?

Dhaval Thakur
2 min readNov 16, 2021

--

We all know that python is a versatile language and it can be used by many, front-end developers, back-end developers, and obviously by data analysts and data scientists. We do code logic, algorithms, but there’s a way that every coder should follow in order to produce an output with as much efficiency.

Source: Github

In this article, I am going to talk about some of the practices that coders do which they should DEFINITELY avoid!

Top 5 things to avoid!

  1. No comments is bad — people forget and you should comment your code.
  2. Too many comments is also bad — you should feel the border line.
  3. No abstractions is bad — they didn’t develop Python for you to write Assembly-style wall of code with no functions and/or classes. Copy-pasting your code is bad — use functions when you catch yourself doing it.
  4. Too many if/else closures is bad — if that thing goes into the 5th tabulation level, you know something isn’t right.
  5. Not separating logically separate blocks by spaces and empty lines is BAD — one more time, don’t make it look like a dead wall, spread things out!
  6. Bonus: Bad variables and function names are bad

Using Import * everywhere!

--

--

Dhaval Thakur
Dhaval Thakur

Written by Dhaval Thakur

Data Enthusiast, Geek, part — time blogger. Every week 1 new Data Science/ Product Management story 🖥 I also write on Python, scripting & blockchain

No responses yet