serbrech

"the "currentUser" model will emit an event to notify your application that it has changed"

That sounds like more than just wrapping knowledge to me.

Also, why do you absolutely want to fit everything into a framework? Or a pattern? Business logic goes into your domain models. Don't mix your business logic with your framework, that's about it...

Oh, you're comparing ST2 to VS without R#.

* Ctrl + D does copy lines

* you can place the cursor at multiple places since VS 2010

* Extensive search with R# (Search files, classes, methods... * using CamelCase, fuzzy..)

* sort shuffle lines, methods or any blocks with R#.

So ok, it's R#, and I agree that ST2 is amazing out of the box. (LOVE it for the Rails side project I work on) but adding R# (or standalone add-ins) to visual studio will get you there too.

Navigation within a .NET solution will always be better with VS + R# in my opinion.

The results feel actually fresh. It's removing the consumerism layer of bullshit that google serves us everyday. Also wondering if that has something to do with the "bubble" that google creates around us based on our search history and social network information.

Thanks for that.

I would argue that with how fast things are moving (and they are only getting faster), accumulating technical depts can lead you very quickly to lose customer (because you can't meet their expectation 'right now'). That can quickly lead to game over with the competition out there.

I posted a comment on the blog, but I might just as well begin the discussion here.

I'm working on a fun project with friends that we would love to see fly (We're applying for YC by Tuesday probably !). As a developers, I relate best to the technical kind of dept. It's interesting to read about other kinds of depts that you will have to pay back when you deal with a startup, pre-launch, and post-launch. Funnily, they all seem as important to keep track on.

Financial dept => game over. Personal dept => burn out => game over. Mental dept => burn out => game over. Technical dept => quality/productivity freefall => game over.

Let's map them the to the assets of a startup. Out of these four kinds of depts, 2 depend on the people and not the skills. Financial depends probably equally on skills and people. Technical dept being mostly skills related.

I think it illustrates well why having a great team synergy is so crucial to success.

What other depts can you think of?

Codiqa seems really awesome. I bookmark it for this week end : There is StartupWeekend in Oslo. I will advertise it there and I'm sure you will get many subscription from Norway this weekend.

I can't agree that a buggy and slow version of a product is an MVP. There are a lot of things that you can cut from a product to make it minimal. I don't believe quality is one of them. However, I also believe that user feedback cannot be the only factor to build something truly great.

A third of his time only? I guess it will be one third as good as the concurrent then?

Done, I like stars.

This is how I want all my tools. I had lots of ideas for better tools popping up in my head while watching this video. The kind of paradigms that he talks about are applicable to most of the creative processes.