[JAVA] Introduction of IDOM engineer's development environment (physics)

What is this?

A glimpse of the development environment of such IDOM engineers may give you an idea of how challenging you are. So I would like to introduce the development environment (physics) of each engineer.

Gulliver flea market team engineers

Now, let's take a look at the development environment (physics) of the engineers of the team in charge of the development of Gulliver Flea Market!

It's neat and tidy and seems to do the job well.

On the contrary, there are few things here and it is cleaned!

As you can see, it's said that you have a personality, it's beautiful and nice!

Car Connect Team Engineers

Next, I would like to introduce the development environment (physics) of the engineers in charge of the development of Car Connect!

Car Connect is being developed by a group of engineers.

The leader of the car connect engineer directs the development using multiple machines.

It's a little small because it's crowded, but it's an environment where team development is likely to progress!

NOREL team engineers

And finally, I would like to take a look at the habitat (partially remote) of the engineers of the service NOREL that I am in charge of.

NOREL works in a conference room, regardless of whether it is an engineer or a non-engineer. It is useful because you can use the whiteboard freely (it is hard to forget to erase it ...).

It is a tidy desk in the team. It's cute to have a lot of drinks!

I'm an engineer who joined me recently, but I'm using a good keyboard. I envy you ...! !!

This is a picture of the members who are participating in the development remotely, although the scenery has changed completely. The picture of the room is simple and cool, unlike the outside scenery! (However, it seems that it is cold now and I am working in the living room).

This is my desk, but I'm longing for an ergonomic keyboard, but I can't afford it, so I'm trying to prevent stiff shoulders by combining the MacBook Pro keyboard and HappyHack keyboard (lite) with pseudo ergonomics.

Summary

How was that. You can imagine the work of our engineers. There is a development environment (physics) that I couldn't introduce this time, but I couldn't take enough time to suppress the photos, so let me do that next time.

that's all. I'm sorry.

bonus

I think that the technical content is insufficient as it is, so I would like to introduce the image processing program posted this time.

Trigger

When I posted this blog, I wanted to reduce the image, and when I realized it, I implemented it in Java. I will publish it in the hope that it will be of some help.

prototype

First of all, I tried to reduce it by simply calling java.awt.Graphics # drawImage (cutting out).

public static void main(String[] args) throws Exception {
	final String inputPath = %Input image path%;
	final String outputPath = %Output image path%;

	BufferedImage org = ImageIO.read(new File(inputPath));
	BufferedImage dist = new BufferedImage(600, 800, org.getType());

	Graphics g = dist.getGraphics();
	g.drawImage(org, 0, 0, dist.getWidth(), dist.getHeight(), null);
	g.dispoise();

	ImageIO.write(dist, "jpg", new File(outputPath));
}

The processing content is simple, the image is read with javax.imageio.ImageIO # read (), the image is processed, and it is output with javax.imageio.ImageIO # write ().

(I tried to upload a reference image, but I omitted it because I was caught in the Qiita limit)

I can still output it, but I wasn't convinced that the jagi was so bad that I decided to devise a little.

A little more properly

Next, try to reduce the image by using java.awt.image.BufferedImage # getScaledInstance () and then export the image.

public static void main(String[] args) throws Exception {
	final String inputPath = %Input image path%;
	final String outputPath = %Output image path%;

	BufferedImage org = ImageIO.read(new File(inputPath));
	BufferedImage dist = new BufferedImage(800, 600, org.getType());

	Graphics g = dist.getGraphics();
	g.drawImage(org.getScaledInstance(dist.getWidth(), dist.getHeight(), BufferedImage.SCALE_AREA_AVERAGING), 0, 0, dist.getWidth(), dist.getHeight(), null);
	g.dispose();

	ImageIO.write(dist, "jpg", new File(outputPath));
}

Now there is no jagi and it can be reduced neatly. I think that the same processing will be done in a few lines in other languages, but in the case of Java, if you install only Runtime (SDK when developing), it is all-in-one, so it is nice that it can be executed easily!