top of page

Three tips on logging your code

  • Nov 23, 2022
  • 1 min read

Logging is like brushing your teeth every morning. The more you do it, the less hassle it seems. When your program crashes, logging gives you the insight to track and debug your code.


So, here are three best tips we find useful while logging:


π‘Άπ’π’π’š π’π’π’ˆ π’π’†π’„π’†π’”π’”π’‚π’“π’š 𝒂𝒏𝒅 π’•π’†π’„π’‰π’π’Šπ’„π’‚π’ 𝒔𝒐𝒖𝒓𝒄𝒆 𝒄𝒐𝒅𝒆 - we often find programmers overlogging causing significant time loss to filter when an error occurs.


𝑺𝒕𝒐𝒓𝒆 𝒕𝒉𝒆 π’π’π’ˆ π’Šπ’ 𝒂 π’”π’Šπ’π’ˆπ’π’† π’π’π’„π’‚π’•π’Šπ’π’ - when working on a project in a team, it is best to make the log visible to everyone involved for better efficiency and avoid miscommunication.


𝑷𝒓𝒐𝒑𝒆𝒓 π’Šπ’π’…π’†π’™π’Šπ’π’ˆ - Categorize and document with a universal language. It makes it easier to recheck the code over time.


There you go.


πš‚πšπšŠπš›πš πš•πš˜πšπšπš’πš—πš πšŠπš—πš πšœπš‘πšŠπš›πšŽ πš’πš˜πšžπš› πšπš’πš™πšœ πš‹πšŽπš•πš˜πš .




Β 
Β 
Β 

Recent Posts

See All

Comments


©2023 by DevOps Codes. Proudly created with Wix.com

bottom of page