Yes, I'm New to This
After thirteen years in technology, that may sound like a strange thing to say.
I have worked across companies, teams, technologies, and projects. I have watched frameworks arrive, become essential, and eventually get replaced by something newer. I have built products from scratch, inherited complicated systems, solved problems under pressure, and started over more times than I can remember.
Every unfamiliar problem, changing technology, and new way of building brings me back to the same starting point: curiosity.
That beginner’s mindset is what eventually led to Rorrim.
Thirteen years of starting again
The thing that kept me moving from one project to another was never simply the technology itself. It was the opportunity to learn something new, create something useful, and solve a problem I had not encountered before.
For a long time, every project felt like a new world.
There were unfamiliar systems to understand, difficult constraints to navigate, and better ways of working to discover. But eventually, the patterns began to repeat. The names of the tools changed, but many of the problems remained the same. We rebuilt similar interfaces, repeated similar processes, and delivered similar solutions through slightly different combinations of technology.
Today, more people can turn an idea into something real. They can create a website, prototype an application, write code, produce designs, analyse information, and experiment without needing the same resources that were once required.
This does not mean that building meaningful technology has become effortless.
Code is becoming easier to produce. But understanding the right problem, making thoughtful decisions, designing a useful experience, and building something people can trust still require judgement, experience, imagination, and care.
Why Rorrim exists
I reached a point where I no longer wanted to repeat the same journey inside a different project or organisation.
Rorrim started from that decision.
We are not trying to become another traditional technology company with a large team, complicated hierarchy, and layers of process. We are starting small, with a few people, years of combined experience, and a willingness to rethink how modern software can be created.
For us, that does not mean asking AI to do everything while we step away from the process. It means using AI wherever it can help us think faster, explore further, remove repetitive work, identify possibilities, and amplify the experience we already have.
AI is part of how we research, design, write, build, test, review, and improve. But it does not replace responsibility. The final decisions, the quality of the work, and the results we deliver still belong to us.
The purpose is not to produce more things simply because we can.
It is to spend more time understanding what deserves to be created.
Begin with something that works
We believe good products do not appear fully formed.
The applications and companies we admire today did not begin as the polished versions we now recognise. They started with assumptions, limitations, imperfect decisions, small experiments, and something simple that worked.
That is how we want to approach every project at Rorrim.
A product does not need to begin with every possible feature. It needs to begin with a clear purpose. From there, it can grow through observation, feedback, and deliberate decisions.
Working software is not the end of the process. It is the beginning of learning.
We are beginners by choice
Calling ourselves beginners does not mean ignoring the experience we have earned.
It means refusing to let that experience become a wall around us.
Technology changes too quickly for anyone to remain an expert forever. A person can have years of experience and still encounter a problem tomorrow that requires them to question what they know, study something unfamiliar, and begin from first principles.
It is one of the most valuable abilities a technology team can have.
At Rorrim, we want to remain curious enough to ask basic questions, humble enough to change our minds, and brave enough to explore approaches that may not work on the first attempt.
We are not here because we already know every answer.
We are here because we enjoy finding them.
From the Navy to a pirate ship
There is a line often associated with Steve Jobs:
For years, many of us were part of the Navy.
We worked inside established systems, followed existing processes, delivered against predefined expectations, and learned enormously from the people and organisations around us.
Not because we want to ignore discipline or responsibility, but because we want the freedom to explore. We want to question familiar routes, travel towards difficult problems, and build differently when the usual approach no longer makes sense.
We are also fans of a certain pirate who began his journey with an impossible dream and an almost empty ship.
What makes that story meaningful is not only the destination. It is the journey from one island to another—the challenges faced, the people met, the lessons learned, and the crewmates who choose to join along the way.
That idea feels close to what we are building.
Rorrim is starting with a small crew and a long journey ahead.
We will move from one problem to another. We will enter unfamiliar territories, understand the people living with those problems, and try to leave behind something useful. We will learn from every project, welcome new crewmates, make mistakes, improve our ship, and keep moving.
We are bootstrapping this company from almost nothing.
There will be rough seas, wrong turns, unfinished maps, and things we have to learn the difficult way. But that uncertainty is also what makes the journey worth taking.
Remember the name
We do not know exactly where this journey will lead.
But we know why we started.
So yes, we are new to this.
New to this company. New to this version of the technology world. New to every challenge we have not yet encountered.
And when you face a problem in technology, software, design, or the changing AI landscape, remember the name Rorrim.