http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660I cannot agree with Adi more, putting exceptions into the code is dangerous enough. Using time-bombed exceptions is by far riskier. In the best case scenario you risk by loosing precious debugging time while in the worse case scenario I can think of, you risk by losing your client for "unstable" product. If you wish to remind yourself to fix a bug, use a bug tracking tool of any kind or simply use outlook tasks. If you still want internally in your code, use TODO remarks. Everything else is may result in unwanted results in production and deployment. http://blog2.tikotzki.com http://ayende.com/2066/hack-bombing#comment11http://ayende.com/2066/hack-bombing#comment11Sat, 17 Feb 2007 18:22:29 GMTHm, don't laugh, I can think of several reasons to do this, actually. http://ayende.com/2066/hack-bombing#comment10http://ayende.com/2066/hack-bombing#comment10Wed, 07 Feb 2007 17:57:15 GMTHow about the reverse.... Fix Bombing, where you add a fix but it only works after a specified date?! http://ayende.com/2066/hack-bombing#comment9http://ayende.com/2066/hack-bombing#comment9Wed, 07 Feb 2007 17:13:11 GMTThat requires quite a bit of work for something that should NOT happen regularly. Contrary to the impression I may have given, I do not tend to use this frequently. :-) http://ayende.com/2066/hack-bombing#comment8http://ayende.com/2066/hack-bombing#comment8Wed, 07 Feb 2007 07:30:59 GMTWhy not create a custom attribute, similar to the "Obsolete" one, but named "ThisIsAHack" which takes in a date created and a developer user name. That way, a very simple utility could be created to search an assembly for methods marked as such, and constantly list the ones needing work. This could even be placed into a CI environment, and email the folks who created the hacks on whatever periodic basis to ensure they don't forget. Ultimately, the attribute based mechanism keeps it from potentially hurting the end-user experience, yet allows for an automated approach for indicating and handling hacks. http://ayende.com/2066/hack-bombing#comment7http://ayende.com/2066/hack-bombing#comment7Tue, 06 Feb 2007 21:20:08 GMThttp://andersnoras.com/blogs/anoras/archive/2007/02/05/hack-bombing-template-for-resharper.aspx http://ayende.com/2066/hack-bombing#comment6http://ayende.com/2066/hack-bombing#comment6Tue, 06 Feb 2007 13:14:20 GMTAbsolutely nothing. I am not even trying to force a lazy developer from doing this, I am trying to ensure that it doesn't get lost in the noise. I should point out that pushing back the date every now and then is an act that you have to do consciously, so you are not losing this bug, you are deciding to defer it. http://ayende.com/2066/hack-bombing#comment5http://ayende.com/2066/hack-bombing#comment5Tue, 06 Feb 2007 10:29:14 GMTi like this idea. but what's to stop a lazy, degenerate developer like me just going into the code every few days and further pushing back the date? http://ayende.com/2066/hack-bombing#comment4http://ayende.com/2066/hack-bombing#comment4Tue, 06 Feb 2007 10:16:52 GMTDefending Hack Bombing http://ayende.com/2066/hack-bombing#comment3http://ayende.com/2066/hack-bombing#comment3Mon, 05 Feb 2007 22:55:13 GMTlol :) This one is quite funny. Anyway, I'm sure that the end-user will Not like that, if it make it to production. And before that, the developer will keep changing the date ;) http://ayende.com/2066/hack-bombing#comment2http://ayende.com/2066/hack-bombing#comment2Mon, 05 Feb 2007 18:27:03 GMTSounds horrible to me: http://dotmad.blogspot.com/2007/02/hack-bombing-is-horrible-idea.html http://ayende.com/2066/hack-bombing#comment1http://ayende.com/2066/hack-bombing#comment1Mon, 05 Feb 2007 12:43:32 GMT