Category: Tlon

It’s taken a few weeks to catch my breath after ReMIX Atlanta.  Most people have been asking if it was stressful to organize an event like this.  The truth is it was exhilarating.

Glen Gordon, Senior Developer Evangelist for Microsoft (pictured above imbibing the fruits of his labor after the event) has a good wrap-up here.  You can see the full set of ReMIX photos here.

In the past, ReMIX events have also been held in Boston and Chicago.  This year ReMIX Atlanta was the only ReMIX (an event based on MIX content and following MIX) in the US, so we have taken to calling it ReMIX USA.  Worldwide, there are also ReMIX events being hosted in Moscow, Paris, Seoul, Melbourne and London.

Our sponsors were amazing.  I can’t tell you how important an early response from sponsors means to the health of an event – as well as their willingness to set aside their typical invoice+60 policies in order to make money available. This early money is the life-blood of a conference – it establishes the scope of the event as well as morale for an event.

The vast majority of our sponsors contributed at the Platinum level – which means they gave us the maximum amount of money we were asking for.  Above and beyond that many also contributed software licenses, swag, and their time at the event.  Intellinet provided volunteers to check badges at the doors. Slalom flew out Nikki Chau to speak.  Microsoft flew out Brandon Watson to be our keynote speaker (Celia Dyer posted her video interview with Brandon for techdrawl here). DevExpress flew out Mehul Harry who is an amazing guy. 

Here is our full list of sponsors: Matrix, Veredus, Dunn Training, Agilitrain, EventVolt, Wintellect, Slalom, Intellinet, Magenic, Microsoft, DevExpress, Telerik, First Floor, Infragistics, Sagepath, AWDG, IxDA.

Special mention should be made of EventVolt.  This is the brainchild of Patrick Nickles, an entrepreneur new to the Atlanta area.  He contacted us just a few days before the event and offered to wire up power for the audience so they could plug in their laptops.   He has his own rig to do this.  He even had a rig for hooking us up with WIFI. His business idea is simply to help out with conferences by doing a lot of this technical plumbing work that hotels and other venues are not set up to do.  His initial email was basically – “I don’t expect anything back.  Just let me set up something cool for you and I’ll stay out of your way.”  Needless to say, this is an event organizer’s dream.

Thanks also go out to the speakers.  Many travelled to get to us – Brandon, Jonathan, Wally, Todd and Nikki.  All were amazing. 

Our full list of speakers is: Brandon Watson, Virginia Cagwin, Rob Cameron, Nikki Chau, James Chittenden, Dennis Estanislao, Sean Gerety, Jonathan Marbutt, Wallace McClure, Todd Miranda, Zachary Pousman, Corey Schuman and Shawn Wildermuth.  We had a scary moment when Steve Porter called us early on Saturday morning and turned out to be incredibly sick.  Corey Schuman was able to fill in at the last minute to do his talk on Windows Phone 7 and Expression Blend.

Thanks should also go out to the organizers.  For what it is worth, organizing an event ultimately comes down to bringing the right people together and letting then run with their ideas.  One assumes that by maintaining a high energy level and firing on all pistons, everyone will be at their best.  One then crosses one’s fingers and hopes that the right people have been brought in.  At ReMIX USA, this was the case.  Everyone pitched in when they saw a gap.  Everyone excelled at whatever became their responsibilities.

The main organizers of ReMIX were James Ashley, Dan Attis, Dennis Estanislao, Sean Gerety, Cliff Jacobson, Corey Schuman and David Steyer.

And then there are all the people who, like Patrick Nickles, simply pitched in and asked for no thanks.  I will do a great disservice at this point by not remembering everyone who helped out in this way.  However, at the risk of ignoring many contributors by naming the few, I’d like to thank Linda Gerety, Sergey Barskiy, Jessie and Jason Rainwater, Jay Cornelius and Farhan Rabbi.

I’ve been busy on multiple projects for the past month. It has kept me up on recent trends in enterprise architecture as well as hardening my hands in Silverlight development. The new year brought with it some problems in the Das Blog engine I use for this site, which prompted me to finally upgrade to the latest version. I am still trying to get various rather interesting comments approved (not sure what the problem is) and updating the theme. A quick observation, however. In December I was commuting daily with a colleague to an engagement downtown, and we both noted that although we were hearing dire warnings about the economy, neither of us actually knew anyone who had been laid off. Come January, everything has changed, and we both know many people either unemployed or facing unemployment. Worrying about how to keep my blog running smoothly is a pleasant distraction, by comparison, and so I will redouble my efforts in that direction.

