On may 1st 2012, Atlassian released a new product called Stash. Stash is a Git repository manager. People that know Atlassian would say “Hey, isn’t it the same as FishEye?”. Well no, it’s not the same. FishEye is for looking at ALL of your source code, in any source repository. Stash is a repository manager for Git only. So how is it different then?
We’re holding another one of our monthly “Techday” events this week. We organize techdays because we like to stay sharp and have some fun in the process (Check out our previous blog post about why we do techdays).
This month’s techday is on thursday april 26th in our Avisi offices in Arnhem. This time about the Play framework. Want to join the fun?
Since Atlassian released their OnDemand platform, customers have been asking for more plugins to be made available there. Until now, only 7 plugins are offered on the new platform.
The current approach of in-VM plugins incurs a very high cost in development, QA, and support time. This is due to tight coupling and increased security and stability risks.
The Atlassian Remote Apps project aims to bring the benefit of third-party extensibility to OnDemand by dramatically lowering the costs and risks related to third-party code.
We investigated the possibilities to setup a remote app for enabling Numbered Headings for OnDemand. Here are our findings…
In my last blog I talked about exploring Kotlin, a JVM language in development by JetBrains. In this blog I’ll walk through a larger piece of Kotlin code.
Spell checker
The program we’re talking about is a simple spell checker. It reads a dictionary of words from a file (/usr/share/dict/words) into a set. Then it reads a sentence from stdin and checks if every word is in the dictionary. Finally it informs the user whether or not the sentence is spelled correctly, i.e. every word is known in the dictionary.
The spell checker is available on my GitHub. Take a moment to study the Java version, we’ll discuss the Kotlin version next. Continue reading
Here’s another one on pair programming: When you hear the driver saying “let’s write a unit test first”… the navigator is too slow.
At Avisi we use a custom built EJB 3 based application for scheduling and running (automated) regression tests. This involves a queue from which objects are taken. These objects contain metadata describing the tests to execute. I won’t go into detail as to why we aren’t using Apache ActiveMQ (or a similar library) for this purpose, but I can say that we didn’t need distributed test-executing minions at that time.
Continuous integration and code quality management tools are pretty much used by every project. And it’s a must if you are in for high quality code. But these tools also need to be managed… or they will manage you.
Last week we held our monthly techday, this time the topic was an introduction to NoSQL databases.
When you are the driver in a pair programming session and you find your navigator grabbing the keyboard all the time it’s time for a good talk. The rule is simple: You hand off the keyboard when pair programming, you don’t grab it.
In my previous post (Part I – Introduction) I gave an introduction to Walle, Avisi’s information radiator. After making some high-level design decisions we started focussing on developing the front-end. When we got the final version of the visual design, it appeared that HTML5, CSS3, jQuery and websockets could make it work. This post shows some highlights of the HTML5 and CSS3 features we used.