More of Joel Spolsky's smart understanding of "social software" as both social and software. Now StackOverflow evolves to become a smart online CV for recruiters.

SocialCalc comes out of beta.

Growth of a Wiki.

WARNING -- THIS BLOG IS STILL SHUTTING DOWN ... PREPARING FOR REBOOT

EditGrid is going free.

Nice. WikiIsNotWikipedia

And by the same token, Wikipedia is not wiki.

Funny advert just popped up on a Google search :

Work in IT within weeks
Become a Microsoft Engineer Earn £35K+ No Experience Necessary

WARNING - this blog is going dark ...

To return to a theme I started many years ago, I commented on this excellent article about why web-site development has got so damned hard. (And remember when we all thought of web-apps as lighter and simpler than desktop apps? What happened?)

Anyway, here's my comment.

I think the problem is less the multiplicity of programming languages, than our insistence that we should always be separating our languages in different places.

This goes against the basic tenets of cohesion and coupling. We cluster unrelated activities together because they happen to have the same syntactic sugar, while separating tightly-coupled activities because half of them happen on the client and the other on the server. Why the hell should this implementation detail have to be reflected in our architecture?

What I'd like, controversially, is to be able to mix-and-match the languages within the same source file, grouping together the python, javascript, html and sql that actually has to work together in one place. I have no trouble dropping into regular expressions or similar DSLs from inside my main code, why should dropping into a layout or query language be different?