OMS Wait Nodes and Timeouts in SAP Commerce | November 09 2026, 05:38

Published a new article on Hybrismart from the series about OMS (Order Mgmt). Along the way, I built a full OMS emulator where you can test all sorts of “what happens if” scenarios – (for example, what will change if we remove product reservation), and there’s already a lot accumulated (for future articles). This article is about implementing wait steps in the order workflow and their specifics (quite SAP Commerce-specific)

<a href="https://hybrismart.com/2026/11/03/oms-wait-nodes-timeouts-rus/

“>https://hybrismart.com/2026/11/03/oms-wait-nodes-timeouts-rus/

https://hybrismart.com/2026/11/03/oms-wait-nodes-timeouts-rus/

Adaptive Chord Learning | November 03 2026, 04:00

Finished the program, now it teaches adaptively, gradually introducing new chords and reducing the frequency of those I make fewer mistakes with. It can do the same with notes, but I’m less interested in notes, since I almost never make mistakes there. Chords are harder and more interesting.

Vibe-Coding an Ear Trainer in 10 Minutes | November 03 2026, 03:21

Check out this thing I vibe-coded in 10 minutes—an ear trainer. The next step is repeating a melody, then repeating it in the specified key (starting from a different note). What a time to be alive! Many ideas are quicker to build than to look for something ready-made 😉

In the next post—an adaptive chord trainer

Exploring Undocumented Features of FlexibleSearch on SAP Commerce Cloud | October 14 2026, 12:50

Published a new article on Hybrismart about undocumented features of FlexibleSearch (SAP Commerce Cloud / Hybris). Relevant if you work with this platform in any way. If not — feel free to send it to those who do 🙂

I now publish articles in three languages – RU, ENG, UKR. Of course, the Russian and Ukrainian are automatic translations from English. But many prefer reading in their native language.

https://hybrismart.com/2026/10/13/flexiblesearch-2026-rus/

https://hybrismart.com/2026/10/13/flexiblesearch-2026-rus/

Mastering Project Presales with Claude Code: A Customized Approach | September 29 2026, 14:10

Lately, I’ve become proficient at creating project resource plans for presales using Claude Code. It turns out very cool. That is, you create an interactive model with sliders that shows the final cost of the project for the specified team and specified flexibility (more or fewer roles, some stages have a larger or smaller buffer). The main thing is that such a model is very specific to a particular project and generally useless as a template for the next, but the principle of building models is the same. In the end, you adjust the sliders to what looks believable and satisfies the level of risk, and you see the sum, and then you generate artifacts for the client, which after manual refinement (sometimes major) are ready to be shown to the client.

Revamping Smartfolio.me: A New Era of Personal Knowledge Workspaces | September 26 2026, 12:51

I’ve updated my smartfolio.me (In short, it’s a personal workspace for knowledge, built around pages that contain other pages, where a child page can reveal a selected snippet in the context of the parent. You write in a full-featured editor—text, formulas, images, embedded PDFs with annotations, saved web pages—and instead of organizing documents into folders, you insert one page inside another, or create a child page as an explanation through LLM of the selected snippet in the context of the parent document. Incoming items accept material from outside, search finds what is left unlinked, and several LLM plugins can parse raw transcription into connected sections, assemble a whole subtree into one document, translate a page without touching its formulas and layout.)

Previously, Smartfolio was a SaaS and stored documents only in Turso—SQLite as a service. Now, in addition to local SQLite and Turso, there are three new storage options: a folder on the disk (for local installation), a GitHub repository, and a folder in Google Drive.

Synchronization has been introduced, and it’s three-way: what A and B have and what they last agreed upon. As a result, “they differ” becomes “this has changed”—without referring to clocks owned by someone else’s machine. Storage pairs are by default bidirectional (a unidirectional mode exists for backups, and the interface writes “only from X to Y”, not drawing an arrow that might be interpreted in reverse); they can be restricted to a page and everything it reaches—including assets identified directly in the content. Conflicts preserve both sides in the form of a conflict copy, rather than merging or discarding them. Pairs are remembered in both storages, so a setup configured on a laptop also appears on the next machine, and the record of consensus lives in exactly one place—if each machine had its own, a regular edit from one side would turn into a conflict.

GitHub and Drive connect easily via oauth; afterwards, the profile shows repositories that the token may write to, or folders in Drive created by this app—selecting an existing one uses it, rather than creating a second one alongside. This is precisely how a second machine connects to already existing notes.

Desktop versions are now available on Electron—for macOS, Windows, and Linux. Smartfolio also works from a mobile browser.

Demo (somewhat outdated, without synchronization) – https://www.youtube.com/watch?v=nWSzEsgciaY

For now, everything is by invitation only—both the service and the source code.

<a href="https://www.youtube.com/watch?v=nWSzEsgciaY

“>

Nostalgic Business: Selling Websites on CDs in the Early 2000s | August 18 2026, 16:31

