@therealchreke I like what unison are up to - the code has one canonical reputation that's stored in a database, not a file, thus the formatting of it becomes a display concern only
@etorreborre ...if I accentuate my prompts towards what I think makes code better than that, and double down on engineering practice around making changes when I'm using an agent (even smaller changes, watch the test fail first, etc.) I can go marginally faster
Extending Records to handle the richer semantics of Classes without losing the benefits of Records. A careful balancing act 🙂
https://t.co/YtjRQ6aaKg
"Java for the AI world"
#java#openJDK#AI
my goal is to become successful enough to use an ipad instead of a laptop. It's the perfect device for the successful man - worse than both a phone and a computer, requiring a staff of people producing actual work to maintain communications with you. A unicycle for the mind.
@therealchreke I mean this one is soluble with a well factored dependency tree and a good build tool, no? Or are you wanting something that lets you edit a root node in an ABI incompatible way and still have a fast build?
@therealchreke I suspect getting the message out with modern build systems is probably possible, and we'll then discover that the test system hasn't got a bloody clue what to do with it...
@therealchreke I feel like the build tool here rightfully says "hey, I built it, over to you now test system" and there's a missing message of "oh btw it was an incremental build and the artifacts that changed were [...]" and then the test system can traverse a different graph to do its work