When I first arrived in Indonesia I didn’t think nor knew much about the difference in our cultures. This quite understandable, although in hindsight I should have read up on it a little bit more. Now, as I know more and more, I also get more and more interested and confused about some very basic things in the society. To not come out as very prejudiced there’s some of disclaimers to be made and I’ll do that throughout the post, but here are few to get started: These are merely my observations after 15 months in the country. I’ve been working with quite a lot of people (met maybe ≈500) and in a few different companies. It’s very easy to jump to a conclusion that some behavior (mine, your or theirs) is stupid or wrong. I don’t want to do that, so in everything I write here I will try...

I wrote a little application called page-logger for purely selfish and lazy reasons. It was fast, quite fun, I learned a lot and apparently I could make MONEY by using it. Which I didn’t thought of when I wrote it. In this post I’ll take you through some code, point to some things that I learned and finally some thoughts about learning from your data. I hope you like it. Why I built page-logger I’ve been using Blogger for a very long time. From when I started to blog (2006… oh my) until early last year… OMG - I’ve been doing this for 9 years. Oh, sorry… got lost in sentimentality there. Ok - last year I switched to Jekyll hosted on GitHub. That’s worked out very well. However - there’s a nice feature of Blogger that I was missing. There’s a lightweight Google Analytics built into Blogger. It’s great...

The blog post I wrote yesterday was from my experience at the time. I even ended the post with a call out for better ways. And sure enough, twitter to the rescue: @marcusoftnet Marcus.. I just use the Coffee command that you installed earlier? No need to compile at all..— Erwin van der Koogh (@evanderkoogh) March 4, 2015 As a side, this why I hang out on twitter. There are brilliant people there that will push you towards ever better. Thanks Erwin for this. So… what does that mean for my post yesterday… Let’s find out: First of all - nothing I wrote will cause you problems but it’s a bit cumbersome and maybe not the CoffeeScript-way… I think. What worked All the things I wrote under the “Initialize project and more” and “Run tests” headings is a ok way to get up and running with CoffeeScript on Node. Doing...

For some reason I’m from time to time drawn to different languages that compiles to JavaScript. And then I’m drawn away again. Especially nowadays with ES6 coming up many ideas and needs for CoffeeScript or TypeScript goes away. So the other day I found myself thinking again: Hey - CoffeeScript. That's not such a bad idea. Maybe I should try to write some. CoffeeScript and I have a dormant but warm relationship because this little language was the one that helped me understand not only JavaScript but also got grips of functional programming. I thought I’d write a simple little kata in Node to fresh up my CoffeeScript-fu. How hard could it be? Well… there’s quite a lot of setup and idiosyncrasies that you need to be aware of. This post tries to summary what I learned as I got my environment up and running. Specifically; initialization, run tests, write...

In Indonesia there’s an interesting development going on right now in health care. A nationwide health insurance is being rolled out. For everyone. Until now health care has been paid for privately or via private health insurances, but with the advent of BPJS (that it’s called) everyone can now afford to go to the hospital… or at least there’s fixed tariffs. Before we continue, imagine the effort to roll this out in the world 5th biggest population… 250-270 million people. Most of which is very poor. I think this is such a great thing and I applaud the Indonesian government for doing it. However… I work for hospitals in Indonesia. On the “other” side of things. For us this is also an opportunity since this will bring more patients to our hospitals and we get to serve those in need. But there’s another side of the story that have very...

Once you’ve coded and tested a Node application we are anxious to deploy it and put in front of real users. I’ve blogged before on how you can do that very easily and fast with Heroku. But one thing that trips me up a lot is the configuration and especially things that I want to vary per environment, like connection strings to databases or user names. Hey - some of those things I don’t even wanna check into source control at all. They might be secrets that I don’t want anyone else to get hold off. In this post I’ll show you a little function / object that I’ve found plenty use of and that I now include in almost every project I deploy. I’ll finish up with a little discussion on how to handle secrets too. I don’t know really where I picked this construct up, the first time,...

I reflected a little bit about the great teams I’ve had the honor to be part of. It’s just a few out of all the teams that I’ve been part of that I would call great. But they all shared some common traits. My first ever scrum team was a great team, that I still think back on fondly. Gothenburg Brass Band was an orchestra that I had the opportunity to be part of for almost 2 years - total awesomeness. My “current” (since I don’t play with them now) band Vasa Band is another group that I hail as a great team. The prayer group we had 2006-2010 in our home was an amazing group too. Looking back I remember these things that was common about them, in the very particular order that I remember the traits…: Sat together The great teams I’ve been part of have all been...

A few days back I said something to my client that apparently many people on twitter found interesting. “How is the project going?” “We have a lot of things going on!” “Ahhh… so you’re slowing down the progress?” #stopStartingStartFinishing— Marcus Hammarberg (@marcusoftnet) January 29, 2015 My client, the hospital that I’ve written about many times before, has a big project ahead. We are going to be accredited for quality in all our processes. So… there’s a lot of documentation, implementation and training to be done. Nobody really knows how much. We think, for hearing other projects, that it’s about 6 months and made that our goal. But we haven’t got a clue how much work it is left for us. The work is divided into 4 areas that we’ve formed teams around. Each of this area has a number of targets that they need to consider and help the hospital to meet. So...

Imagine that you want to learn a new technology or tool. Who would you want to learn that from, and how? For me I’d want to sit down and pair program with the creator (not The Creator, but you get what I mean) of the tool, and then someone who has vast experience implementing this and finally someone who knows this tool well on my platform. Preferable all three together. This book is exactly that. It’s an opportunity for you to learn Cucumber from Aslak Hellesøy (the creator of cucumber), Matt Wynne that has consulted and trained on the tool for a long time and Seb Rose that have build the Java Implementation. Now, the important thing to remember about Cucumber is that it’s not about the tool. Specification by example (BDD) is first and foremost a communication and collaboration technique that doesn’t really need a tool. I’ve got a...

M: “… hahaha, exactly. And speaking of RT*M, you know what I did yesterday?” H: “No, but I like it already. Tell me more.” M: “So I wanted to whip out a fast little Koa site. It’s sooo good for those” H: “Yeah, I know. You told me like a million times.” M: “Ok… sorry. Off to the terminal I went and went through the usual steps:” mkdir newAwesomeApp cd newAwesomeApp git init npm init npm install koa koa-route --save touch app.js H: “Dude, is this a screen cast or are you going to tell me something interesting already?” M: “Well hang on for just a few seconds more. I wrote my first simple route, to verify it. And I’m glad I did” var app = require("koa")(); var route = require("koa-route"); // routes app.use(route.get("/", function *(){ this.body = "Yup, it's working!"})); // start it app.listen(3000); console.log("App listening... http://localhost:3000"); H: “I’m...