24,240 karma · joined February 5, 2013
val name = "mats"
val domain = "matsemann.com"
val email = "${name}@${domain}"
Some projects:https://github.com/Matsemann/
Fpv with oculus rift https://news.ycombinator.com/item?id=7654141
Thesis on using ea to evolve bicycle wheels https://news.ycombinator.com/item?id=10410813
Optical illusions https://news.ycombinator.com/item?id=18307573
One example: setting the agent ablaze on some task, keeping it going, and after a few days of working with the agent you have a feature. But it's not what you were supposed to make. The agent didn't have all the context and made something slightly off, and you never internalized the problem enough to even spot it. If you actually stopped to think a bit on how the feature would have to work to tie it in with everything else, like you would have done before, you would've spotted it.
Second example: something wasn't feasible to do before, due to not being worth the time investment. Like a feature that would need a bigger architectural change to implement. You and the agent take a crack at it, and rewrite huge parts of the code, and it seems to work. But now no one understands how, and it might have been the wrong way to solve it, you just went with it. Before, you would've sat down and discussed and thought about the architectural tradeoffs. Now one decision was just made with little thought.
Also remember that I set up some kind of templating, where I could print the same document multiple times, but it would go down a list of values. So I could print personalized birthday invitations, I felt so cool 8)
Uv hasn't fixed all issues, but made it far less painful.
So stupid interface. No discoverability.
From the position history in the previous post. Good point. Same with bishops "sniping". If a bishop is moved to b2, and remains there or 20 moves, it can be "forgotten" and opponent suddenly has a pin or something underprotected. But if I saw the exact same board, but the previous move was moving the bishop to b2, I would be aware of it. That kind of local thinking is of course something I should learn to not do, but at my level (1700-1800 FIDE) it's how humans play.
without seeing eggballs in a cup due to JWZ's ego. So I say there's no winners with two big egos like these.
https://www.jetbrains.com/lp/devecosystem-2022/
Which matches what I've seen. Every single huge company or government function in Norway have the last years written most of the new code in their applications in kotlin. Basically all java conference talks I've seen has kotlin as the backdrop.
Kotlin's impact in preparing java devs for more functional code has been tremendous.
Mind you, I like that java has taken its time to get the features right. Of course, java has had the advantage of enhancing the jvm while adding the features, where Kotlin had to work around the jvm in some cases (like green threads vs coroutines).
So I prefer javas version of many of the of the more modern things (but do miss Kotlin's lambdas and vast library of extension functions when writing java). But I feel it's wrong to downplay Kotlin's role in modernizing things on the jvm. Heck, if it weren't for kotlin as a temporary stopgap, I'd probably would've left the jvm while the features were still lacking in java.