ludovicianul

Working on a words game: https://hilogame.cc and planning to release 2-3 more that, if they get traction, will live under a single umbrella in the future.

Additionally, I'm building a REST API fuzzer: https://github.com/Endava/cats

I'm always amazed by how much thinking and work the Java leads put in rolling out changes that move the language forward, but make it backward compatible as much as possible.

A combination of visual identity of the game, with the Highs and Lows and helping players visualise with the before and after. I’ve implementarea the letters fading in each position on the keyboard, so that you only see the letters that are valid for that position.

The name of the game is a combination of High and Low. So high would mean right or after the letter and low would mean left or sooner in the alphabet. I’ve added a one time display of the rules before the first game.

I’ve added an archive link in the menu.

Now it allows all 7 letters english words. Apparently 32k words.

Thanks everyone for the feedback. I've implemented several suggestions from the thread, that tweak the user experience: allow all 7 words list as valid words, better contrast, make Go button more visible, as you type letters, the keyboard will fade out letters which are not possible for that position, fixed share + a few more. Archive + easier mode planned for the next weeks.

Yeah. True. Now that you say. Might not be an actual reason. I'll probably load the full dictionary (i have) in the next release.

Planned to be implemented in the near future.

I've tried with 5 letters. After playing some games it was too easy, as it gives you more hints than Wordle on the positioning of the letters. I've also tried 6, but settled on 7 with 5 guesses as it seemed the most balanced.

Higher = right = after, Lower = left = before. Once you play some games, it will become more natural. At least this was the feedback from friends playing the game.

Thanks! Archive is in progress. As for the length of the words, I initially though a 5-6-7/esy-medium-hard, but It seemed very easy to guess the 5 letters once you play some games. I'll reconsider.

I've tried with 5 letters and 6. It seemed too easy to guess though.

This is not something I intentionally design that way. I'll consider switching the position. Thanks!

For now, the plan it's to keep it on the site. But might extend in the future depending if people find it interesting to play regularly.

Thanks for the feedback. I'll try to incorporate as much as possible. For now it was mainly played by family. :D

Thanks for the feedback. I've taken all the 7 letter words from the dictionary and filtered based on different criteria. I'm still thinking what's the easiest automated way to have all valid words, while avoiding offensive, inappropriate ones.

I've built a simple word game with my kids recently. It's fun to add stuff quickly even if they are used only by the family. It has only 5 players now and they have their own group, the family, but open to anyone if interested.

As this is already distilled information, rather than an essay/blog post, my thought was that every part is important. Just like you take notes from a course and use different UI elements to signal how each thing is important.

Yes, exactly. We move cost in another place. When you look holistically at a (complex) project, efficiencies are not that big.

I've written something similar https://blog.dochia.dev/blog/waterfall-returning/ As code is less expensive, specs are the new bottleneck.

I’m working on https://hilogame.cc It’s a word guessing game based on binary search. Only having around 10 users for now, but hope more people will find it fun.

I wouldn’t reduce it to don't use Java/Spring Boot. Rewrites often (not always) look great because they remove years of accumulated complexity, not because the original stack was inherently bad.

Just rewrite it in X doesn't "just work" for complex systems. It ignores risk, and the fact that design usually matters more than language.

With Quarkus (and other new frameworks) you can have webapps with less than 100MiB. Startup times in a couple of miliseconds. CLI apps, with limited number of third party libraries are under 40-50MiBs.

I program in Java for more than 15 years now. I can resonate with people hating the language from it's early days due to the experience with all the enterprisy features and over abstractions. Or confunding Java with the Spring ecosystem. But Java came a long way over the years. It's now what many would call a "modern" language. It's less verbose, has many of the features people find appealing in Scala and Kotlin and it can even compile to native binaries using GraalVM. This made building CLIs in Java feasible. Or lambdas.

Thanks for the feedback. Next on the list :)

It's the second time I see it on HN and read Winamp.

Yes.

I'm using pitest for unit test mutations. And I've actually wrote a tool I'm using for REST API fuzzing. It's called CATS.

Fuzzing as a concept is heavily underused in routine testing. People will usually focus on positive flows and some obvious/typical negative ones. But it's almost impossible to have the time to write exhaustive testing to cover all negative and boundary scenarios. But the good news is, you don't actually have to. There are so many tools now that can almost exhaustively generate tests for you at all levels. The bad news, they are not so widely used.