SE News

Over decades we’ve used to adapt our habits, behavior and mindset to technology. We’ve improved our productivity by using tools and devices designed especially for the tasks we have to deal with regularly. But we’ve also constrained our abilities to the features of the very tools and devices we’ve become dependant on.

We’ve got used to a number of things. To traditional mouse-keyboard user interaction, to 2D windows-based user interface and to a rather unspectacular user’s workflow which enables one user interact with only one application at a time. For instance, while you’re browsing in your web browser you can’t scale your text and resize your window simultaneously — unless you are a keyboard-shortcut-master.

Good news: it can be different. Below we present some of the outstanding recent developments in the field of user experience design. Most techniques may seem very futuristic, but they are reality. And in fact, they are extremely impressive. Keep in mind: they can become ubiquitous over the next years.

Smashing Magazine

http://www.smashingmagazine.com/2007/11/26/monday-inspiration-user-experience-of-the-future/

Over the last few months (actually many months), I’ve been working on a book on Domain Specific Languages. I’m now at the point where I think it’s worth pushing out my work in progress. This page will keep you informed on where things are (and there’s an atom feed too). Rather than drop it all out in one huge dollop, I shall release what I have so far in bits over the next few weeks.

Martin Fowler

http://martinfowler.com/dslwip/

While the intention of both HTML V5 and XHTML V2 is to improve on the existing versions, the approaches the developers chose to make those improvements is very different. And with differing philosophies come distinct results. For the first time in many years, the direction of upcoming browser versions is uncertain. Uncover the bigger picture behind the details of these two standards.

Adriaan de Jonge

http://www.ibm.com/developerworks/library/x-html5xhtml2.html

No list of patterns, no matter how exhaustive, can cover every situation that comes up while programming. Eventually (or even frequently) you’ll come upon a situation where none of the cookie cutters fits. This need for general approaches to unique problems is one reason to study the theory of programming. Another is the sense of mastery that comes of knowing both what to do and why. Conversations about programming are also more interesting when they cover both theory and practice.

Kent Beck is the author of Implementation Patterns, from which this article is adapted.

http://www.ddj.com/architect/204201170

Ruby.NET version 0.9 has just been released. This is the first release of Ruby.NET under the new open source community model.

What is Ruby.NET? Ruby is a dynamic, open source programming language with a focus on simplicity and productivity. Ruby.NET is a compiler that translates Ruby source code into .NET intermediate code. This allows components implemented using the Ruby language to:
- Natively execute on the .NET platform.
- Be linked with third party components developed using other .NET languages such as C#.
- Utilize the extensive resources of the .NET platform including visual design and debugging tools, the security framework and an extensive collection of class libraries used, for example, to create Windows forms, web and database applications.

Ruby.NET is developed, owned and controlled by the Ruby and .NET open source communities.

http://rubydotnet.googlegroups.com/web/Home.htm

Elke markt is anders en in elke sector spelen andere afwegingen. Vandaar dat we kenners uit verschillende branches hebben gevraagd het krachtenveld te schetsen waarin architectuur zich begeeft. Veel aandacht gaat in dit thema dus uit naar de specifieke situatie, bijvoorbeeld bij banken, verzekeringen, de zorg en de groene sector. En daarnaast is er aandacht voor generieke onderwerpen zoals de opkomst van TOGAF en de ervaringen met drie jaar NK ICT Architectuur.

http://informatie.nl/artikelen/2007/11/

The Android platform is a software stack for mobile devices including an operating system, middleware and key applications. Developers can create applications for the platform using the Android SDK. Applications are written using the Java programming language and run on Dalvik, a custom virtual machine designed for embedded use which runs on top of a Linux kernel.

Next to a variety of documentation that will help you learn about Android and develop mobile applications for the platform, an early look of the Android SDK is also available. It includes sample projects with source code, development tools, an emulator, and libraries you’ll need to build an Android application.

http://code.google.com/android

Kevin Kelleher suggested an interesting way to compare programming languages: to describe each in terms of the problem it fixes. The surprising thing is how many, and how well, languages can be described this way.

Paul Graham

http://www.paulgraham.com/fix.html

The Carnegie Mellon Software Engineering Institute (SEI) proudly announced the release of CMMI for Acquisition (CMMI-ACQ), Version 1.2, a CMMI model designed for use in managing the supply chain by those who acquire, procure, or otherwise select and purchase products and services for business purposes. This model is a continuation of work to define best practices for organizations that acquire products and services or outsource development and support, which was work begun in a partnership between General Motors and the SEI.

CMMI-ACQ provides guidance to acquisition organizations for initiating and managing the acquisition of products and services that meet the needs of the customer. The model focuses on acquirer processes and integrates bodies of knowledge that are essential for successful acquisitions.

http://www.sei.cmu.edu/cmmi/models/ACQ-v12-announce.html

I am pleased to announce the release of Implementation Patterns. The book explains how to write code that communicates well with other humans. A chapter in the back explains an alternative style to use if you are writing frameworks instead of applications. The examples are all in Java, although the principles and most of the patterns apply to languages in the same family.

The book connects with XP’s values. Writing code that communicates with other people is a way of demonstrating that you value communication. Writing code that communicates is respectful to others. The book also connects with principles like maximizing the option value of software and writing code one can be proud of.

Kent Beck

http://www.informit.com/titles/0321413091

Why won’t developers make schedules? Two reasons. One: it’s a pain in the butt. Two: nobody believes the schedule is realistic. Why go to all the trouble of working on a schedule if it’s not going to be right?

Over the last year or so at Fog Creek we’ve been developing a system that’s so easy even our grouchiest developers are willing to go along with it. And as far as we can tell, it produces extremely reliable schedules. It’s called Evidence-Based Scheduling, or EBS. You gather evidence, mostly from historical timesheet data, that you feed back into your schedules. What you get is not just one ship date: you get a confidence distribution curve, showing the probability that you will ship on any given date.

http://www.joelonsoftware.com/items/2007/10/26.html