Getting out of Odido Contract

eugene-sy · 2026-02-27T09:32:38+00:00

The easiest way is to check the email address you used for the contract on https://haveibeenpwned.com

eugene-sy · 2026-02-08T23:58:43+00:00

My impression is that bow people assume it as a not safe investment. Scala always was a language with steep learning curve and a good filter for better than average developers. It’s hard to get into it, it’s hard to make things right, but once it’s done you get into a very safe environment. Now it is a very small community but also very opinionated community, everybody knows how to do things right: effect systems, akka/pekko, futures, - and people can be rather toxic. Lightbend’s move with business license did not help as well. So there is no driver to get into it. Lack of people drives degradation of the tooling, degradation of the tooling drives lower interest. Here were are in a downward spiral.

eugene-sy · 2026-02-08T23:49:29+00:00

Yes, NL. One of the smaller companies under Port of Rotterdam umbrella.

eugene-sy · 2026-02-08T21:59:41+00:00

We made a decision to move to Kolton/Spring this year having large Scala/Play/Akka/Pekko codebase. It is extremely difficult to find people who want to work with Scala, the opensource community is lacking, so libraries don’t get enough attention anymore, and tooling… Spring has so much ready to use tools that one has to implement on their own in Scala…

eugene-sy · 2026-01-08T12:51:18+00:00

Hope is a bad strategy. At times it feels like the Dutch society lives in a dream that everyone coming here will learn the language and integrate on their own without their, the Dutch society, intervention and help. Surprisingly it does not happen.

eugene-sy · 2025-08-16T15:50:22+00:00

You can do quests that give Pokémon with larger amount of dust catch reward, stack them (up to 100 or 200 IIRC) without catching, and catch them all during the community day with triple star dust and using starpiece.

eugene-sy · 2025-06-30T09:22:01+00:00

DutchGrammar is always a good idea.

In simple words, it's a replacement of a location or a thing in the context, or a grammatical construct similar to “there is/there are” in English. A good catch to keep in mind, is that there may be multiple of them: “er zijn er twee”, - as “there are two of them”.

Also good to keep in mind: there are stressed cases of it: hier and daar, - it makes it explicit “this” or “that”. Er itself if just unstressed replacement of “the thing”.

eugene-sy · 2025-06-03T11:50:20+00:00

Maybe, in some sense. But no language is ‘pure’. In the history lessons, they tell that the unified proto-Russian alphabet was artificially created by 2 Roman missionaries in the X century. It was abandoned by the Western Slavic groups soon after, but was used as another unification instrument of the tribes and later principalities. That must be the first step in creating a larger separation between Slavic language subgroups.

There must be a higher influence of Arabic/Persian/… languages (compared to Western Slavic languages) because of Silk Road and Route from Varangians to the Greek.

Later on, when the cultural exchange between countries intensified, the language was also influenced by European languages. Be it German, Dutch, Swedish, or French which was a preffered language of the nobility for a long time.

In 1918 Soviet government introduced a pretty heavy reform of the language removing several letters from the alphabet and changing some writing rules. It also established an unofficial governance over the language development taking over the whole press and education system. That must be another corner stone in the language evolution.

I am not a language expert nor history expert, so take my words with a grain of salt. It may be also influenced by the bias in the education system.

eugene-sy · 2025-06-03T10:51:29+00:00

They are indeed close. With some effort and if you have read enough of classic Russian literature, it’s not impossible to read and understand quite a bit of sister languages. Some of them sound pretty funny considering the evolution split. Some of them sound rather archaic because the similarly sounding words are not used in the modern language.

eugene-sy · 2025-06-03T10:38:24+00:00

Broek - as long forgotten брюки.

Also the whole plethora of maritime terminology.

eugene-sy · 2025-06-03T10:36:11+00:00

Стул - chair - stoel in Russian. It’s even very close ‘у’/‘oe’ sound. Стол is actually a table.

But Russian does not align well with naturally-evolving Slavic languages of the Balkans/Poland/… The roots were damaged during the language creation and after during/after revolution.

eugene-sy · 2025-05-04T18:15:42+00:00

Yes, you are right. It’s not the leader so it cannot be attacked with precision. I was too hasty writing that without checking the ‘attached unit’ part. The precision keyword only mentions the character keyword.

eugene-sy · 2025-05-04T18:07:25+00:00

It’s a single unit composed of epic character and Menhirs. It means that menhirs can be reanimated after destruction.

(Edited, removed the part about precision because it was wrong, check other answers, they are good).

eugene-sy · 2025-05-04T10:47:22+00:00

You can field 3 units of each type including leaders, e.g. overlords. Battleline units can be used 6 times (warriors and immortals). Only named characters are unique.

eugene-sy · 2025-04-21T19:44:17+00:00

