Forem: Hyesung Lee

Introducing Hit Counter for Your GitHub or Any Kind of Websites You Want

Hyesung Lee — Mon, 21 Feb 2022 01:37:06 +0000

What is Hits?

Hits is a simple and easy to use web application that counts the number of hits on your website.

If you're familiar with GitHub, you've probably already seen hit counter in the documentation on the GitHub repository:

Getting Started

Hits supports the following three of the most common use cases: Markdown, HTML and Image Link.

For example, to get a hits badge for https://github.com/silentsoft/hits:

Markdown

  [![Hits](https://hits.sh/github.com/silentsoft/hits.svg)](https://hits.sh/github.com/silentsoft/hits/)

HTML

  <a href="https://hits.sh/github.com/silentsoft/hits/"><img alt="Hits" src="https://hits.sh/github.com/silentsoft/hits.svg"/></a>

Image Link

  https://hits.sh/github.com/silentsoft/hits.svg

Features in Query String

view

total (default)
today-total

style

flat (default)
flat-square
for-the-badge
plastic

label

For setting the label text instead of the default hits.

extraCount

This is useful if you want to add an extra count to your badge. For example, if you want to add a count of 1000 to your badge, you can set extraCount=1000.
When Do I Need This?
- If the hit counter service you used previously has end-of-service, you can start with any number instead of starting from 1.

color, labelColor

Named color by shields.io
Any valid CSS color
- named color
- hexadecimal numbers
- rgb[a](red, green, blue[, opacity])
- cmyk[a](cyan, magenta, yellow, black[, opacity])
- hsl[a](hue, saturation, lightness[, opacity])

logo

simple-icons slug
or data:image/svg+xml;base64,..

Statistics

You can see the statistics of your website by replacing the .svg with / in the URL you used to get the badge.

For example, to get a statistics for https://github.com/silentsoft/hits then visit https://hits.sh/github.com/silentsoft/hits/

Conclusion

Hits is a simple, easy to use, and free to use hit counter badge for your website.

Thank you for reading this article. If you like Hits, give it a 🌟 on GitHub.

Hits

Getting Started

Hits supports the following three of the most common use cases: Markdown, HTML and Image Link.

For example, to get a hits badge for https://github.com/silentsoft/hits:

Markdown

[![Hits](https://hits.sh/github.com/silentsoft/hits.svg)](https://hits.sh/github.com/silentsoft/hits/)

HTML

<a href="https://hits.sh/github.com/silentsoft/hits/"><img alt="Hits" src="https://hits.sh/github.com/silentsoft/hits.svg"/></a>

Image Link

https://hits.sh/github.com/silentsoft/hits.svg

Features in Query String

view

total (default)
today-total

style

flat (default)
flat-square
for-the-badge
plastic

label

For setting the label text instead of the default hits.

extraCount

This is useful if you want to add an extra count to your badge. For example, if you want to add a count of 1000 to your badge, you can set extraCount=1000.
When Do I Need This?
- If the hit counter service you used previously has end-of-service, you can start with any number instead of starting…

View on GitHub

What Kind of Tool Do You Use to Control Spring Batch Jobs?

Hyesung Lee — Thu, 27 Jan 2022 00:40:16 +0000

Are there any open source tools you are using or know of to do something like below?

Perform Jobs
Monitoring Jobs (stats, log, ..)
etc

Measuring Code Execution Time Using Stopwatch

Hyesung Lee — Wed, 26 Jan 2022 02:36:33 +0000

You might have used the System.out.println(end - start + "ms elapsed") through System.currentTimeMillis() to measure the execution time of a piece of code.

If you have a small number of code points to measure, it can be quite appropriate to do this.

But when we have a lot of code points to measure, this makes us difficult.

If you want to see the result with a meaningful name and how much of the total time it takes, you have to add cumbersome code to do it. like:

long start = System.currentTimeMillis();

long initStart = System.currentTimeMillis();
// initialization
long initEnd = System.currentTimeMillis();

long processingStart = System.currentTimeMillis();
// processing
long processingEnd = System.currentTimeMillis();

long end = System.currentTimeMillis();

System.out.println("initialization: " + (initEnd - initStart) + "ms");
System.out.println("processing: " + (processingEnd - processingStart) + "ms");
System.out.println("total: " + (end - start) + "ms");

It's Time to Use Stopwatch

Stopwatch is a library that helps you measure the execution time of a piece of code with a meaningful name and how much of the total time it takes.

We can simply use it like this:

Stopwatch stopwatch = new Stopwatch();

stopwatch.start("initialization");
// ...
stopwatch.stop();

stopwatch.start("processing");
// ...
stopwatch.stop();

stopwatch.start("rendering");
// ...
stopwatch.stop();

stopwatch.print();

The stopwatch.print() will give you the result like this:

|           name |     % |      ms |      s |
|----------------|-------|---------|--------|
| initialization | 59.5% | 1,234ms | 1.234s |
|     processing | 40.0% |   830ms | 0.830s |
|      rendering |  0.5% |    10ms | 0.010s |
|                |       |         |        |
|          total |  100% | 2,074ms | 2.074s |

One More Thing

The Stopwatch can be paused and resumed to remove the time between code points where you do not want to measure. like this:

stopwatch.start("rendering");
// prepare rendering
stopwatch.pause();
// load font stuff
stopwatch.resume();
// render
stopwatch.stop();

Conclusion

Stopwatch can remove chores from your code. If you have a lot of code points to measure, or you want to see the result with a meaningful name and how much of the total time it takes, you can use it.

Thank you for reading this article. If you like Stopwatch, give it a 🌟 on GitHub.

Stopwatch

Stopwatch for get rid of chore in your code.

Usage

Stopwatch stopwatch = new Stopwatch();

stopwatch.start("initialization");
// ...
stopwatch.stop();

stopwatch.start("processing");
// ...
stopwatch.stop();

stopwatch.start("rendering");
// ...
stopwatch.stop();

stopwatch.print();

Result

|           name |     % |      ms |      s |
|----------------|-------|---------|--------|
| initialization | 59.5% | 1,234ms | 1.234s |
|     processing | 40.0% |   830ms | 0.830s |
|      rendering |  0.5% |    10ms | 0.010s |
|                |       |         |        |
|          total |  100% | 2,074ms | 2.074s |

Maven Central

<dependency>
    <groupId>org.silentsoft</groupId>
    <artifactId>stopwatch</artifactId>
    <version>2.2.1</version>
</dependency>

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like…

View on GitHub

5 Things You Should Remember When You Are Getting Code Review

Hyesung Lee — Mon, 24 Jan 2022 17:00:34 +0000

Code review is an essential part of creating high quality software.

One of the things that I disappointed while reviewing co-workers code at work a few years ago was the attitude. In a code review conducted with several people, if one of them speaks emotionally, the person who is receiving the review is likely to be tired and upset. No matter how code review to make better software, but who would like it if they heard sadistic words when they did their best?

So I'm going to summarize the 5 things that I think would be fine if we knew each other.

1. Avoid Aggressive Questions

"Why did you write it like this?"

This kind of question makes the listener feel uncomfortable. And it embarrasses people who are watching the code review. Remember the purpose of code review. We are doing this not to criticize other people's code and/or to imprint that who is more superior but to find bugs in advance and make better software.

"How about this one?"

Let's start to talk like this. However, we should make it clear that it is not a personal taste by giving a proper explanation or reason.

2. Listen First and Speak Last

If the reviewer keeps making comments while he/she is explaining the code and intention, the flow will break repeatedly. And not only who are receiving code review but also those who are watching the code review are getting tired. Taking notes or remembering rather than immediately discussing improvements or questions about code is much more effective at avoiding emotional comments. Because it makes you think again.

At this moment, the person who wrote the code will need the trick of cutting it off properly so that it will not be taken too long like in terms of class file or small business unit.

3. Praise and Encourage Immediately

"I think this code is very good."

"Looking at the code you wrote, you must have had a hard time..."

What more needs to be said?

4. Avoid Unnecessary Arguments

There is no worse code review than discussing "Declaring variables across multiple lines v.s. Declaring variables side-by-side with commas". Of course, that wasn't the main issue of the code review but let's respect other people's tastes. Nevertheless, if it is bothering you, defining code conventions after gaining majority consent can be a good way to avoid unnecessary arguments.

5. Give Direction for Good Code, but Don’t Force It

"You have to change this line like this."

Is it an industry standard? Then accept it. Is it a ground rule on your team? Accept it too. Is there a potential possibility of an error if you don't change it? Fix it right away.

What I mean is don't force changes to code that works regardless of the changes. If it is not a violation of an industry standard or ground rule, then it should be their choice whether to change it or not. If the reviewer forces such a code so that members receives a negative result such as Failed or Rejected, then the team members will blame themselves. Furthermore, the morale of the entire team will drop at some point. These threats should be eliminated whenever possible.

The Semantic Emptiness of Objects in the If Statement

Hyesung Lee — Wed, 19 Jan 2022 03:11:10 +0000

Philosophy

A semantic emptiness is a key concept used to indicate the absence of a value. Even if an object is not actually referenced as null, it can be considered null if it is semantically filled with empty values.

In the beginning there was...

You had to convert an empty value to null to persist it in a database. Also you had to convert null to an empty string to display it in a GUI or something elsewhere like Stream or Writer. If you don't want to use null at all, you had to write a code to getting default value/object. like this:

if (value != null && value.length() <= 0) {
    entity.setValue(null);
} else {
    entity.setValue(value);
}

entity.setValue(value == null || value.length() <= 0 ? null : value);

Okay, That's totally fine. But how about this?

entity.setValue(Nullify.of(value));

in some cases, you might want to use empty string("") instead of null:

Nullify.toString(value);

Further, checking for semantically empty

if (collection == null || collection.size() <= 0) {
    collection = Arrays.asList("default_value");
} else {
    boolean isSemanticallyEmpty = true;
    for (String value : collection) {
        if (value != null && value.length() > 0) {
            isSemanticallyEmpty = false;
            break;
        }
    }
    if (isSemanticallyEmpty) {
        collection = Arrays.asList("default_value");
    }
}

above code can also be replaced with:

Nullify.of(collection, Arrays.asList("default_value"));

Conclusion

If you're tired of writing code that checks whether a value is semantically empty or not, you can use Nullify.

silentsoft / nullify

Nullify for null representations and assertions of objects.

Nullify

Nullify for null representations and assertions of objects.

Philosophy

A semantic emptiness is a key concept used to indicate the absence of a value Even if an object is not actually referenced as null, it can be considered null if it is semantically filled with empty values.

In the beginning there was...

You had to convert an empty value to null to persist it in a database Also you had to convert null to an empty string to display it in a GUI or something elsewhere like Stream or Writer If you don't want to use null at all, you had to write a code to getting default value/object. like this:

if (value != null && value.length() <= 0) {
    entity.setValue(null);
} else {
    entity.setValue(value);
}

entity.setValue(value == null || value.length() <= 0 ?

…

View on GitHub

Forem: Hyesung Lee

Introducing Hit Counter for Your GitHub or Any Kind of Websites You Want

What is Hits?

Getting Started

Features in Query String

view

style

label

extraCount

color, labelColor

logo

Statistics

Conclusion

silentsoft / hits

📈 Hit Counter for Your GitHub or Any Kind of Websites You Want.

Hits

Getting Started

Features in Query String

view

style

label

extraCount

What Kind of Tool Do You Use to Control Spring Batch Jobs?

Measuring Code Execution Time Using Stopwatch

It's Time to Use Stopwatch

One More Thing

Conclusion

silentsoft / stopwatch

⚡ Stopwatch for get rid of chore in your code.

Stopwatch

Usage

Result

Maven Central

Contributing

5 Things You Should Remember When You Are Getting Code Review

1. Avoid Aggressive Questions

2. Listen First and Speak Last

3. Praise and Encourage Immediately

4. Avoid Unnecessary Arguments

5. Give Direction for Good Code, but Don’t Force It

The Semantic Emptiness of Objects in the If Statement

Philosophy

In the beginning there was...

Okay, That's totally fine. But how about this?

Further, checking for semantically empty

Conclusion

silentsoft / nullify

Nullify for null representations and assertions of objects.

Nullify

Philosophy

In the beginning there was...