background preloader

A lire

Facebook Twitter

Blog - String Calculator kata with Autofixture exercise 5. F# Design Patterns. Mieux comprendre les émotions. Les émotions: amies fidèles ou ennemies incapacitantes?

Mieux comprendre les émotions

Nos émotions nous parlent de nous La lecture émotionnelle au service du bien-êtreEmotions et pseudo-émotions Mieux comprendre les émotions La lecture émotionnelle au service des relations Collaboration, conflit et lecture émotionnelle De l’importance de la distinction entre stress et émotionsEfficacité professionnelle et émotions Remparts, coursives et échauguettes: les états de défense aux émotions Émotions et comportements paravents.

ASP.NET WebAPI: Getting Started with MVC4 and WebAPI. Download source code - 2.81 MB Introduction.

ASP.NET WebAPI: Getting Started with MVC4 and WebAPI

About - Nemerle programming language official site. Programming language for "special forces" of developers.

About - Nemerle programming language official site

Nemerle is a general-purpose, multi-paradigm programming language for the .Net platform. It is as easy to learn and use as C# or VB.NET but Nemerle is by far more powerful. One may start using it as an advanced C# and then, as learning goes on, employ a range of cool features enabling metaprogramming and functional programming. The metaprogramming is based on macros bearing some similarity to Lisp. General information. Clean Architecture. In the weeks since I started talking about the need to clean up our architecture, I’ve noticed a surprising resistance to the idea. Apparently the notion that it’s a good idea to hide the framework, UI, or database from the application code is not universally accepted. I first blogged about this topic here, I did some short video blogs here, here, and I did a whole cleancoders.com episode on the topic.

I’ve also done several keynotes on the topic, the slides for which are here, and a video recording of which is here. One somewhat dissenting view, written by The Frustrated Architect in his coding {the} architecture blog is here. He shows a picture, which I’ll repeat: The point he’s trying to make is that if the UI and Database are a much larger part of the system than the business rules, then the architecture of the system should be more oriented around those larger elements. NServiceBus - First Hands-On Experience - sfeldman.NET.

Tuesday, December 20, 2011 8:28 PM Sean Feldman NServiceBus - First Hands-On Experience I previously blogged on afterthoughts on NServiceBus course. Equipped with new powerful knowledge I have approached on of the TODO tasks on my plate – decouple email notification service from the main web application. First, the problem with the code that needed to be resolved. Gallery -EventSourcing Store. KsigDo. A Knockout, SignalR, ASP.net, MVVM, MVC and EF all mixed together into a multiuser real time sync To Do" example. The scope of technology used in this example was kind of breath taking, yet Anoop was able to bring it all together, exampling it to us as we followed along...

KsigDo. A Knockout, SignalR, ASP.net, MVVM, MVC and EF all mixed together into a multiuser real time sync To Do" example

KsigDo = Knockout + SignalR To-do app. Source code is here in Codeplex, keep it handy.Real time data syncing across user views *was* hard, especially in web applications. Most of the time, the second user needs to refresh the screen, to see the changes made by first user, or we need to implement some long polling that fetches the data and does the update manually.Now, with SignalR and Knockout, ASP.NET developers can take advantage of view model syncing across users, that’ll simplify these scenarios in a big way, with minimal code. This post discusses how to implement a real time to-do pad, which will sync data across users accessing the application. This means, users can make changes to their tasks (add/remove/update etc), and other users will see the changes instantly. Sustainable Test-Driven Development: Test Reflexology, Part 1 (first post) Download the Podcast How unit tests inform us about our design As proponents of Test-Driven Development, we constantly seek to identify and point out the various ways that the effort one puts into writing tests will be of value to the development team.

Sustainable Test-Driven Development: Test Reflexology, Part 1 (first post)

As with most highly-powerful techniques, TDD tends to deliver multiple values across the entire development effort.One example is this: We all agree that design is important, but most people would say that ‘good’ design is hard to define. It's like pornography and the Supreme Court [1]; we cannot quite define it but we know it when we see it. Liz Keogh's blog » Scrum and Kanban: both the same, only different. Tech·Ed North America 2011. Agile software development emphasizes that some increment of business value be delivered every iteration.

Tech·Ed North America 2011

How can this happen when your iterations are two weeks in length and you estimate it will take you two months just to design the database and the access layers? The answer is to think in slices,not layers. In this session,learn how to implement enough of each layer,including the database,to solve that iteration’s problems and provide value to the business. As we use good design principles,engineering practices,and tools,the architecture will emerge. Is it Time to Stop Estimating User Stories? Most new Agile teams transition from hours based estimates to relative estimation using story points, but do we even need estimates at all?

Is it Time to Stop Estimating User Stories?

Michael Dubakov suggests the following reasons why you should stop estimating user stories: CQRS, l’architecture aux deux visages (partie 1) Dans un article précédent, nous avons vu comment l’approche DDD, via la définition et l’utilisation d’un Ubiquitous Language et d’un véritable modèle du domaine, peut faciliter la communication entre acteurs projet, aider à l’écriture d’un code plus expressif (et donc plus maintenable), et capable d’adresser la complexité – et les changements – du métier.

Entity Framework doit-il faire peur aux DBA ? L'arrivée d'Entity Framework avec le Framework .Net permet aujourd'hui aux développeurs d'être encore plus productifs qu'auparavant. Ce gain de productivité intervient tout d'abord sur la construction de son modèle métier. En effet avec la version 4.0 d'Entity Framework Microsoft intègre un designer de modèle très puissant, entièrement intégré à Visual Studio. Mais les fonctionnalités d'un outil de mapping objet relationnel ne s'arrêtent pas là.

On parle notamment de SQL dynamique. Un outil ORM doit également permettre de s'abstraire de la source de données en fournissant un langage de requêtage. Partant de cette définition, il est légitime de se poser des questions sur les requêtes générées par ces outils. Dans cet article nous allons analyser quelques requêtes SQL générées par Entity Framework lorsque des relations d'héritages sont définies. Le modèle de base de données Le modèle de base de données ci-dessous représente le championnat de rugby simplifié.

Le modèle Entity Framework. Tito.Net: n layer web app with Entity Framework 4.1/4.2 - Things to consider. Public class CompanyRepository : BaseRepository public CompanyRepository() :base() public void Create(Company company) this.Context.Companies.Add(company);

Tito.Net: n layer web app with Entity Framework 4.1/4.2 - Things to consider