Give me a problem.
It can be technical. It can be weird. The route may change. The answer usually doesn't.
No roadmap. No business case. Just things I wanted to build, break, test and make work. And I still haven't found much use for the word "NO".
Plan A usually works. When it doesn't, there are 25 more letters in the alphabet. And SQL.
Four tiny experiments about problems, solutions, enterprise complexity and one suspiciously unavailable word.
It can be technical. It can be weird. The route may change. The answer usually doesn't.
There are technically two options. One of them is considerably more cooperative.
The path is rarely elegant. That's fine. Working beats elegant.
Move carefully. A five-minute task is only a few approvals away from becoming a programme.
Six questions. Zero scientific value. Potentially dangerous enterprise conclusions.
Skip the traditional bio. Ask the console what I actually do.
A tiny visual demo of how I connect product UI with enterprise systems.
/api/integration/designPortfolio simulation — the point is the architecture, separation of concerns and clear data contract.
{
"source": "Business Application",
"api": "Integration Layer",
"target": "SAP / Oracle / Enterprise Platform",
"principles": ["security", "auditability", "resilience"],
"result": "designed_for_scale"
}Choose a difficulty, match all pairs and try to reach the leaderboard.
Moves: 0 | Time: 0s
| Player | Score | Time | Date |
|---|---|---|---|
| Vuk Nikolic | 96 | 1s | 2025-11-30 17:36:33 |
| Vuk Jankovic | 96 | 3s | 2025-12-01 17:36:55 |
| T | 96 | 3s | 2025-12-04 23:34:05 |
| Miroslav | 96 | 4s | 2025-11-30 09:40:07 |
| pokemon | 95 | 6s | 2026-03-17 20:06:12 |
| 94 | 6s | 2026-03-17 20:06:37 | |
| Tinkić | 94 | 6s | 2026-08-27 17:54:00 |
| 94 | 8s | 2026-03-19 10:21:19 | |
| 94 | 8s | 2025-11-30 09:24:13 | |
| test2 | 94 | 9s | 2026-08-17 17:24:17 |
Good ideas, strange bugs, useful experiments and technology conversations are always welcome.