I previously posted about how to use the Microsoft Ajax Library in order to provide Globalization script functionality without using the ScriptManager control.  Why would you want to do this?

One issue is that Microsoft is currently working on the ASP.NET MVC framework, which will provide a way of doing web applications that is more familiar to PHP and JSP programmers.  In other words, it doesn’t use the WebForms infrastructure that has underpinned Microsoft’s whole approach to web development for the past six years.  The original promise of WebForms was to abstract web development so it looks more like traditional Windows Forms development.  In order to accomplish this, the developers at Microsoft have worked hard to abstract the underlying web technology using windows components that render html and emit client script for the developer.

But now the tide is turning, and with WPF and XAML, Microsoft’s newest technology for building desktop applications, we are seeing a transition to the development metaphors that we have become accustomed to in web development.

ASP.NET AJAX was originally developed following the WebForms paradigm.  While other AJAX frameworks provided script libraries that you needed to manipulate using client script (typically javascript), Microsoft provided their framework wrapped in controls like the ScriptManager and the UpdatePanel.  Even the Ajax Control Toolkit, the Microsoft backed opensource project that extends ASP.NET AJAX with additional controls, follows this model.

But the MVC model doesn’t follow this model.  It follows the model followed by every other vendor of web technology.

So how do ASP.NET MVC and ASP.NET AJAX come together if they follow these radically different models?  Well … the Microsoft AJAX team also provides the underlying scripts for their framework in the Microsoft Ajax Library, which can be used in JSP, PHP, or even your traditional HTML page if you are willing to do the muscle work required to hook into them.  They can also, of course, be used with the MVC framework.

The Ajax Control Toolkit now also exposes its underlying script files for general use, allowing use to get all the great ACT functionality with WebForms or a ScriptManager.  The only problem is that learning to use the library without controls to manage our state and emit our code is difficult, and there is very little online help to get you started.

Stephen Walther is now helping people through this difficulty on his blog, and it is a wonderful thing.  He has already tackled the Popup Calendar and Autocomplete.  Expect to hear more from him in the near future.  I can’t wait to see what he does next.

h/t to Bertrand Leroy’s Tales From the Evil Empire for highlighting this.

There are many ways to make a career in IT, but perhaps the one most often dreamed of is starting your own business.  Lots of programmers get side-jobs that they hope will eventually lead to starting their own IT consulting business (this rarely works out, by the way).  Others wait for that great idea to come along, like a brilliant new Internet search algorithm, or a better way to do business reporting, or maybe even designing an original programming language.

I have heard that the thing that always kept Bill Gates up at night was the thought that some brilliant geeks would come up with the next great idea in their garage and put him out of business.

A colleague of mine has started his own somewhat atypical business building guitar stands in his own garage, and selling them on ebay.  While not the sort of stuff likely to unsettle either Steve Jobs or Bill Gates from his slumbers, my friend has done well enough with his home business that he has launched a web storefront, and is now selling his guitar stands at http://www.measuretwiceproducts.com.

He made a two-way stand for me with blazing pink and orange flames flying up the sides.  I love it, and it keeps me from stumbling over my Rock Band guitar after my kids have played a few riffs.  It ain’t the next great operating system, I know, and it isn’t even The Clapper, but if you find yourself wondering where to put your Guitar Hero or Rock Band guitar, I would highly recommend it.

Software engineering is a young discipline.  The process of developing software has been compared to building houses (software patterns), craft (pragmatic programming), gardening, manufacturing on an assembly line (ask your boss about this), and no doubt other metaphors will appear as the discipline’s teeth get lengthier.

Despite the relative youth of the profession, and despite the constantly changing nature of the game, there are nevertheless certain articles about the industry, the discipline, the phenomenon of software programming that have proven to be indispensable, if only because they continue to reveal truisms about ourselves, as coders, that we continue to forget.  The simplest lesson is that software projects are always harder than we think they are going to be.

What Mary Knows is a philosophical essay by Frank Jackson which poses a thought experiment in order to explore what we mean when we speak of ‘knowing’.  Mary is an imaginary person locked in a darkened room and deprived of all sense impressions.  At the same time, she is fed all the knowledge she needs in order to develop a scientifically descriptive and scientifically full picture of the world.  Eventually she is released from her room and encounters something she has never comes across before, despite the completeness of her education.  She comes across the color yellow, and finds that she doesn’t ‘know’ what it is.

