Live data from Hacker News

Auto-expiring TODO notes in Ruby

github.com

41–42 of 42 posts

Re: Auto-expiring TODO notes in Ruby

#41
post #20
post #13

Earlier quoted context omitted.

My TODO comments show up in nice view in GUI I use (Eclipse). I'm sure other GUIs have similar views somewhere. I'm also sure that plugin to turn old ones into syntax errors could be done in a day or two. That sound like much safer approach then runtime exception.

A day or two, really? That seems like an awfully long time requirement for what should be a simple change.

I'm sure it is a simple change. The hard part is to find out where exactly should you do that simple change and how exactly should you do it. If you do not have experience with related APIs, you will need a day for googling and reading. Eclipse framework is huge and not all its parts are immediately understandable.

Re: Auto-expiring TODO notes in Ruby

#42
post #28

Earlier quoted context omitted.

Given that we are talking about lazy/overworked on top of lazy/overworked here, why any confidence that this will be done 100% of the time? Putting time bombs in your code, regardless of a global configuration switch, is just asking for trouble.

I agree with you; my point was that while skrebbel spoke as if the point had never even been considered, it had in fact been considered. I have to admit to a certain amount of pet-peeve-like sensitivity to people commenting in ways that make it look like they only read the title.

I am guilty of this more often than I care to admit. Ooops.
Post reply on HN