In the early 2000s, I had a “business” selling the internet at retail – on CDs. I would make agreements with content providers – websites like algolist, openbsd, and cooking recipes to place a “buy this site on CD” banner on every page, and in return I invested time in creating a static version with search functionality and recording it onto discs. Links from the pages led to .nadiske.ru, where there was a large order button and upsells from other projects, related and not. A percentage from each disc went to the content owner. Delivery was done by cash on delivery through the Russian Post (meaning, I sent the discs without prior payment), and I collected the money at the post office. The site effectively had two pages – a product list with checkboxes and an order form. However, there were as many sub-sites as there were partners – on each of them, the main product was listed first, and the rest were upsells. The idea was that since we’re already ordering, let’s get something else too”.

So, several interesting problems arose back then. How to match the money received with the orders posted? For each order, I dynamically formed a price – adding pennies so the price was unique. For the end customer, it made no difference whether they agreed to a price of 150 rubles or 150 rubles and 12 kopecks, but for me, it was convenient for matching. Together with the date, it was quite reliable.

The second problem was where to manage orders with statuses and the like. In the end, I chose Microsoft Access. It pulled XML with new orders from the website. I developed the whole system on Access in a couple of hours. It was ideal. By the way, has Access died out yet?

Interestingly, the top sellers were discs that I had produced just to expand the selection – Unixes and Linux. Understandably, there weren’t any links from partner websites to these, but they were bought as add-ons, and ultimately they topped the sales and were the easiest and cheapest to produce.

Also, I developed a search engine for the CD to search through this content. I don’t remember how, but back then it was possible to embed executable code in the browser that opened index.html from the disc. Either there were ASP inserts and DLLs, or something of that nature.

I closed the project when it became clear that decent internet would eventually reach the regions, and the demand for discs would someday wane. Plus, everything was heading in that direction. Additionally, the disks required updates, and it was a pity to invest more effort and time, especially considering the first point.

Challenging the Limits of AI with ARC-AGI-3 Tests | August 17 2026, 04:51

Today I came across ARC-AGI-3 tests for AI models. That is, if you think that AI can do anything for you, consider that you have already earned a large part of the $850,000 prize fund – just submit your beautiful code, and let it be the best. But it doesn’t work that way. Humans handle 100% of tasks, while programs have not yet surpassed the 2.5-3% mark. What are those tasks?

The program is given not a textual task but a mini-game. There are no instructions or descriptions of the rules. At each step, the program receives a “frame” — a JSON object with the current state of the field. It is a grid of up to 64×64 cells, where the cells are encoded with numbers from 0 to 15 (representing different colors or types of blocks). The agent has a standardized interface (actions 1–7), including basic steps and the ability to specify specific coordinates (X, Y). But AI does not know beforehand what these actions do! In one task “Action 1” might shift a block to the right, in another repaint it, in a third turn on gravity. To understand the logic, AI must actively “poke with a stick” at the environment. It performs an experimental action, the environment reacts and returns a new frame. The agent must analyze the changes, update its theory about the physics of this particular world, and make the next deliberate step. The game can end with the status WIN, GAME_OVER, or continue further.

Again – humans score 100%, machines – 2-3%. You can try it at the ARC PRIZE website, there are sample tasks available.

Exploring Unpublished Social Sharing Previews: Solutions and Simulations | August 14 2026, 14:49

It’s interesting that there seem to be no tools available to check how Social Sharing Previews for Facebook, LinkedIn, Twitter work for a site that is not yet public. I can think of two solutions for this: simulating social network behavior and creating a page with stripped content but correct headers, which is opened to the public for a minute, then preview generation is performed through the actual tools of FB, LI, Twitter, conclusions are drawn on what to adjust, and the page disappears. The simulation could also be done, seems not too complicated.

Automating Disk Analysis with AI: Towards Smarter File Management | July 23 2026, 12:24

I contemplate creating a small program that would scan the disk and analyze all folders and files, peering inside the files only if necessary – primarily focusing on their names, and using LLM to tag and briefly describe entire hierarchies, and more importantly, classify, and save the size of files in the hierarchy. It’s assumed that such a tool runs in the evening and the results are discovered in the morning, because naturally all this is slow. But in the morning, I receive a detailed, structured, relatively small comprehensive report on what needs to be backed up, what can probably be deleted (for instance, a clone of some repository from the public domain), sorted by impact (freeing up space, less clutter, etc.).

Of course, throwing tens of thousands of files at an LLM – is an unreasonable waste of tokens. An agency scheme is assumed – the system takes the top level, makes assumptions, checks them, looks at the time files were modified, checks if there have been changes since the creation of the entire hierarchy and asks the LLM very compactly, setting a percentage of confidence in the judgement about the necessity/unnecessity of any given folder. Then the user can manually check something, or ask to take a closer look at something else.

I wonder, would such a thing be useful to anyone else?