Author: Thomas Kjeldahl Nilsson

I enjoy programming. Unfortunately, my skull is too small to hold a lot of stuff at the same time. Because of this, I have to keep my eyes on the target and I have to take small steps. If I don’t, I risk introducing bugs and unneccessary cruft. Perhaps you’re different, but this is how my head works.

A technique I sometimes use is pseudocode. I write my intended code out as simple sentences first, to see if it makes sense to me. If it doesn’t, I rewrite and edit more. When I’m happy with the story, I translate it into real code. Continue reading “Programmer Friday: I love pseudocode”→

If you join a team I’m working at, you’ll probably hear this from me on your first day:

“…we’ve done our best to write documentation, but I know that it could be way better. Could you help out? It would be awesome if we could improve the docs together while you’re getting to know the project: that’s the best time for it!”

Sometimes I talk to others who are considering going the same route. I now have a more or less standard list of advice that I send to them. I’m turning it into this blog post, so I can simply point here next time.

Sometimes you, the Android developer, will work with designers who have the time and knowledge to think of everything. They create complete, detailed designs for every screen and interaction. They cover both web, iOS and Android. They regularly use both Android and iOS themselves. They understand the strengths and conventions of each platform.

These projects are delightful. Unfortunately, all projects are not like this.