Design - Morten Nielsen

Morten Nielsen

Sign in Subscribe

Design

A collection of 16 posts

Making it easy to work with performance

We’ve been working with performance in our REST API a while back. We’ve been considering different options for measuring our API in production, but we had an idea to use the design of the API itself to handle the measuring. Part of the inspiration came from the Changlelog

Bananas!

During Android Only [http://swdc-central.com/androidonly/index.html] Erik Hellman from Sony Ericsson explained how they create their Android Phones. During his talk he mentioned that they put all phones through a monkey test. Where a phone has to sit for days with random input on the phone, without

Refactoring of logging rules

I’ve been working on a logging system for RemoteX Applications, the system is going Live any day now. (In fact since this post will be scheduled it might already have). So I started out doing the code as straight forward as possible, but it quickly started to nest if-statements

Working at the right level of abstraction

At RemoteX [http://www.remotex.com] we have been a bit unhappy with the code produced to create our REST-service using WCF. The problem is that you have these contracts that you specify. These contracts then build up a web-service end-point using the WebGet and similar attributes, to create a

Inheritance of features

Given my recent combining [https://www.morten.software/?p=1015] of Tracks [http://www.getontracks.org/] and Shuffle [http://code.google.com/p/android-shuffle/]. An interesting thing happened. Something that happens when you combine two products so that they inherit features from each other. On Shuffle’s issue list there

The guessing user interface

My girlfriend [http://natooktesting.wordpress.com/] has downloaded a solitaire application to her HTC Tattoo. While solitaire isn’t anything revolutionary it has an interface feature which got me thinking. Se what the interface does is move those cards that it is sure that the next step is to move.

Rethinking design desicions

I read a blog post at Three Rivers Institute [http://www.threeriversinstitute.org/blog/?p=398] that lead me to the following presentation [http://onstartups.com/tabid/3339/bid/11042/Dharmesh-On-Startup-Marketing-Video-From-MIT-Startup-Bootcamp.aspx?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+onstartups+(OnStartups)&utm_content=Google+Feedfetcher]

The importance of teaching

I have a good friend whom after university focused on first communication and then management. But now he has turned to development. We’ve been having a few discussion over the past few days about SOLID and REST and Grails. IoC containers and what not. He hasn’t seen these

Refactoring how to open views

We had a problem in RemoteX applications, not a big one, but an old structure that had to be refactored. Our open method only accepted URIs as arguments. This forced most of our commands that create new entities, to first save an empty new version of the entity to make

Performance monitoring of a deployed application

I had an idea today while working with a performance issue on the REST-service of RemoteX Applications. In theory having a performance counter with the average execution time of SQL-queries over time. Will allow monitoring of system wide average cost for queries in the system. That means that overtime its

Grails: Ajax Login using Basic Auth

So I have my Grails environment setup. The point is to build a REST-service that will work as a back end to a highly dynamic JavaScript page. I chose Grails, since it builds on Hibernate and Spring. Two frameworks Id like to examine for the purpose of seeing the differences

Working with a domain model

We just took a new turn on the work with our Domain Model in RemoteX Applications. In recent months, mostly due to the increased number of customers using the system. There had been some innovative ways in using the product. Some for which we hadnt intended the product to be

Every time you downcast a kitten breaks a rib

This is a snippet taken from our design guidelines document. > Most code doesn’t require casting. Avoid casting, especially if you cast to a more specialized class.

Use extension methods with care

.Net 3.5 introduced the extension methods; they can be a nice way to extend classes we have no control over. They can wrap common usages of objects; even implement methods on interfaces to assist the common responsibility of the usage of that interface. However, extension methods are basically just

Design consideration when using Extention methods

Extension methods are a nice way to warp up code that you often execute on different classes. However do not forget to consider the test implications of the Extension methods you are creating. A simple mutating extension method is easy enough. But if you have an extension method that does

The cost of an conditional flow in a user story

During this sprint in at my work, some minor touch up stories were added to the sprint. These stories however we’re thought out, at least not to the level that they were ready to be implemented. Ill try to describe a particular problem of one of them. The problem