Browsed by
Author: Patrick

My personal wrap-up of the NDC 2012

My personal wrap-up of the NDC 2012

Comments 1 comment

I was at the Norwegian Developer Conference (NDC) 2012 in Oslo. It is one of the best conferences I know in Europe. One reason is, that a lot of alpha-geeks are speaking there. There were during three days 8 parallels tracks, so you have to manage your program. My program looked like this: Wednesday, 6.6.2012 Keynote, Aral Balkan Decisions, Decisions, Dan North Professional Software Development, Robert C. Martin (Uncle Bob) Agile Estimating, Mike Cohn Modeling Distributed Systems with NServiceBus Studio,…

Read More Read More

Quality isn’t a tool–You can’t install it!

Quality isn’t a tool–You can’t install it!

Comments 13 comments

Did you ask yourself why a team in an organization produces very good software quality and another team in the same organization just struggles to get things done and those things are in really bad quality? Interesting is also that for both teams exists the same rules (methologies, procedures, tools, frameworks, etc.). But why could and does this happen? Some people – mostly managers or vendors – try to distill quality to a recipe. Vendors could sell it expensively (with…

Read More Read More

Are stale data evil?

Are stale data evil?

Comments 1 comment

When you’re a software engineer who produces software for enterprises like banks or assurances, then it is normal you have huge databases (several gigabytes). Such systems have an operative application where users do the daily business of the company and there are more informative parts (or strategic parts) of the systems which the management uses. At a first glance, there isn’t a problem with those two views, but as you probably know, those companies have for the second part for…

Read More Read More

Anti-Pattern ‘Validation by Execute ‘n’ Rollback’

Anti-Pattern ‘Validation by Execute ‘n’ Rollback’

Comments 1 comment

Recently in some reviews I saw an anti-pattern. First you have to know, in the code, there was a validation of the data before it was stored in the database. So far so good. But when I looked at the validation code, I saw the following: public void Validate() { DoProcess(true); } And the persist logic (with some business logic) looked like this: public void Process() { DoProcess(false); } So, I asked myself, what the Boolean means. Well, here is…

Read More Read More

Who should make decisions about technologies?

Who should make decisions about technologies?

Comments 0 Comment

One of the biggest problems of software engineering companies in Switzerland is currently to get new software developers. To get new employees there are several points as for example salary, environment, career possibilities and technologies. The last point looks easy but in reality it isn’t that easy. Why are essential technology decisions (like languages, frameworks, application servers or big libraries) not only made by developers? Why does the management mostly make those decisions? In this blog post I try to…

Read More Read More