Some time ago we wrote about the process of building Nortal Technology Radar. Today we’d like to share the radar itself. While reading this, please keep in mind that our technology radar is an opinionated view of our developers. This should not be studied as a research or considered as Nortal’s official point of view. Read more
Few months ago around twenty developers from Nortal gathered in a forest cabin to discuss our experiences and all things relevant in software development and as a result build Nortal Technology Radar. The result has already proved to be valuable but the process itself taught us a lot as well. I want to share the process, our experience and lessons learnt from building the radar.
Baltic DevOps conference in Tallinn hosted more than 130 participants this year. Nortal sponsored the event and of course participated as well. The conference had two tracks: Technical DevOps and Organizational DevOps. These two cover wide range of aspects within this topic. The content and knowledge shared proved to be of high quality and valuable for me personally.
You probably know and hopefully have used SonarQube. It’s a great tool that is actively evolving and improving. This is great if you are a developer using SonarQube. However, if you happen to administer SonarQube instance, the constant upgrades are quite a hassle since upgrade guide consists of 11 steps.
This article first appeared on Risto’s personal blog.
Ethereum is one of the hottest things in the world of cryptocurrencies. As it has finished its first big release, here is my take at explaining what it is about.
My story begins with a tool called Streamtools that my coworker showed me another day. It is an open source project by The New York Times R&D Lab which provides a general purpose, graphical tool for dealing with streams of data. It provides a vocabulary of operations that can be connected together to create live data processing systems without the need for programming or complicated infrastructure. Sounds like a dream.
What is development environments automation? Why use it? What problem it solves?
Imagine you are a developer just assigned to a new project. There are some new cool ideas to be realized and you are given some good challenges in this project. You are full of excitement to begin coding. Now you just need to set up the environment.
We’ve been using Tomcat 6.0.x in several projects for years, and some of them have finally settled plans for major upgrade. In one particular project an interesting performance issue was encountered. After some minor corrections to code, the project was running on Tomcat 8.0.18. The application ran well, but slowly… The startup time had gained ~33% and response times were dreadfully bad, we encountered 2-3-fold slowdown for even the simplest pages. This needed a bit of investigating to sort everything out and we decided to share these results with you as well. Might be useful if you plan to migrate, or if you already use Tomcat 8 you could check if this issue applies to your application as well.
A few months ago I decided to try out new things and switched my programming language from ActionScript 3 to Java. I have heard that these kind of radical shakeups work out pretty well at last and I hope that with each day I feel a bit less of a newbie. Knowing OOP and having a real working experience as a developer has been helpful, but what I really need is TIME. Eventually (I hope) the whole system will come together like a huge and almost completed jigsaw puzzle.
Here at Nortal, we recently held our second annual internal Hackathon.
This year, we picked IoT (Internet of Things) and cloud computing as our main themes, mirroring both the current interests of Nortal Finland employees and the general direction of the tech-breeze on the IT-field.