General programming question, but asking it here as I suspect every language community is a little bit different. What is the correct balance between (extracting out as much logic as possible to other functions + making one's variable/method names explain the code) and (writing detailed comments)?

• bitwiseOperatorsDemo

  1 0 2.6 C

  Used my answer to a Codewars challenge to soup up a Udemy assignment. Wrote this on 01/01/2021.

This is an example of how I used to comment ("to comment the heck out of everything") when I first started.

• BinarySearchTreeExercises

  6 0 0.0 C++

  Practicing with Binary Search Trees

This is theDS project that I have spent 2 weeks on and have not commented almost at all on. A red black tree map, I did not have anything well defined concerning how much I was going to end up doing with it, so it has evolved into what it is now. If I do anything more with it, it will probably be just to add in the rest of the special members and maybe 2 unary operators (+ and -) to the Iterator.

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• Options

  1 0 3.6 C

  My first C Project, a console app (by sethvan)

In case you have the time, I have another program from actually that same time period ( also in C but before I started commenting ) and that additionally after a friend gave me advice, I several months later refactored quite a bit to make it look cleaner and more self-explanatory. It currently has no comments I believe. Could you let me know if it's not clear enough without comments? The opposite scenario so to speak. If you have the time that is. This is it.

Suggest a related project