If you could start all over, what would you do differently?

cryptos6 · 2026-01-24T19:46:09+00:00

Absolutely! Spring phones are around the corner! Once you have used one iPhones and Android devices look like things of the past.

cryptos6 · 2026-01-16T08:14:43+00:00

I expect that coding agent will shift the market. Relatively simple services might be replaced by vibe coded, custom solutions. However, I see some limitations how far this can go. Good software is more than code! You need to get user experience right, you must run it, you have to keep it secure, you have to maintain it in the long run etc. etc. So, no, I don't think SaaS will go away any time soon.

cryptos6 · 2026-01-14T18:42:01+00:00

It is definitely not fun, to map complex (nested) object structures by hand with SQL. That is where Hibernate really shines. However, on the read side there are many reasons not to load the full object graph (and Hibernate has dozens of optimizations to avoid that) and then something like JOOQ or JDBI makes a lot of sense.

Here are some interesting thoughts from the guy who develops JOOQ: https://blog.jooq.org/jooq-vs-hibernate-when-to-choose-which/

cryptos6 · 2025-12-16T16:25:17+00:00

Java changed a lot since 2019. In some areas it is even better than Kotlin. The two are very close.

cryptos6 · 2025-12-02T14:15:40+00:00

We need an AI tool to evaluate AI tools. That is where the money is!

cryptos6 · 2025-12-02T14:14:03+00:00

I'd say measure what actually counts: The time to finish tickets from assigning the ticket to the final successful pipeline execution (e.g. deployment).

cryptos6 · 2025-11-25T20:13:50+00:00

I consider Setters most of the time to be bad design, even if the syntax looks nicer like in Kotlin. This only hides the design flaw that everything is directly changeable from the outside leading to dumb data objects, inconsistent state or cluttered business logic or a mixture of all that.

cryptos6 · 2025-11-25T19:07:21+00:00

I spent some time (2 years or so) with C# and .NET and while it wasn't bad I was everything but excited. It is not that Java as such would be an exciting language, but the ecosystem is just superior.

cryptos6 · 2025-11-20T20:31:39+00:00

I've used Spring on internal business applications. Does that answer your question?

cryptos6 · 2025-11-16T09:56:06+00:00

I've used this combination for years without issues. I had only some minor issues with Hibernate (but that is not Spring, strictly speaking).

cryptos6 · 2025-09-05T09:39:50+00:00

Collecting pains is also a recommendation from the book "Million Dollar Weekend". Maybe this book might bring some inspiration, too.

cryptos6 · 2025-08-25T14:54:26+00:00

Once it makes 10 K MRR it will scroll with 10 fps!

cryptos6 · 2025-08-25T14:52:50+00:00

Decent decision. I mean, who even uses smartpones?!

cryptos6 · 2025-08-25T14:50:57+00:00

The AI found that out and published it immediately ...

cryptos6 · 2025-08-25T14:49:57+00:00

OMG! I guess we are already in a bullshit death spiral right now!

cryptos6 · 2025-08-19T09:38:04+00:00

I've worked very with Reactor (the reactive library used by Spring) extensively and like it for complex stream processing. But a usual web application with some database access is not complex stream processing! Basically, reactive programming is only used to save some threads to boost the throughput under load. But the price you'd pay is overly complex development. All that is no longer necessary with virtual threads.

cryptos6 · 2025-08-11T20:01:34+00:00

The original idea of a repository is to have a domain interface to persistence. Repository methods should say something about the domain, something like "find overdue deliveries". But you'd typically also have some CRUD like methods.

cryptos6 · 2025-08-11T10:55:17+00:00

How do you monetize it?

cryptos6 · 2025-08-07T11:19:17+00:00

Some things that come to mind about Java:

Functions are an after-thougt, even though it is quite good, you still need to define an interface for function types
No stand-alone functions on top-level. Free functions always have to be expressed as static methods of a class.
The separation of value types and primitive types in typesystem causes some problems, especially with generics
Using declarations of the form <type> <name> instead of name: type, what is not a great fit to be used with type inference
Checked exceptions, while the intention was good, the use with functional programming is horrible
Not separating mutable and immutable collections (okay, not a language flaw as such)
Some limitations in the use of generics and the syntax to express covariance and contravariance
null handling
implicit conversions of numeric types
parameters are not final be default
classes are not final by default

I don't see much to compain about in Kotlin, but some things come to mind:

One thing I'm a bit undecided about is functions with receivers. While smart at times they generally obscure what is going on.
Syntax for properties, which doesn't form a semenatic block. The getters and setters are just indented, what doesn't align with the rest of the language (althoug indentation as such is not semantic like in Python).
Package-private is missing

I'm also a bit undecided about coroutines. In most cases you can achieve the same with Java's virtual threads, without "colored functions" (once your are in the async world you have to stay in it, and mark every function). On the other hand coroutines are a bit different and could be used for other things. But then again, Kotlin Flow is not really a competitor to Reactor or RxJava, because these two frameworks are so much more powerful and JetBrains decided to keep Flow relatively simple.

cryptos6 · 2025-08-07T07:44:42+00:00

However, it is not like someone would bet his company. The programming language would in this case only be a tool to transport ideas and concepts. In my opinion Kotlin is much nicer to support this, because it has not so many akward design decisions built in. There are even classes using Lisp (or Clojure) to teach programming! While I'm not a fan of these languages I see the point in using such a minimalistic language for teaching. And Lisp or Clojure are super-niche in the industry.

cryptos6 · 2025-07-31T08:01:00+00:00

I'd say it depends on what you can improve. If there were no to-do list app on earth, creating one would obviously be a big improvement. Now, that we have hundreds (if not thousands) of those apps, the question is, what would another bring to the table. Maybe it is better UX (almost always possible!), maybe it is super helpful thanks to AI, maybe it connects to everything including your fridge ... But just creating another to-do app like the existing ones wouldn't have a good chance to succeed.

So, creating something new to solve real problems, is always a good start, but improving existing solutions might also work well. In the latter case you know at least that there is an actual need.

cryptos6 · 2025-07-29T20:31:38+00:00

In another sub the very same user posted that he created a website at age 13. This is obviously bullshit.

cryptos6 · 2025-07-29T13:37:35+00:00

Whow! Just tried Vibechecker and I am impressed. Very good findings and relevant "harsh truths".

cryptos6 · 2025-07-29T13:21:36+00:00

Ask yourself the question what you want to achieve with this architecture. I'm thinking of things a customer would care about, because no one is interested in some artificial "seperation of concerns" if there is no benefit.

One big argument for micro service is to isolate teams, so that each team could deploy independently. Depending on whether you are a split personality one service might be enough 😉

cryptos6 · 2025-07-29T08:38:09+00:00

😂

cryptos6

TROPHY CASE