RSS Feed | Niko Heikkilä

A longstanding grievance with several social media platforms has been how they promote the use of AI in content creation, but for all the wrong use cases.

I was watching Scott Tolinski’s insightful video on Syntax about the negative mental health effects developers experience while coding with AI.

I’m writing this post with Neovim editor.

Ha, got you there, did I?

Originally published on Polar Squad blog.

Originally published on Polar Squad blog.

Originally published on Polar Squad blog.

Originally published on Polar Squad blog.

I’m going to show you two code snippets that solve the same problem of comparing two inputs.

Thomas Ptacek published this article in the Fly.io company blog.

Originally published on Polar Squad blog Generative AI tools have changed how we developers approach our daily work.

Some years ago, I noticed I had grown increasingly frustrated with the modern trends in the software engineering field.

Benefits of Small Batches and Vertical Slicing When capturing and writing down the work we need to do, we often add it to our designated issue-tracking system.

Whenever there is a new film from the master of anarchistic cinema, Yorgos Lanthimos, I must remind myself to bring something to support my jaws into the theatre, for they are guaranteed to drop.

One technique of ensuring my work will be remembered is giving back professional pointers on how the client can improve the quality of their product and process after I’m gone.

The goal of every software team is to deliver the solution into their users’ hands sooner than later.

In the previous chapters, you saw how the heart of our architecture — services, gateways, and domain models — were covered with behavioural IO-free1 tests.

In the previous chapters, I have demonstrated the power of designing and testing a backend within the frontend, but you can only walk so far.

Whether you follow the domain-driven design or not, clean domain modelling is one of the most crucial problems we software engineers must tackle.

In the previous post, I designed our service and use case handlers.

The essence of software lies in the problems it helps us to solve.

Long gone in the past1 are websites that purely displayed static, seldom changing content to visitors.

In software development, there’s a lot of talk about small vs big batches.

The single most important topic in functional programming is to understand what a function is.

I often ponder my work and where I want to head with it.

I’m going to admit something: I had trouble understanding test-driven development (TDD) and it took me a long time to get over it.

I’ve recently participated in discussions related to developer productivity.

Recently, I had a discussion with my team regarding an always timely question: at what level should I write my automated tests: unit, integration, or end-to-end?

This post was originally published in Futurice blog.

Few rules in designing clean code have been as crucial for me as Kent Beck’s four rules of simple design.

Developer: “Hey, could you review my PR?

There is one thing uniting the people working in tech.

There are too many places to mention, but I’ll list a few here: GitHub Explore can offer you many suggested packages based on the GitHub repositories you’ve browsed.

Don’t care about reading much, eh?

The promise on DevTernity conference homepage is to turn developers into architects and engineering leaders.

While dipping our toes with test-driven development for the first time, a significant obstacle is usually finding out how to write our first tests.

In the modern world struck by volatility, uncertainty, complexity, and ambiguity we are still pushed to estimate our work accurately.

Recently, on LinkedIn, I shared my unapologetic opinion that you’re not a professional software developer if you don’t care to write automated tests to verify your code.

Long Time Ago in a Software Company, Far Far Away The product management learns about a speculative need for the Feature that will help the company increase their cash flow.

In software, legacy code is a code that runs in production.

Hey!

I recently finished reading Practical Remote Pair Programming by Adrian Bolboacă.

Many software developers who have at least a couple of years of experience in this industry are often barraged with headhunting letters from recruiters.

During our careers, almost everyone has regular one-on-one meetings, sometimes referred to as performance reviews.

There’s a fascinating law of mathematical theory applicable to agile software development, which helps you deliver features faster without sacrificing quality.

For people doing mainly project work, planning daily tasks is a constant struggle, which can cause severe issues with productivity and mental well-being.

Throughout the observed history, human motivation has adapted to demands and economies of the current age.

This post might come off like a weird spiritual tip for a developer, but bear with me a minute… Santosha A word I came across in yoga that fits very aptly into the 21st-century knowledge work.

Earlier in the summer of 2020, I made a bold decision to refresh and broaden my career from a product company to software consultancy.

By the 2020s, every software company in existence should be using open-source code as building blocks for their products.