Naresha's Blog

Latest — Nov 19, 2024

Favour empirical evidence over extended arguments

Often, we get into extended arguments when we have to pick an optimal solution from multiple available options. Especially in the case of science and technology, gathering empirical evidence is a highly effective solution. In this post, I share my experience of a code review. This was the first piece

More issues

Accepting our shortcomings is a pre-requisite for an improvement

In the initial days of my professional career, I joined a project as a Software Engineer. Once I got access to the codebase, I started going through the codebase. The project was using JSP technology for the views (server-rendered views). A senior developer from the team was demonstrating the implementation

What is in a Jargon?

During my interactions with engineers in various training programs, I noticed a common trend - they often used the term' story point' instead of 'user story' or simply 'story'. These engineers, all graduates from reputed educational institutions and had interned at well-known software development

Effective Java with Groovy - How Language Influences Adoption of Good Practices - ApacheCon@Home 2020

Slides Releated blog posts

What's in Groovy for Functional Programming - ApacheCon 2020

Slides Related blog posts

Effective Java with Groovy

Collection of blog posts on how Groovy improves the developer experience of implementing Effective Java practices. 1. GR8Conf EU Talk 2. When float and double put you in trouble! 3. Are you implementing equals and hashCode correctly? 4. Favour Internal Iterators 5. Enabling Order 6. The (in)famous null 7.

What's in Groovy for Functional Programming

Collection of blog posts on functional programming with Groovy. * Closures * Higher order functions * Currying * Function composition * Pure functions * Immutability * Recursion * Tail call optimisation * Memoization * Collect - map operation * Filter * Reduce * Map filter reduce * Strategy pattern * Command pattern * Execute Around pattern

Micronaut Dependency Injection - The stand-alone Setup

In this post, let's explore how to use Micronaut as the Dependency Injection container in a stand-alone Java application. Let's start by creating a stand-alone Java application. I make use of the initialisers provided by Gradle (gradle init command). The application structure looks as follows. ➜ microdemo

Groovy Scripts - Reusable Code

Let's start with the following Groovy script which reads and prints all the properties from a file. import java.nio.file.Path Properties loadProperties() { Properties properties = new Properties() Path propertyFilePath = Path.of('my.properties') propertyFilePath.withInputStream { properties.load(it) } properties } Properties properties = loadProperties() properties.each { println

Continuous Delivery vs Continuous Deployment

There is a good chance that you would have had several debates on what is the difference between 'Continuous delivery' and 'Continuous Deployment'. I have spent several hours discussing this with different groups. Usually, 'Continuous Delivery' implies keeping your software in the releasable state