|
Sometimes in my code I'll put // Finish and if I don't do it within a short time and go back I sometimes wonder what it was I was supposed to finish. Especially when I did finish and didn't remove the comment.
The less you need, the more you have.
Even a blind squirrel gets a nut...occasionally.
JaxCoder.com
|
|
|
|
|
Or //Hack: Needs refactoring
And when you go back to fix it, it looks fine.
|
|
|
|
|
|
TODO is the ultimate tool of the social procrastinator. Its me telling others that I"ll never come back to this.
Lately, I've been an anti-social procrastinator not even bothering with the TODO because its work to even add it
Hogan
|
|
|
|
|
just looked at my code, there's about 50 TODO, half of them are auto generated MFC code, half are probably at least 10 years old each.
Too lazy to create a ticket and branch and Pull-Request to take them out.
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
And then you need the testing proof for the change.
I love to review user acceptance tests for “delete unreferenced methods” commits.
|
|
|
|
|
I am usually a lot harder on myself with the fix it todo comments. Lots of f words and referring to myself as a mentally challenged crayon eater.
The icing on the cake is that I forget to remove some of these wonderful comments prior to code reviews. the other devs get a kick out of it.
|
|
|
|
|
I never liked 'TODO' comments in the code.
I rather keep a plain text file in the project directory listing all the things that should be remembered and considered. Then I can be sure that I don't overlook a fix because I didn't open that source file. I can more easily sort out a group of related fixes and do them in one cleanup. And I can put in a reminder about planned/desired functionality that doesn't yet have any definite place in the source code of already implemented functionality.
In my text files, the entries are not necessarily limited to strict coding actions. They may e.g. state the defined order of method parameters for this project, or identify the standards to be followed. Sometimes it grows to require a splitting into sections. Some of that information later goes into the system documentation.
|
|
|
|
|
That's also how I keep track of enhancements. But a non-trivial bug calls for a comment in the code to notify others who may be looking at it.
|
|
|
|
|
|
|
Thanks, I'll look into this. What I currently do is tag some comments with special characters:
And so on.
|
|
|
|
|
|
If you use VS.
GCS d--(d-) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
you can search for all TODO's in a solution. that's what I do. it works perfectly for me.
I do feel that TODOs can get out of hand a lot of times, and so, I try to use them sparingly.
There is also a window that is for using and managing TODOs, etc.
modified 10-Feb-22 16:59pm.
|
|
|
|
|
I do the same, luckily I developed this way of working very early in my career so now I am quite efficient with it.
GCS d--(d-) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Visual Studio has a Task List view which brings them all together which I think is better than having a separate file which may or may not get updated when then 'TODO' is done.
|
|
|
|
|
The very last thing I do before adding to a commit is to git diff, going line by line getting rid of spare spaces and comments like these, as well as taking notes on lines changed.
I do, however, find old notes from past coders very like this, but with dates and initials added. Some are 5 years old - might not be important to fix that, eh?
|
|
|
|
|
|
I thought "you know, that looks like Base64 data to me" ... so I ran it through an online "decoder".
And it's JSON data as Base64 containing her email address, two GUIDs, 4 URLs, and some other rubbish.
No wonder it's so long ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: an online "decoder"
You've not installed DevToys[^] yet then?
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Herself has to have regular background checks (every couple of years) to ensure she's not going to murder the residents of the home she works in.
And this year she can do it online.
But if the button doesn't work - and I'm not going to press it - they provide a text hyperlink to enter manually.
All 677 characters of it ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
At least if it's in an email, you can copy and paste it (into a text editor first, to make sure it hasn't been changed, then from there into your browser).
I can't find the story at the moment, but I'm sure a few years back there was a scan of a job advert in a print newspaper with a link of a similar length.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Richard Deeming wrote: At least if it's in an email, you can copy and paste it
Whoever put together my bank's site thought it would be a good idea to disable click and drag in the browser, so I can't copy things like 12-digit transaction numbers that I like to copy for my own records...
|
|
|
|
|
At my last company the marketing department used to send (by post) a monthly paper bulletin. It was usually about 5-10 pages and each page had at least three printed URLs, which extended to 4 or 5 lines. I sent them an email suggesting they email the stuff to make it easier. Their reply was the usual, "Thank you, we will take your suggestion under advisement" - translation: "Dude, you know nothing." (which of course is true, but that is another matter).
|
|
|
|