I would say “Don’t use TODOs (in your code) at all”. They are just “broken windows” in your code. If something is a bug and you think that it is important to be fixed - just do it. If you think that something has to be done but it is out of the scope of your current task, note it down somewhere and take ownership of making it happen one way or another. Leaving a comment in your code just puts this responsibility away from you. In my experience this does not work and those type of tasks just pile up.
I know about it, but:
(1) I had slightly different ideas about the format of the CV.
(2) I would like to add a personal blog at some point which will be generated from .MD files in the same repository as your resume.
You said that you "have used in the past". Do you use different solution, right now?
I am Deyan, the developer behind Textstandup.com. I released its first public version few weeks ago and some external feedback will be very useful to me. I have written more about the motivation behind the project here https://medium.com/@ddobrinov/text-based-stand-ups-de741fa6c....
Well, I don't think it is the best answer to your 'challenges'. I mean stand-ups should eliminate the requirement for other meetings as those disturb the focus a developer requires to work, but eliminating that tiny bit of mandatory human interaction seems weird to me (and probably hurts the team spirit in the long run).
I don't mean to be negative, just honest feedback.
No, I completely agree. Having no meetings at all could hurt the team spirit. At the same time I doubt that you have only one meeting per day. This could be the case for small remote companies. I am personally using it and it works well. I have written more about the motivation behind the project here - https://medium.com/@ddobrinov/text-based-stand-ups-de741fa6c....
