- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- 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
Brilliant! I award you the Laugh Out Loud prize!
Admin
Maybe make them submit resume first and fill the quiz next?
Admin
I'm sure we could all learn from your code and be humbled by it. This is especially the case with those 12 tier architectures (with and without facades, proxies, adapters and factories). OK, that's a little harsh.
I apologize.
I'm too old to be all smoke and fire anymore.
Don't spank MVC too much. Where would .NET be without it? :)
-Tim the Enchanter
Admin
256 comments? Let's see if TDWTF can handle another byte! (Or maybe it was signed, in which case I already lost :/)
Admin
Too good to be true:
Tenacity, determination, ingenuity....
Man, that's exactly the kind of guy I'd hire! And, finally, let's not forget: he scored 92!
In other words, if you want someone who you know will keep at it until the job gets done, no matter what, and who will almost certainly succeed... that was your guy!
Admin
I don't know if these are disadvantages or simple issues, and it would depend on framework, in this case its PureMvc adapted for dot Net with some modifications:
Original PureMvc for dot Net used refection to call notification handlers, which fucked up the stack trace.
With the observer pattern, there is always a concern lurking in what observer got called first. You have to design so this never becomes an issue.
When using an event system, whether Mvc or dot net, you cannot trace an execution path in your static code.
Recursion. Fences have to be put up at times when you have events that do things that end up triggering the same event again.
Wiring. Every view mediator has to be wired up to its controls and respective events. Using reflection some of this wiring can be automated.
Since Mvc is designed to decouple things, it is often difficult to detect when something that should be hooked up, hasn't been. It fails silently.
I wish dot Net had a language enhancement called 'transient', so you could create an instance of a transient class, but if that class was on an exclude list the runtime would ignore or refactor all statements using that class.
public transient class C{}
main(){
var c=new C();// if c is excluded do nothing
c.Something();// ignored if excluded
int i=1; fn(c, i);// calls fn(int) if c is excluded and fn(int) exists, else do nothing }
So this transient property would be used so you could unplug dependencies for development reasons. Accomplishing decoupling in dev.
Admin
5 years later...
Yeah, VB isn't that great to begin with. But there IS a proper use of "On Error Resume Next". Hint: It should NOT be used at the beginning of your code to "ignore" all Errors!
http://www.cpearson.com/excel/errorhandling.htm
Admin
Nice post. I was checking continuously this blog and I'm impressed! Extremely helpful info particularly the last part :) I care for such info a lot. I was looking for this certain info for a long time. Thank you and best of luck. save refuges