Naresha

Java developers, reading text from a file is not a thing anymore!

Suppose you have to read the contents of a text file. This is a commonly recurring task. If you think about the amount of code required in Java or have the experience of already implementing it, you would agree with me that it takes a significant amount of code. Following

Groovy file operations - execute around pattern in action

In an older post, I described Execute Around Pattern. In this post, let's understand how this pattern simplifies the solution while reading from files and writing to files. Suppose we have a text file that contains a few names one name per line. We want our program to

IDE generated code - a good idea?

In my previous post I mentioned how pain acted as a trigger to positive action. In this post, let's analyse potential solutions to the problem I had mentioned in the above post and what can we learn from them. At the time of this incident, our team was

Using Pain as a Trigger to Positive Action

Recently I gave a talk titled "Evolving with Java - How to Remain Relevant and Effective" in GIDS on the Java Day of the conference. The talk was centred around using pain as the triggering point for positive action. Let me tell you the incident that triggered this

Evolving with Java - How to remain Relevant and Effective

Evolving with Java - How to remain Relevant and Effective from Naresha K

Micronaut External Config

In one of the previous posts, I described how to have configurations per environment and why it a bad idea to build your jar for every environment. Also we saw how to read configuration values from property sources. Many times you might not be in a position to enumerate your

Effective Java with Groovy - How Language can Influence Good Practices

Effective Java with Groovy - How Language can Influence Good Practices from Naresha K

Micronaut - A common mistake with the use of @Value

Micronaut provides io.micronaut.context.annotation.Value for injecting value from the property source into a variable. Spring framework also provides a similar annotation. Can you spot the mistake in the below code? package com.nareshak; import io.micronaut.context.annotation.Value; import io.micronaut.http.MediaType; import io.micronaut.

Micronaut Environment Specific Configuration

In my previous post I described the anti-pattern of rebuilding your artifacts for every environment and explained why it is a bad idea. I also mentioned that modern frameworks support environment specific out of the box. In this post let's see this in action using Micronaut. I will

If you are building your artifacts per environment, you are doing it wrong

I have heard several times developer telling me how they build their artifacts before deploying to each of their environment. Yes, they build a jar for dev and instead of promoting the same jar to their acceptance testing environment, they rebuild the jar specifically for their UAT environment. Here is