Software developers often suffer from a similar condition.  While we feel fully knowledgeable about the specific things, and the specific trends, we are currently working on in our cubicles, we tend to lose sight of the big picture. 

To this end, I’ve been trying to build up a library of things every developer should know.  The only condition on this canon is that the articles must be publicly accessible for, to my thinking, if an article is hard to get or is something that someone else is making money off (which they certainly deserve to — I don’t have a particular beef with monetizing denken) then it is not something that everyone needs to know.  That’s a bit of sophistry, of course, but it serves my purposes.  Any suggestions for extending this list (quite short at the moment) are most welcome.

Here’s the beginnings of the canon:

1. Alan Turing’s 1950 essay, Computing Machinery and Intelligence — software programming constantly runs into questions about artificial intelligence, if only because, in developing business solutions, we often are trying to translate human activities into software enforced rules.  This article is the original source for many of these considerations.

2. Vernor Vinge’s influential 1993 article on The Singularity — if the Turing paper tells us where software developers come from, Vinge’s paper tells us where we may be headed.  It combines two notions: first Moore’s Law, which has become a metaphor for the exponential rate at which technology improves, and second the observation that we are not in control of this progress.

3. Nicholas Carr’s IT Doesn’t Matter is rather hard to find, but is important in that it questions the primacy of software development, and proposes that we, as software developers, may all be working ourselves out of a job.

4. Fred Brooks’s No Silver Bullet tells us why software development on reasonably large projects is so, very hard.  More importantly, he reveals some of the preconceptions that often make it harder than it needs to be, and dooms us to frequent failures.  Brooks’s essay The Mythical Man-Month is also essential reading, but I cannot find an Internet source for it, alas (fortunately, the title, for the most part, tells you what you need to know).

5. In the same vein as Fred Brooks’s skeptical essays about the nature of software development is Michael Oakeshott’s Rationality in Politics.  Though not really about software programming, it does examine some of the preconceptions about rationality that underpin how we view software programming, and provides some intellectual underpinnings for Fred Brooks’s work, should you like to explore it.

The Oakeshott also makes a good segue for discussing some free podcasts worth listening to.  Since I spend an inordinate amount of time in Atlanta traffic, I am always on the lookout for these sorts of things.  And like the software canon above, I like my listening to be free.

First, you might enjoy Learn Out Loud’s philosophy podcast.  By subscribing to this podcast through iTunes, you have the opportunity to listen to dramatic readings of the major philosophers, including Plato, Aristotle, Hobbes, Hume and Wittgenstein.  This may seem, at first, like a recipe for falling asleep at the wheel, but they are actually quite engaging, thanks largely to the fact that the reader used in most of these recordings is a dead-ringer for Captain Picard from TNG.

(For some reason, I get many hits for Kierkegaard’s essay The Crowd is Untruth on my blog.  For those readers, in particular, I’d like to point out that Learn Out Loud has a 3.6 MB download of K’s essay.)

You might get a kick out of Open Court Publishing’s podcast of excerpts from their Popular Philosophy series.  Subscribe today, and you will have the opportunity to hear:

• Why Make a Matrix? And Why You Might Be in One
• Enjoying the So-Called Iced Cream: Mr. Burns, Satan, and Happiness 
• Seven Lessons in Philosophy You Already Learned Playing Texas Hold’Em
• When They Aren’t Eating Us, They Bring Us Together: Zombies and the American Social Contract
• Tony Soprano as Ethical Manager
• Monty Python and David Hume on Religion
• … and many more …

 

Giornale Nuovo, a blog written anonymously by someone calling himself Misteraitch, is coming to an end after five years.  Without any exaggeration, it has been one of the best things available on the net over that time, and Misteraitch’s  efforts will be sorely missed.

Giornale Nuovo falls into that strange category of erudite blogs in which the author takes a personal passion and draws one into it.  M.’s passion happens to be rare books, and in particular rare illustrated books.  Based in Italy, and later somewhere in Scandinavia, he would haunt the odd bookstores of Europe tracking down rumors of quaint and curious volumes of forgotten lore — so to speak — and once acquired, he would digest them through his scanner and publish them on his blog, pointing out the peculiarities of his acquisitions.  He is also an art lover, and was quite good at finding painters, sculptors, and installation artists that you had never heard of before but whom, after reading the blog, you would never forget.

