The author mentions in the footnotes he mostly uses this setup for note taking. That makes sense as he probably remains in one window for extended periods of time.

This makes me wonder why most of us use Java at all. In your typical web app project, classes just feel like either:

1) Data structures. This I suspect is a result of ORM's not really being ORM's but actually "Structural Relational Mappers".

- or -

2) Namespaces to dump functions. These are your run-of-the-mill "utils" classes or "service" classes, etc.

The more I work in Java, the more I feel friction between the language, its identity(OO beginning to incorporate functional ideas), and how people write in it.

If something is nested, let it be represented as a nested structure. I find flattening causes more mental overhead. If something is too flat, it becomes less obvious what data is exactly necessary to do what you want to do

Code in any form can generate a ton of incidental complexity. The issue isn't the tool rather than the education to properly wield those tools. Especially when you introduce the team dynamic where everyone has varying understandings of what is being built and how it should be built.

I don't fully understand the quote from Djikstra where he first talked about this but I'm sure he didn't mean it as it's interpreted today: "draw invisible boundaries in random places because best practices."

That's probably the fault of the people writing it. People can also write crap looking code using frameworks too.

> and never able to achieve the interactivity the front-end can.

That's what small sprinkles of javascript is for. You don't need incredibly beautiful interactivity in every pixel.

[1] https://tic80.com/

https://github.com/jeremyevans/sequel/discussions/2198

This, imo, is one of the big reasons people so easily dismiss OOP. They put whatever data _they think they probably need_ in an object using setters/builders/what have you. This leads to abstractions of data that don't accurately reflect state. They will then let an external entity (service or whatever pattern) manipulate this data. At this point people might as well use something analogous to a C struct where anything can be done to the values. Objects are not managing their own invariants. When you rip this responsibility from an object, then nothing becomes responsible for the validity of an object. Due to this, people wonder why they get bugs and have trouble growing their software.

This also leads to things like "isValid". People don't understand that an object should be constructed with only valid data. The best example I've found of protecting variants and construction of valid objects to be this strategy in F#:

https://fsharpforfunandprofit.com/series/designing-with-type...

I'm yet to find a good way to do this in a language such as Java unfortunately.

1. Hot reloading code. As a Java developer, this is important for prototyping as I can iterate quicker.

2. Clarity. I can read exactly what's going on and I know exactly what query is being executed.

The pervasive "compostable library" mindset also completely ignores the other benefits of having a standardized framework such as Rails that people can rally around: 1. Standardized documentation 2. Being able to create community that can provide support when you're having issues 3. Easily google-able solutions to common issues 4. A standard that can be iterated upon. I feel like Clojure libraries do this somewhat already so they can work with each other so what's the harm on standardizing these interfaces?

Remote: Yes

Willing to relocate: No

Looking for: Full time or part time

Technologies: Java, AWS(SNS,SQS,EC2,DynamoDB), Neo4j, Spring Boot, (always open to learning more!)

Resume/CV: https://www.linkedin.com/in/ericjflick/

Email: flick.eric.j [at] gmail.com

About: Backend software engineer for 4 years. Worked at two companies in the past -- one large, one small. Even though I've been primarily a Java person in the past, I'm very much looking to try out different languages and frameworks while working in different parts of the stack! Have been abroad studying at a language school the past year and am looking to get back in the game!

Remote: Yes

Willing to relocate: No

Looking for: Full time or part time

Technologies: Java, AWS(SNS,SQS,EC2,DynamoDB), Neo4j, Spring Boot, (always open to learning more!)

Resume/CV: https://www.linkedin.com/in/ericjflick/

Email: flick.eric.j [at] gmail.com

About: Backend software engineer for 4 years. Worked at two companies in the past -- one large, one small. Even though I've been primarily a Java person in the past, I'm very much looking to try out different languages and frameworks while working in different parts of the stack! Have been abroad studying at a language school the past year and am looking to get back in the game!

Remote: Yes (preferred)

Willing to relocate: No. (American citizen but will be remaining in Taiwan for the foreseeable future).

Looking for: Full time...but would be down for part time

Technologies: Java, AWS(SNS,SQS,EC2,DynamoDB), Neo4j, Spring Boot, (always open to learning more!)

Resume/CV: https://www.linkedin.com/in/ericjflick/

Email: flick.eric.j@gmail.com

About: Backend software engineer for 4 years. Worked at two companies in the past -- one large, one small. Even though I've been primarily a Java person in the past, I'm very much looking to try out different languages and frameworks while working in different parts of the stack! Have been abroad studying at a language school the past year and am looking to get back in the game!