IT contract safety for the buyer
Check whether your contract is not a machine built for long-term milking of the client.
Notes from the edge of design, process, and strategic implemetation of technology
TWe write about what happens inside an organization when AI stops being a project.
Newest posts
You ask who will deploy AI for us. The real question: does your company know how it actually works?
From the WordPress era to GPT, we keep running into the same pattern.
Poland is short an estimated 50,000–150,000 ICT specialists. Even if you hire one, your company may not be ready.
For eighteen months you may pay senior invoices while getting a translator. Here is how to shorten that runway and grow architects inside the organisation.
The dead end of “we will just train our own model”
When a narrow ML model is a bullseye, what a language calculator is, why training your own LLM on contracts is a blind alley, and three questions before you spend the budget.
Why roughly 70% of digital transformation programmes miss their stated goals
Technology is only 10% of the BCG recipe. A bad stack choice is vendor lock-in, a migration bill three years out, and a programme that starts life in debt nobody budgeted for.
The migration took eight months. A year later, the headaches were the same.
New stack, new UI — and the same friction on pricing, logistics, and data. A “what you are importing” checklist, four moves before the RFP, and one numeric question before you sign.
Why customers walk away before they pay
Garden furniture at ~€7,000 in the cart, eight calm minutes on site, then exit — no error, no rage click. A €35 case and a €7,000 patio set are two different psychologies — and two different checkouts.
Is your interface locking out users you never see in analytics?
Foundations with autoplay, crowdfunding without a usable right hand — both served disabled communities, neither tested their own site. You are excluding more people than your dashboards suggest.
Technical debt is not a technical problem
Technical debt is a ledger of past trade-offs. When nobody is left to fight fires, the culprit is often a chain of earlier shortcuts — not headcount alone.
DevConE #5 — comfort at work is not a perk; it is a precondition for sound decisions
When fatigue and fragmentation are the norm, even a good process will not carry the day. A short write-up after DevConE #5.
“Retroactive architecture” — a new idea in IT?
AI deployments diverge by department — no inventory, no owner. Retroactive architecture is how you understand how things are before you decide what to change.
HRMS does for people what no one does for your agents
Organizations are building fleets of agents with no governance layer. We introduce a language and inventory model: AIRS — AI Repository of Skills.
Who's Responsible for AI Transformation in Your Company?
Most firms separate deploying a model from owning how people apply it. Until AI is treated as an organizational resource with its own line of accountability — not an “IT project” — the MIT and BCG statistics will stay where they are.
Your n8n Agent Is Already Compromised
The architecture you have built is probably elegant — and, in its current form, an open door. When your n8n agent reads an external source and passes it through memory, you create the exact conditions of the Zombie Agent framework.