And now, M. is hanging up his spurs.  Fortunately, he will be leaving the archives of his blog up for a while, giving readers a chance to catch up on his industriousness somewhat belatedly — I almost said posthumously.  M.’s main complaint, I take it, is exhaustion.  It takes much out of a person to continuously publish writing of this caliber, and no doubt M. was concerned that his output would eventually flag.  Going through the archives, however, I see little sign of this.  All the entries are consistently good.  Take, for instance, his contribution to our common knowledge with Curiosities of Literature, or his frequent entries on Emblem Books, or this one about Anthropomorphic Alphabets.  These I selected randomly, just to give you a taste of what I have been enjoying for many months.

M. is also rightly famous for his giveaways.  Every so often, he would decide that his bookshelves were too full, or his CD collection too disorganized, and he would simply list the overflow of books or music on his site, with charming descriptions, and then mail them, gratis, to the first person who showed any interest (one year I received Rachmaninov’s Vespers from him). 

Such generosity was not uncommon with M., and his entire site is, in fact, a five year act of generosity in which he artfully lay out his personal tastes for the world to view.  If you have never visited Giornale Nuovo before, then I heartily recommend that you take this opportunity to browse through its archives while it is still available.  It is a monument of the Internet not to be missed, and a rare example of how technology, rather than twisting the human soul, can actually make it soar.

dasBlog is the engine I have been using over the past year on my web site.  Besides its low cost (free as beer), and a tendency to be a reliable blog engine, I also like it because it uses XML files rather than a database to persist information.  The release version has been running on the .NET 1.1 Framework for quite a long while, and despite a teaser tag on their home site insisting that the new 2.0 version would be released in a matter of weeks, dasBlog 2.0 has actually taken a much, much, longer time to come out.

But now the wait is over, and I plan to upgrade to the newest version sometime later tonight.  As sometimes happens, this may entail the complete collapse of the site and the loss of all prior blog posts — but I’m keeping my fingers crossed and maintaining a positive attitude about it, for such is the price of progress.

Supposing that I am successful in migrating to the newest version, I don’t plan to post a review of the qualities of the new platform since, in this case, the medium is very much the message.

I was busy writing away in a notebook last night when I suddenly realized that I was sleeping.  In the dream, I had been working on a commentary on Montaigne’s essay Of Cannibals.  The problem with discussing dreams, of course, is that it ofen leads one into an embarrassing consideration of one’s own inner life which tends to be self-stroking and not particularly revealing — or rather, it reveals some self-absorbed aspects of one’s own personality even as one is sure that it is revealing some great inner-truth, like John Marcher’s beast in the jungle.  Or even worse, it is like taking one of those IQ tests that occassionally pop-up in one’s browser and determining from it that one is quite intelligent.

When I woke up in the morning, there was no commentary written out at my bedside, or even prepared in my head.  I don’t even remember what I was trying to say about Of Cannibals.  This contrasts starkly with the experience of sleep coding, which occassionally overcomes software developers who have been working too hard on a particular problem, and in some circles is even considered to be a mark of particularly virtuous coding.

I am convinced, as many programmers are, that sleep coding really works — that is, that in sleep, programmers actually solve problems from their waking hours.  I have often spent hours on a particularly insidious problem only to find, after a good night’s sleep, that I am able to quickly fix the problem the next morning.  And it seems to be something different from simply taking a break.  Walking away from a problem for a few hours, while it can be helpful in reducing stress, has never had the revelatory effect that sleeping has had.  I’ve even come to the point that when I consider a problem to be particularly difficult, instead of trying to solve the problem right away, I plan on learning as much as I can about it in order to hand it over to my dream-coder to solve in the night.  I think of this as an occult offshoring.

It is quite possible, of course, that the experience of dreaming code and the phenomenon of having code solved in one’s sleep are two entirely different things.  The second can be true even if the first is essentially meaningless, a phantom caused by neurons misfiring in our sleep.  And this is, in some cases, the solution to the mind-body problem.  The theory goes that when awake, we are merely observers of a mechanistic process with epiphenomenal experiences that do not actually affect what is going on in the world.  We are merely passive observers, even though we think we are actually participating and making decisions — though this implies a rather inelegant duplication of entities in the world.  Why should it be that I can code in my sleep, and also observe myself coding in my sleep through my dreams, but these two things are not the same thing?

And also, is this something that only happens for computer programmers?  Is it the case that our bodies can perform high cognitive functions without us, but only for certain types of tasks?  I don’t recall ever waking up in college with an essay fully formed in my mind.  Then again, we are told that Coleridge woke up from a dream with Kubla Kahn fully formed in his mind, and only after being interrupted by a visitor and taking a break from it, did he lose it again.