@therealdanvega What Java is really missing here is a stronger concept of subpackages.
With "package by feature" I often struggle with shared or cross-cutting concerns. If every concern becomes its own module, the root package can quickly turn into a flat, unstructured list.
@1ovthafew By "rich internal life," do you mean those psychopaths who are smiling while biking alone in the rain because whatever’s happening in their head is better than reality?
@Lutra_Gaming I love this scene and the music! What I had a hard time with was that the ship was pointing towards the Amargosa sun when it exploded. It had to do a full 180 to warp away with a second to spare.
@WindyTheCollie@Lutra_Gaming Well, they can see through the chief engineers eyes and adjust to any frequency change. That wouldn't be very interesting to watch.
@simas_ch I've been trying out Codex and am now comparing it with Claude code. It's hard to figure out where the boundaries are of what each can do. Or what the cost difference is. Undiscovered country
@simas_ch@sivalabs I mostly work on legacy refactorings. Stakeholders are gone, domain knowledge is lost, and the code is the only source of truth. I refactor incrementally into small aggregates (bottom up) with integration tests (top down) as a safety net.
@sivalabs I feel like things like hexagonal get shoehorned in with DDD. My brain usually works bottom up, so I like the concept of aggregates as the smallest unit in the system.
@sivalabs I’ve found that modeling the domain as aggregate trees has kept me from modeling the domain separate from the persistence tech.
OneToManies, converters for value types, and UserCompositeType for sealed interfaces or records with multiple components.
@simas_ch My repositoryFactoryBeanClass stopped working, I had to change my custom repository base class into a fragment.
I had to change new HttpEntity(null) into HttpEntity.EMPTY.
So far it's going great