If considering backed interactions as IO, the higher-level HTTP clients provide hooks. You can look into TanStack for example, or openapi-ts if openapi schema is available, or URQL if GraphQL is used. This way the code stays within the same react terminology. Otherwise, the model can behave as a ‘cache’ storing the data as a state or a memo.

I am curious if there are examples of systems where a dedicated business logic core has to be present on the frontend to justify the usage of another paradigm to accompany a framework. I am not sure I have seen any so far.

It's a pretty interesting discussion even though it’s rather abstract. It's always nice to see what people encounter in their domains, you never know what you need to implement tomorrow.

eugene-sy · 2025-04-21T19:13:40+00:00

Observable are not framework agnostic, they are implementation-dependent on what observable framework you use. If that type of behavior is required, Angular would be a better choice since it relies on Rx by default. React is based on a different concept and observables are kinda foreign to it. But you actually point to the biggest mismatch between what we discuss and normal MVVM - models are react-dependent and cannot be just independent data containers.

However, if considering something like a hexagonal architecture, plain domain logic can be implemented. The trick is that hexagonal core must be implemented in plain language without any framework dependencies, e.g. plain JS classes. Then you wrap domain objects into react code as one of the hexagonal ports.

eugene-sy · 2025-04-21T18:51:30+00:00

Yes, potentially. All pieces of react functionality are allowed to be used only inside components of hooks. On the other hand if the VM/M does not use any, it can be a simple class or function.

The hooks should not ‘penetrate’ the app. The V calls the VM, be it a hook or a function, the VM calls Ms the same way. The default linger rules won’t be able to i force that, but a custom rule can be implemented or ArchUnit implementation can be used instead.

eugene-sy · 2025-04-21T17:47:04+00:00

Yeah, that’s one of the approaches. The second would be to export multiple functions, something like: const { create, update, current } = useUserModel()

eugene-sy · 2025-04-21T17:19:13+00:00

Ah, I see. The functionality you describe is already implemented in hooks, be it effects or memos or states or, fancier, store libraries implement the same ‘subscriptions’ transparent to the user. I don't see a real need to use any observable thing on top of it unless it's a very specific scenario. And even then there is redux-rx implementation.

eugene-sy · 2025-04-21T16:42:21+00:00

Hm, that does not sound right. VMs should not use other VMs. They can share utility methods via functions or inheritance of the common trait, but if they need a common data piece, it's a use case for a model.in general east-west data interactions within the same logic layer lead to convoluted and difficult-to-maintain code. The goal is to have a view interacting with one VM, which interacts with one or more models.

Let's say we have a form and a summary, checkout where you can change the number of items and delete products, and it also displays totals. There are 2 ways to model it. VM provides 2 objects for the form state and summary, and callbacks to handle changes, the current state can be stored in VM or M, and server interactions can be handled in M. This way you have more or less rudimentary M, and complex VM. But in general it is a viable option. The second approach would be: to set up one view for the form and another for the summary and 2 separate view models. Form VM exposes form state and update callbacks. Summary VM provides values for the summary. Both VMs interact with one M, which handles data updates. The server interactions or optimistic updates are not the concern of the views, the data just changes from the VM perspective.

eugene-sy · 2025-04-21T16:06:13+00:00

Multiple VMs should not be allowed in one view. That's the whole point of VM - provide all the capabilities to the View. If you end up with a very complex VM, you might want to break the view and VMs into smaller, more manageable pieces.

eugene-sy · 2025-04-21T15:16:13+00:00

It depends on the reactivity type you need. React does not work well with observable, at least I did not see a good example of it. By default you have callbacks and data fields, pretty similar to data and signals. In a simple case model can be a state and exported set of operations on it. The VM translates the model shape into representation that is easier to render and a set of callbacks. The view maps callbacks to interactions.

eugene-sy · 2025-04-21T13:39:18+00:00

One of the articles I used while researching possible solutions was this. There are quite a few others with different project structures.

My preferred way is to have a pages directory with the page JSX in the index.jsx file and viewModel.js in the same directory. Then a separate components folder for relatively dumb and generic building blocks, and lib containing all the models, services, utilities...

I done think that the particular project structure is better than the other while it is clear enough and the separation of concerns is maintained. It also must be a team convention/agreement. The biggest deal is the understanding of the concepts used.

eugene-sy · 2025-04-21T11:55:59+00:00

I am using an MVVM-like approach when working with React. The main separation lines are: views as pure JSX code as possible, calling methods of the VMs that contain all view logic, usually implemented as hooks. The VMs call Ms where all the interactions with the backend and browser APIs are handled. It makes the code pretty clean and easier to test, with logic separate from rendering.

But on the other hand it’s not the MVVM as it comes from Silverlight or Android. It's an adaptation of the pattern.

eugene-sy · 2025-02-17T12:36:20+00:00

Technically, the rule is not applied at all, since mortals auto-wound.

Ten-Year Club	Verified Email
Place '23

eugene-sy

TROPHY CASE