Consider to take look on http://intive-fdv.github.io/DynamicJasper/ It is more code friendly Jasper wrapper to provide reports. Plain jasper is very XML heavy and you will end in wrapping it in some template engine at some point to reduce repetition. Otherwise download the Jasper Report studio crate simple reports and play around. There are maven and gradle build plugins that compile reports during the build and then you can work with compiled versions.

Jasper by itself is not a bad technology and work quite good for designing reports.

Yes. It is much in vogue. Especially in big corps. And Big corps have no idea what they doing. A year ago I had helped couple of managers to “go back to engineering”, because org had to many managers.

The amount of people who can make code and manage is very limited. But it is very alluring from the perspective of human resource optimization for people to do both. You take decent engineer => You receive shitty miserable manager that can code something non essential. This is very sad.

Big corps are like a pythons on ketanol. They have no idea what happening but they want to grow and shit profits everywhere.

Tldr; take offer, don’t quit engineering yet, you are fine

Don’t quit engineering if you enjoy it. If you have better offer and the current ship is leaky as fuck => jump the ship. Saving the leaky ships should be very profitable if it is not => you are being heavily exploited.

I jumped the ship thrice. And one time accepted a lower payed position, just because I was quite burnout.

On the topic not using the progress and not understanding the Intenals. Understanding internal will not make you senior. Understanding what you can apply that you already know can make you senior. I remember being in a situation like yours. I thought I didn’t know Jack, but then on a newplace I seen people who were running around like a headless chickens on crack. This has given me a good understanding about what knowledge is and that applicable knowledge is the key.

Coding interviews are a decent way to screen out the false positives. Watching someone solve coding challenges gives you some assurance that they can, well, code.

Hahahahaha. If only. There is very big distinction between ability to priduce code that solves the problem and solving the problem. My personal experiense showed me that passing the coding interview and being a good Software engineer is a two different skills.

There is no love if you dont constructor it. Then you would need to initialize it or use existing instance to borrow. You can even extend from Respect or Humor as a starting point, there is no need to implement Love from scratch.

Is it possible to build XML parser in it?

If answer is yes then i will build XML parser in it.

Solving a problem you know how to solve and solved more than once is a my goto approach in learning languge or frameworks. Translation of already solved problem to the new operational model or semantic exposes a lot internal stuff and marketing double talk.

This is a lot of work and time so can not recommend it for all cases and situations.

in many cases for text docs I’d rather write them using markdown and maybe add some html styling then convert with pandoc

Yep. Exactly the case. Using the multiple instruments instead of one “specially created for this reason” programm become normal. And it become normal because the program become unpredictable in changes. All the functionality is click away, but you need to know what to click.

And as a chery on top Outlook by default uses ctrl+f to forward a message. Instead of starting search.

I wholeheartedly agree with that. Every version of Excel is massively worse than previous one. Same with the other Office products. Incremental fixes and impovements covered with unneded features and Ribbon design.

The Ribbon interface intoduction is the most obnoxious design decision that was pushed to the keyboard and mouse users. It only helps “touch” or “pen” users and only marginally.

Then OneDrive aka “we holding your data ransom” Drive. This is the only one Drive that is purelly sheit.

Which OOP? Alan Kay meant this:

OOP to me means only messaging, local retention and protection and hiding of state-process, and extreme late-binding of all things. It can be done in Smalltalk and in LISP. There are possibly other systems in which this is possible, but I’m not aware of them.

But there is also various other OOP around. And those really about completly different things.

People hate Java when they are forced to use it. Or when they switch from other language to the Java and expect same semantics and behaviour. Historically Java was quite bad in character/sense ratio this coupled with Enterprise patterns and people who have no idea how to write programs on java resulted in atrocious code bases with nightmare episodes. Currently I am writing non-stop Java for about 15 years. And I am able to tolerate Java quirks, because I know how to side step them. I don’t like Java, but given the choice I would pick it as a language that I am willing to code for money out of many others. Java have amazing ecosystem, ci/cd culture and instruments. Dunking on “bad” language is okay especially in the joke context.

In the end there is no ideal language, they are just more or less fitting for a task or role.

Clojure. Simple language for complex things. It also has java interop and Javascript interop and c# interop. So I will be fine.

Thank you for sharing link to the site! I have found 4 new terminal fonts to try.

Some might. I using Comic Code and Fantasque Code from time to time as it forces my brain to reinterpret “known” code and helps to find errors that way. It also help with minor dyslexia moments. I like Radon, except I fully hate how “i” character is looking it is a “z” with a dot on it. If there were variant with normal “i” I would consider using it.

And release zip contains a _MACOSX folder which is a clear indication of sloppiness and/or rushed release. … and ligatures don’t work out the box in JetBrains product IDEs.

And if only they slapped beta on this there will be not problem what so ever…

Will Amper kill Maven and Gradle?

If it works and it is free then maybe, but probably still not. Also it is a Gradle plugin, so it will not touch Maven at all. And it uses yaml configs… I do not like this at all 😀

Maven is very good for small projects and Gradle take a niche of Ant on steroids. Nobody in his sane mind will migrate from one build system to other until benefits of migration outweighs the burden of redoing all pipelines from scratch.

The problem with JB products that they are barely working now. If you step one iota outside of mainstream functionality then it will break.

Both Maven and Gradle integration are very very brittle. And also not really optimized for big projects with big amount of modules/sources.

And I love JB products. It saddens me to see every year I drops in quality of IntelliJ. And New fancy interface transition is just the mess.

Migration to the subscription based allowed JB to release more products but overral quality dropped.

And sadly one more font I will never be able to use due to missing support of non-latin characters.

Sadly some features are nice.

Game mods and Advent Of Code did it for me.

I did a small RimWorld mod and a parser for NoManSky internal format.

Creating both of them was a blast. I had fun doing programming stuff again.

Advent Of Code allowed me to try different languages in a small bursts of the different problems. Somehow I really like this format.

From my personal consumer experience I would say twitch streams and steam demo fest are my two main sources of new games to “put a pin”. And on twitch I mostly watch small channels (below 200 viewers), with couple of exceptions.

And also there is a lot of cases where you really don’t need or want static typing. Static typing and type systems are great when they helping you but very bad when you are forced to fight them due to compiler problems or bad modeling.

In the end it is all an engineering problem: which amount of your budget you need to spend on proving programm correctness. Cost/benefit and all of that.

Static typing and unit tests don’t make your codebases great, safe and supportable. Thinking and understanding your usecases, decomplecting problems and some future planning wins.

I am very very skeptic about this whole DORA org and approach and adoption. I have a greatest respect to the DevOps philosophy, but from DORA I only got a baseless/faceless metrics. Maybe it is also Google driving it that gives me additional rejection impulses. I am quite skeptic at what and how Google does and this colors my perception of all thing it produces.