- Feature Articles
- CodeSOD
- Error'd
-
Forums
-
Other Articles
- Random Article
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Yes, it is true that this a
TODO.Admin
I think most (if not all) IT departments need at least a month to do everything marked as 'todo'
Admin
This code looks like it's part of a voting machine's software...
Admin
IntelliJ defaults to failing if there are TODOs in your code before committing to source control. I turn that feature off.
Admin
Yeah, I mean I have seen plenty of those "workarounds" in the wild and to be fair, they always get mandated from the top.
Never seen an instance where a developer was like "yeah, it should be secure but I really want 30 extra minutes to implement the pointless corporate rebranding instead". Example is purely made up. Or is it? You'll never know...
Admin
@DQ
A month? Probably more like a decade to retire all the technical debt. TODOs are the teeniist tip of the antenna on top of the iceberg.
Admin
I'll add the time-honored tradition of making people implement authentication who have no skills in that area because they're cheap and/or 'know how to do software'. I've seen client-side validation of server credentials twice in the wild (different customers). Twice I explained why this is a really awful idea. Twice I was ignored because 'this is just an internal tool, after all'.
Admin
I make FIXMEs fail builds, but TODOs just be warnings. It's useful to separate the two...
Admin
Really? What happens if you have a variable named "TODO" or "TODOO" ?
Admin
She's got a token to ri-ide... she's got a token to rii-i-iiiide.
Admin
But she don't care!
Admin
You could always just remove the TODOs... It's not like anyone ever gets round to doing them anyway :-)
Admin
TODO: Write witty remark
Admin
Nothing probably. Unless you write comments like // VARIABLENAME: this is what it does
Admin
All variables should be addressed by their ID only. The ID being an index in a lookup table whose contents are located in a separate per project file. The file should contain the type, name and a comment.
Each variable in memory is a struct consisting of a void * to the data, a char* for the type and a char* for the comment.
To use the variables, the developer needs to include the entire configuration file, load the variable by index and apply conditional casting to the value parameter based off the value of the type parameter.
The actual configuration files are developed ad hoc along side the program and their content are not determined in advance. Developers simply add new lines with new variables to the file as needed.
In production the variable values are deployed in a separate config file that can be edited by data entry staff.
Admin
I may start using @FIXME. Thanks
Admin
America has got to be the only country where this kind of code could pass for democracy.
Admin
I’ve never been allowed to do any technical debt or todos because the current sprint has to be completed first.
Admin
That's why waterfall development is better than agile. It is impossible for tech debt to be created with waterfall because no one put "create tech debt" onto the gantt chart, and the gantt chart is the single source of truth.
No, we can't change it to add "remove tech debt", this is the version the customer signed off on a year ago before we started the project. How dare you even create tech debt when you weren't allocated to work on that? This plan was not approved with "create tech debt" on it, you cowboy-coder!