That diagram is rather bad at what it tries to do. Those are also historically and phonetically the same:
Λ Л
Δ Д
Κ К
The first Cyrillic alphabet was using the https://en.wikipedia.org/wiki/Glagolitic_script , curiously created by Saint Cyril, but then people found it was too difficult, so someone in the Preslav Literary School in the First Bulgarian Empire mashed up Glagolitic, Greek and Latin to create the new Cyrillic (probably naming it as a sorry to Cyril for butchering his nice unique alphabet).
The diagram says that (Cyrillic ∩ Greek) - (Cyrillic ∩ Latin) is 3 letters, П Ф Г but as the sibling comment says, Λ/Л, Δ/Д and Κ/К are similar enough. That only leaves you with Θ/theta (th as in thin), Σ/sigma (s as in soft), Ξ/xi (x as in fox), Ψ/psi (ps as in lapse), and Ω/omega (o as in ore.) A lot of those are close enough that you can sort of guess, if you know the English names for the letters!
Many Cyrillic letters are Latin-looking, but actually have direct Greek analogues due to the history of the writing system. If you don't know Greek letters, you'd have a hard time guessing р made a 'r' sound. If you do, it's a natural guess.
I noticed it was added to a couple of others that I didn't submit to (goldles.com and dles.aukspot.com) I'm not sure if there are others I should be aware of.
I’m not totally sure! Marketing is not my strong suit.
I think my biggest advantages are:
- It’s sticky. A good percentage of players keep playing once they start
- Organic sharing. Lots of people have told me they shared it with friends and family. (I also built a “share” feature)
The pattern so far has been:
- I share it or someone else shares it somewhere.
- There’s a big spike of people trying it out.
- I get some new players.
- The player count stays roughly steady until it gets shared somewhere else that gains traction.
It was featured by Thinky Games. Sharing here got people interested. Someone shared it on Metafilter and that got a lot of views. Other folks have shared it on other sites that have led to smaller bumps.
Somehow I feel like this article was very unclear? The way it's written, the way it tells its story, I'm really not sure what happened. I wish there was just a link to the saas in question.
Like maybe it's that I just woke up, but all I really got out of this was that a vibe-coded app resulted in a company being downsized. But that's in the title. Any specifics beyond that? I really couldn't say despite having read the whole article.
They said that the team they work with is being replaced by a vibe coded SaaS product and that when they look at the product it only looks like it could replace the actual engineers from a very surface level.
> It's like someone took some screenshots of a competitor
This line stood out to me. I think it's something any of us who've tried to end to end vibe code something have experienced. The result is pretty (sometimes) but not functional.
> At the shallowest depth, I can see how a CEO got bamboozled. The happiest path is implemented. The second happiest path is rough. The third happiest path is unhinged.
If I'm understanding them, they're saying on the surface (the "happiest path") is correct, but everything underneath isn't. That the stuff underneath is harder. So only the easiest part was shown and the leadership was happy to move forward because they wanted to believe. It promised they could reduce costs by laying of expensive developers but the decision was unjustified considering the product didn't work as advertised.
not sure, but i'm getting the sense that they're annoyed that someone is expressing themself on their own personal blog and not being Professional enough
A part of me starts liking this kind of style because it feels more human... I'd rather wanna be bothered by some cringy writing than by those em dashes...
I had the same difficulty. i.e. what was the issue that caused a headcount reduction from a 1000 to 10 or less? It’s possible the organization had larger issues than generated code but again, difficult to draw conclusions without details.
It sounds like their employer is on the outs and in a bone-headed move to save on cost, is replacing the author's team and tech with some piece of crap vibe coded SaaS product.
They are expressing their (and their team's) bitterness over losing their jobs to something of such obvious poor quality.
I can empathize with this view. Seems like people's standards are a lot lower than they let on, and slop-ware is apparently A-OK at the right price point. Sad. But as the author points out, there will be legal consequences..
What is happening to this person sucks for sure. But one thing I have learned in this industry is the thing being replaced is always better than the thing replacing it when you talk to the team who built and run the thing being replaced.
There is enough to read between the lines. Dilbert manager has bought into a barely competent app (that they think replaces humans) in a panic because costs. They’ll learn more lessons over the next year, if they survive. The author might be a bit emotionally charged right now and is writing between some lines as they help migrate. Once they have some emotional distance they might write the fully clear article you’d like.
A question I asked myself when I first created it. Some people will be annoyed by that, some won't. It's fine if you're the former! but the fact is, without an input field, there's no way to verify that your solution is accepted and mark the puzzle as completed.
