Welcome to the Fancy Pixel blog
We're opening the doors to our workshop: what we'll publish here, why we do it, and how we want to talk about it.
For more than ten years we’ve worked side by side with industrial companies, tech startups and research teams, building software that often nobody sees but keeps machines, processes and products running. From Ferrara, in northern Italy, we’ve shipped projects for IMA, Carpigiani, Electrolux and Meta — from remote control of production lines to VR interfaces for haptic feedback.
Over time we’ve learned that the value isn’t in the code itself, but in the choices that come before: understanding a complex domain, picking the right tech for the context, avoiding over-engineering and — most importantly — staying honest about what actually works and what doesn’t.
Why a blog
A good chunk of what we do doesn’t fit a polished case study on our website. There are architectural decisions, failed experiments, libraries we picked for the wrong reason and then fixed mid-flight. All of that is valuable material for someone facing similar problems, but it stays in Confluence pages and internal chats.
This blog is an attempt to open a small slice of that knowledge. It won’t be a magazine of trends, nor a marketing megaphone: we want every post to carry a concrete, transferable idea — and admit its own limits.
What we’ll write about
Three threads:
- Industrial & IoT: real-time monitoring, field protocols (OPC UA, MQTT, MQTT-SN), MES/ERP integration, edge computing.
- Web & Mobile: modern frontend architectures, native iOS/Android, accessibility, design systems.
- R&D & Innovation: prototypes, custom hardware, applied machine learning, experiments that might one day turn into patents.
Sometimes there’ll be a less technical reflection — on team culture, client relationships, how we handle complexity. We promise we’ll never write “the future of work”.
How we’ll write
Three simple rules, starting today:
- No AI-generated posts without a human putting their face on it. We can use models as a support tool, but the byline is always a team member.
- When something didn’t work, we say so. Post-mortems are more useful than success stories.
- Runnable code, not pseudo-code. Every example is pulled from real projects or public repos you can clone.
Talk to you soon. If you want to suggest a topic, drop us a line at rgb@fancypixel.it.