One Software Engineer's ramblings

Search This Blog

The WebSite is down - Video

on August 12, 2008

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Nothing to say. Just watch this.

Misc

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

ASP.NET Readers' Choice Award 2008 Products

The ASP.NET Readers' Choice voting is on. There are lots of companies and products listed. But I don't even know lots of them. I think many developers also don't. So I just decided to put all the listings together here. Just to make sure we'll be able at least to have a look on each one from a sinlge page. And this is a nice bookmark for me :) Add-in C# Refactory Xtreme Simplicity www.xtreme-simplicity.net Chant SpeechKit Chant www.chant.net CodeObject - Visual Studio .NET Madinina Software www.codeobject.com CodeRush for Visual Studio .NET Developer Express www.devexpress.com CodeSMART VS.NET AxTools www.axtools.com DeKlarit Artech www.deklarit.com DevPartner Studio Professional Edition Compuware www.compuware.com/products/devpartner/studio.htm IntraWeb Atozed Computer Software www.atozed.com/intraWeb/index.iwp ModelMaker Code Explorer for VS ModelMaker

Templating done easy - JavaScript HAML with Rails

HAML templating with no worries: native, precompiled HAML. Blazing fast and as easy to use as it can be. UPDATE: this functionality moved into ruby-haml-js gem, please use it instead. Recently I have been working on a Ruby gem that packs a set of common JavaScript libraries in one place so you can just reference those easily from Rails 3.1 app. But now I want to write a bit about a very handy tool that the gem includes. I needed to work on a Backbone app and, unfortunately, there was no very simple and easy way of using HAML markup for my client side templates. Main problems: I don't want to embed the template into the document. The Underscore.js templating is ok, but it is too verbose for me (as most of others). The haml-js is great, but I do not want to bother precompiling the templates. I do not want to think about templating as another layer or component. I want it to just work . Fortunately it was pretty easy solve these problems with the Sprockets

Versioning in an Event Sourced System - TLDR

This is an extremely short version of the excellent writing by Greg Young on versioning in Event Sourcing. It can also be applied in other systems as well. Most of what is written here - my own interpretation of the original book or sometimes quoted as-is and as such, all credit goes to Greg Young for this. I only added minor notes and only extended on the GDPR erasure a touch. I want to write it in a "bullet point" style for myself as a reminder and a short summary. Versioning techniques Basic Versioning A new version of an event must be convertible from the old version of the event. If not, it is not a new version of the event but rather a new event. Event.version (version on every event) InventoryItemDeactivated , InventoryItemDeactivated_v2 , InventoryItemDeactivated_v17 (class for every version) Thus, any InventoryItemDeactivated_vNNN can be converted to InventoryItemDeactivated_CURRENT and previous versions are never “visible” from app perspect

Powered by Blogger