Sounds a little scary, right?
But really, I don’t know everything. I’m just the kind of person who finds it hard to leave something alone when I don’t understand it yet.
One small question can send me into hours of reading and exploration. Sometimes the answer leads to three more questions, and before I know it, I’m a long way from where I started.
The funny thing is, I usually enjoy it.
It all starts with “Why?”
As a kid, I loved taking toys apart to see what was inside. Of course, I couldn’t always put them back together.
Growing up didn’t change that habit much. Only the things I wanted to understand became different.
A production process, an Excel spreadsheet, a piece of code—or questions about biology, mathematics, and how AI learns from data.
Once, I spent a lot of time trying to understand why sine and cosine are useful for representing seasonality in a forecasting model.
Writing two lines of code is quick. But I wanted to understand why that approach makes sense, rather than simply knowing that it works.
I think that describes me best: I like understanding how things work.
A somewhat winding path
If you look at my work history, it might seem a little… inconsistent.
I spent many years working in food manufacturing, mainly with coconut products. My work in quality control included roles such as QC Supervisor, QA Specialist, and quality management.
That gave me a chance to learn a great deal about how a factory actually operates: raw materials, production, quality, people, and the small issues that can affect an entire process.
At other points, I also worked in software.
I worked as a Software Tester and a Business Analyst (BA), then took on the role of Product Owner for a small ERP system.
Software gave me another perspective: how to turn real problems into requirements, how to design a system, how to check whether it works correctly, and especially the gap between a feature that runs and a feature that is actually useful to its users.
Looking back, I think moving through different roles and fields has been both a strength and a weakness.
My strength is knowing a fairly wide range of things and being able to look at a problem from different perspectives.
I can understand some of the challenges production teams face, the needs of quality departments, the way software users think, and the technical constraints involved in building a system.
My weakness is that I haven’t followed a particularly steady career path, and my knowledge isn’t equally deep in every area.
There are areas I’ve worked in long enough to understand quite well, and others I’m still learning about. I don’t assume that knowing a broad range of things makes me a substitute for someone who has spent years developing deep expertise in one field.
But there’s something interesting about that.
That seemingly inconsistent combination has become my greatest advantage in my current work: advising and supporting people across digitalization, automation, quality management, and process optimization.
I don’t have to be the best at every individual field. What I try to do is understand the problem clearly enough, see which knowledge and tools can work together, and find an approach that fits the situation in practice.
Sometimes I do it myself. Sometimes I need tools, AI, or help from people who understand the problem better.
To me, what matters is not who wrote every line of code, but whether we understand what we’re building and take responsibility for its outcome.
Not everything I learn is for work
In fact, many of the things I explore have no particular financial purpose.
I like science, especially questions about how the natural world works. I enjoy exploring AI and machine learning. I also like games, and sometimes I want to make one simply because the idea interests me.
Sometimes I think about making simple interactive experiments so children can explore for themselves why a boat floats or how a tornado forms.
Not every idea becomes a finished product. Some things I try briefly before moving on to another question.
I don’t think that is necessarily a waste.
Sometimes, knowledge that seemed unrelated helps me solve a problem years later.
And of course, curiosity has its costs
I can spend too much time on a single question.
I can learn something more complicated than the work actually requires.
I can start a new idea while the previous one is still unfinished.
I’m still learning to balance wanting to understand deeply with knowing when that understanding is enough.
But if I had to choose, I think I would still want to keep that curiosity.
Because I love the feeling of something that made no sense yesterday suddenly becoming clear.
So, what is QuianSpace?
It isn’t a big company. It isn’t a place where I try to prove how good I am, either.
It’s simply a little corner where I keep things I’ve made, ideas I’m trying, and sometimes things I’ve just learned.
You might find a useful tool.
Maybe a small experiment.
Or simply a capybara sitting around playing games.
Either way, thank you for stopping by this little corner.
Make yourself at home.