Proinet

Insights

Insights from practice

Writing about how we work and what our projects taught us.

2026-10-18

BiLSTM with attention on market data. The hard part is an honest experiment, not the network

Over several months we built BiLSTM networks with attention, a reinforcement-learning environment and a point-in-time fundamentals layer. What paid off most were not the architectures but placebos, thresholds fixed in advance and written-up negative results.

2026-10-18

Kubernetes is not just a new way to deploy. It changes your operational habits

Moving applications from servers into containers is the smaller part of the job. The bigger part is dropping old habits — host monitoring, logs in /var/log, the assumption that the application runs as a single instance, and knowing which machine it runs on.

2026-10-14

The customer as a process participant — BPM tasks from an email link

Some process steps can only be completed by the customer — confirm, accept, reply. Here is how to bring the customer into a BPM process without exposing the process engine and without tokens in links.

2026-10-10

AI does not ruin code. In an architect's hands it raises quality

The market consensus says language models flood repositories with lower-quality code. Our experience modernising a large platform is the opposite — on one condition.

2026-09-25

Moving a dozen-plus applications to our own k3s cluster — problems and payoffs

Our third bare-metal Kubernetes cluster — the first in production for a client. Running since November 2023, it serves about 20 applications across four environments. The architecture, seven problems that surprised us, and what we actually gained.

2026-08-20

BPM tasks belong in your CRM, not in a separate panel

BPM engines ship with their own task lists and ready-made UIs. We embedded process tasks in the existing admin panel instead. Here is why — and what the first week after go-live taught us.