June 2009 - Posts
This makes me laugh, in light of tech pundits who overstate the importance of Twitter.
I read a good post today about the silly wars that go on in versus debates, in this case the arguments about whether to use Webforms or MVC for ASP.NET.
I kind of saw this storm coming when people started describing
themselves as part of the alternative "movement" in the ASP.NET
The truth is that MVC gets me really excited, for a
thousand different reasons. My win comes from the fact that I feel like
I'm no longer fighting the statelessness of the Web by conforming to a
framework that simulates statefullness. Maybe I never really realized I
was doing that. But the nice thing about MVC is that it has forced me
to break down what I'm doing into simple actions. There are two
benefits developing that I had not previously considered.
first is that the stripped down nature of the MVC pattern causes you to
back off if you're someone who does UI development. It can be argued
that many of the apps out there now that get all of the press and
attention are ridiculously simple and easy to use because they don't
try to do a lot, and, by no coincidence, happen to be developed on
another MVC framework, Rails. Whether it be Twitter or my wife's
favorite site, Ravelry, there is a simple style that seems
representative of sites developed using this design pattern.
second benefit is that adhering to a strict seperation of concerns,
whether it be for reasons of testability or the desire to decouple your
pieces parts as much as possible (or because "they" said so), makes
your code infinitely easier to maintain.
That said, when bouncing
back to a Webforms project, I'm amazed at just how much cleaner
everything I write is in terms of keeping the moving parts minimally
coupled to each other. It's not that I had 10,000-line code-behind
files before, but my mindset has changed enough since spending time in
MVC that I'm a better developer now when using Webforms.
all of the crazy zealots go on and on about how awesome MVC is, I'm not
writing that image gallery control for the hundredth time, because I
did it once years ago. The simple content management apps, handlers and
diagnostic pieces are all there still for me to use, and now I'm wiring
it all together in a much cleaner way.
I love MVC. I mean I really dig it. I can't wait to get some of my projects based on it out into the open (other than my personal blog,
anyway). But the truth is that the value already built into years of
ASP.NET Webforms is not trivialized or bested by the new framework.
Instead, there's a great compliment in place now where I can use which
ever gets me to market the fastest. At the end of the day, rewriting
things for the sake of science doesn't get me paid. Shipping stuff is
what puts food on the table. Now my toolbox is a lot bigger.
Obviously Silverlight runs on OS X. That much we know, since developers like me use it for non-development tasks instead of Windows. How difficult would it be to adapt it to stand-alone apps on the iPhone? Even if it had to include the runtime and base library (at a few megabytes), it would still be pretty cool, and we wouldn't have to use Xcode (which I'm not impressed with).
I just read the JJ Abrams essay in the previous issue of Wired.
This essay really struck home about where we get joy out of life, and
how we seem so eager to overlook it. This quote sums it up for me:
"True understanding (or skill or effort) has become
bothersome—an unnecessary headache that impedes our ability to get on
with our lives (and most likely skip to something else). Earning the
endgame seems so yesterday, especially when we can know whatever we
need to know whenever we need to know it."
That is true on more levels than I can describe. While the Internet
has done so much to facilitate communication and bring people together,
it has also managed to trivilaize knowledge and the process of
I liken this to a suggestion that a friend made to me last year when
I was in the midst of writing code for one of my sites. He asked, "Why
don't you just use all of the free stuff out there and stictch it
together to make a site?" Aside from issues of integration, I asked
what I would get out of that as a developer. The "skill and effort" is
important to me. Deeper understanding is important to me. It's the same
reason someone may build a table instead of buying one from Ikea.
Indeed, sometimes the end product is less interesting than the journey
required to get there.
After a great deal of soul searching (and a PDF draft of chapter 1 posted), I've decided that I'm not going to follow through on this book. I've got a total of four chapters, two of which are at 75%, but there are a number of reasons that I've decided to focus my attention elsewhere.
The biggest issue I have right now is that I don't see an obvious personal benefit to following through at this time, especially when I compare it to other projects. Since I'm essentially "self-employed," and foresee that as a lasting condition for some time given the sad job market, I really want to pour more energy into things that look and smell like income. Self-publishing, for all of the benefits, doesn't pay up front the way an advance does through a mainstream publisher and, you know, I like to eat and do summer stuff.
I've also had a lot of fun in the last two months tweaking and analyzing my existing Web sites. CoasterBuzz is doing very well, with page views up 20%. I've been shooting video and photographing rides for the site too, something I love to do but kind of let go of over the years. I'm really getting back in touch with the stuff that motivated me to get into software in the first place.
Perhaps most important, I'm getting back into some basic level of fitness. I'm married again, and I have to look after myself for someone else's benefit as well. The nasty high stress crappy job I lost really had me pushing aside just common sense eating and exercise, and I want to make sure I'm balancing all of that out.
The content I've written so far will not go away, and it will see the light of day one way or another. Perhaps it'll appear as a finished book for a future release, or as a series of long Web pieces. I haven't decided. The simple blogging app used as the example code will be released as well, probably sooner than later (in part because I'm hell bent on proving that 95% of what you want to do can be achieved by 10% of the average "best practice" or "sample" app).
This wasn't an easy decision, especially given all of the wonderful feedback I've received so far (and even some outright hate mail). At the end of the day, I need to chase what gets me out of bed, and unfortunately, this just wasn't it.
I moved my personal blog to a more appropriate domain name, JeffPutz.com. Hooray for vanity names! I'll continue to keep technical and programming junk here. It seemed appropriate though to have a central location for me stuff, including my resume and various media samples, so this is it.
This is the first MVC app that I've put into production, oddly enough. Well, technically it is, though I've supervised the development of MVC apps elsewhere. This little app is what I've been writing my next book around, and it is purposefully as simple as possible. Most of the sample apps I've tried to disect are entirely too complex, and I think that's a barrier for a lot of people. I'll post the code after I've put it through the paces a bit.
The other day, me and Diana were talking
about the concept of "supported" browsers, and how big corporations
often restrict their online applications for use only with certain
browsers. This is a throwback to the days when you needed ActiveX or
certain IE-only features, and is rooted in old school corporate IT
But there are still a lot of financial institutions in
particular that keep telling you what browser to use, and that's just
stupid. I was looking at the stats for my sites today, and it shows
that 15% of visitors are Mac users, and only about 55% are IE users.
Even the iPhone is closing in on 1%, which is crazy.
world we live in. If you blow off 15% of your audience, can you afford
that? Imagine if Amazon did this. Their holiday quarter did $225
million in profit. Do you think they'd be OK with leaving $33 million
on the table?
I ran into another support issue today, when trying
to view the video clips for the Halo prequel and the body control stuff
for Xbox. I'd love to watch them, but they use some goofy stream that's
presumably Windows Media based and I can't watch them on the Mac.
Technologist apologists seem hell bent on declaring that this kind of
thing is OK, but especially for marketing intent, why would you exclude
any percentage of your audience?
I'm not suggesting we all need
to test for IE6 at this point, but come on man... with the standards
and frameworks we have, it isn't that hard to reach 99% of your