I'm a hybrid developer, with experience ranging from 20 years of Photoshop work to Fortune 500 intranet application development. I've done more than my fair share of dabbling in Classic ASP, Flash, HTML, CSS, Javascript, and other languages during my career, and I'm always excited to try out new tools.

I developed methods for asynchronous page updates before XMLHttp was built into most browsers using a MacGuyver-esque collusion of Flash and Classic ASP, was writing dynamic Flash into browsers before the EOLAS debacle, and have a general disdain for blind allegiance to techniques with no regard to understanding of their benefits and consequences.

My general focus has been on front-end, UI and UX work, with a goal of making design decisions that are flexible and efficient. My mentor taught me the joys of Occam's Razor, a device I seek to employ in every possible situation.

When I'm not haunting the halls of programming, I'm probably either gaming, reading, drawing or making a fool of myself on a stage somewhere.

Likes: clean code, small, fast data transactions, a sense of craftsmanship, fun problems, learning and helping others learn at the same time

Dislikes: willful ignorance, overuse of <br/> tags, sloppy markup and lazy CSS, and did I mention I REALLY hate the abuse of the <br/> tag?

11 Actions

Dynamic Forms: Pattern or AntiPattern?Ah, ok, thanks for the explanation. That makes a lot of sense, considering how we had our form-builder system set up, too. (It's been a few years since I worked on it.)

Oct19

comment

Dynamic Forms: Pattern or AntiPattern?How would one architect such a system and keep separation of concerns in mind? There's been such a push in the past several years to distinctly separate data from presentation, that from that perspective, this would seem an "anti-pattern" but I also know from experience (we built something similar inside a corporate intranet that lasted for years, and was highly favored over corp-IT "solutions") that there is a place for such systems. I'm just curious what the best way to do something like this would be, keeping in the separation of data and view?

ASP.NET Webforms developers and web designers: how to interact?I was sort of assuming that any web developer worth their salt (even ones that only work with static HTML and CSS) would be using something like Firebug, but that's a good point to consider... coupling Firebug (or even Chrome's Developer window) with access to a test server, or running it locally and using Firebug on top of that, creates the closest thing to an "ideal" environment for getting a designer used to the adjustments they have to make for dynamic sites.