![]() ![]() So never treat it as a finite set of best practices. There is never an exhaustive list of “best practices.” These are a few simple ones I learnt in the industry, that helped me improve my coding and work in a collaborative environment. The 8 best practices I have listed here are in addition to what Anmol has mentioned in his article. So as long as you are writing simple, understandable code that someone else can improve upon, you are writing “Industry standard code”. ![]() If that is not possible, software industry won’t scale beyond individuals. Sometime later, a completely different person, working for the same firm, should be able to read my code, understand it, make improvements on it, or fix a bug in it, or integrate it with another piece of software. If I write some piece of code while working for a firm, the code I write is owned by the firm. But it is nothing other than readable, reusable, modifiable code. “Industry standard code” may sound fancy. But after being part of a team, I learnt these best practices from my colleagues and wished I knew and followed these small steps early on. ![]() I did not follow these best practices before going to the industry. Then I felt like “Well, I can add a few more to this list by Anmol.” Hence, here I am, writing this blog post. It touches on simple yet effective best practices that can improve your code quality. I recently read a good article by Anmol Tomar on Python Best Practices. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |