Notes on data, AI, IT
and security
No marketing fog. The way I think about real problems with founders and managers.
Excel as shadow IT: banning it is pointless, rethinking the process is not
Spreadsheets live where corporate systems are too slow or too rigid. Here is what to do about that.
Data lineage: where the number in the report came from, and who owns it
Tracing metrics back to their source is not a technical nicety - it is the foundation of trust in analytics.
Text analytics without a silver bullet: where the real value is in reviews and tickets
Why processing customer text starts not with understanding language, but with routing and classifying reasons.
Voice versus search: what Siri teaches corporate knowledge bases
Users want an answer, not navigation through menus. Why voice interfaces are changing the requirements for internal knowledge systems.
Telemetry architecture: collecting sensor data so it is still useful in three years
Why sensor data needs to be designed as a long-term asset, not launched as a one-off pilot that cannot be reused later.
API-first inside the company: why integrations should not happen by word of mouth
How to agree on system interfaces before integration chaos becomes the norm, and why this matters for a growing company.
Security metrics for executives: why virus counts are a bad KPI
How to talk about information security in terms of risk and resilience, rather than technical counters that tell a manager nothing meaningful.
Personal data: map the flows before adding controls
Why protecting personal data starts not with encryption or policies, but with understanding what data the company actually collects and why.
ETL as a production line: where queues, stoppages, and grey operations appear
Translating data integration into the language of manufacturing - so a manager can see bottlenecks in process logic, not in code.
Machine vision for quality control: where it can work today
Not magic and not the future - specific tasks on a production line with clear defect economics and measurable outcomes.
Patching industrial control systems is hard, but no update regime is worse
How to bring operations engineers and security teams to a shared testing and maintenance scheme - without illusions and without paralysis.
Failure as a management scenario: who decides in the first 30 minutes
On why a technical incident is not only an engineering problem, and how to define roles, escalation paths, and a single source of truth before something breaks.