Group items tagged

" Don Syme overviews some of the basic features of functional languages, presenting why and when they are useful for parallel programming: simplicity, composability, immutability, lightweight reaction, translations, data parallelism, using F# examples but addressing the larger spectrum of functional languages including Haskell, Erlang, Clojure and JavaScript. "

" In this interview from the Erlang Factory event in London, three creators of modern functional languages -- Martin Odersky, creator of Scala; Joe Armstrong, a creator of Erlang; and Don Syme, creator of F# -- discuss the similarities and differences of their creations. They also discuss their languages' common thread -- that they integrate object-oriented features in functional languages. "

"I'm passionate about Domain Driven Design (DDD). Like many experienced object modellers, I was practicing this long before Eric Evans coined that specific term, though I have sinced learned some useful specific patterns from his book. To me, DDD is about two things: focussing on the business functionality rather than on the technical implementation; and focussing on building a good model of the business domain rather than just on the specific immediate requirements. Like many others, I perceived that the key to this was to model the domain as behaviourally-complete domain objects: to actively resist the tendency to separate business functionality from the persistent domain entities."

" The Xcoordination Application Space is a small framework to make writing asynchronous and distributed applications easier. It´s based on the concept of Space Based Computing which revolves around the notion of autonomous functional units communicating only indirectly and possibly in a stateful manner."

"There are quite of lot of things that I want to put into the framework, but it is functional in its current state. One of the goals for Nancy is to make it run on other environment and platforms, other than ASP.NET / IIS and there are spikes taking place to run it on Mono with FastCGI, making it possible to run on a bunch of other platforms. However, although this is the goal, the current source code does not provide any helpers to make that possible. Right now it only ships with an IHttpHandler that acts as an adaptor between ASP.NET / IIS and the Nancy engine."

"ORM users have grown accustomed to thinking in terms of .NET and LINQ, forgetting the specifics of particular databases, differences in their functionality and effectiveness of certain SQL-constructions. In this article, we shall briefly discuss some of the problems that the user may face in the process of developing an application for Entity Framework (EF), which is meant to interact with Oracle, MySQL, PostgreSQL or SQLite rather than Microsoft SQL Server. I hope this will be useful both for users who create an EF-application for these databases for the first time as well as for those who create an application that must support interaction with multiple databases, i.e., SQL Server and Oracle. As examples of implementing EF-providers for databases other than SQL Server, we shall use Devart ADO.NET providers."

"Pusher is a hosted API for quickly, easily and securely adding scalable realtime functionality via WebSockets to web and mobile apps."

"Agile development starts to build before the outcome is fully understood, ad­justs designs and plans as empirical knowledge is gained while building, trusts the judgment of those closest to the problem, and encourages continual col­laboration with the ultimate consumers. Architecture establishes a technol­ogy stack, creates design patterns, enhances quality attributes, and communicates to all interested parties. The combination of these two spaces is agile architecture - an approach that uses agile techniques to drive toward good architecture. Successful agile architecture requires an architect who understands agile de­velopment, interacts with the team at well-defined points, influences them using critical skills easily adapted from architectural experience with other approaches, and applies architectural functions that are independent of project methodology."

Sounds like this guy is confuse between enterprise architecture and solutions architecture. Or I am. :)

I think both those roles are evolving quite quickly at the moment. The classic Enterprise Architect is having to find new ways to plan, communicate and check quality as more and more teams explore Agile methodologies. The Solution Architect is suddenly playing a more obvious role as a result of the above. My feeling is, it is not so much about people, but about function. The same person could operate as a Solutions Architect most of the day, but then could get together in some kind of Architect's forum and play the role of an Enterprise Architect. That forum then wrestles through the Enterprise Architect issues and establishes the back-bone on which the Agile Development is done. That's what is probably happening, formally or informally in a lot of dev teams at the moment.