Dock
A technology company from Gdańsk, Poland. Websites, online stores, applications, maintenance, digital accessibility, plus automation and AI for growing businesses.
- Type
- Technology company
- Period
- since 2024
- Product website
- dock.eu
My role
My role
My contribution
As CTO, I’m responsible for technical direction: architecture, infrastructure, quality standards and tool choices. I take part in estimates and client conversations when a technical decision affects scope or cost.
The team’s work
Projects are delivered by a team of specialists: developers, testers, and marketing and accessibility specialists. My role is decisions and standards, not building every project myself.
Decision line
One shared infrastructure standard for client projects instead of a separate setup for every deployment.
- Context
Many projects, different histories
Client projects were built at different times and in different ways. Each deployment required its own know-how, and maintenance depended on who remembered the details.
- Choice
A shared deployment standard
Containers, one way to build and deploy, a shared reverse proxy and monitoring. A new project starts from a ready-made template.
- Trade-off
Less freedom in any single project
Some projects had to adapt to the standard, even though on their own they could have been configured more simply.
- Takeaway
Maintenance no longer depends on one person’s memory
Deployment knowledge lives in templates and documentation, not in people’s heads. Onboarding a new team member is easier.
Dock
Dock
For me, Dock is above all a lesson in how technical decisions translate into business. Every architectural choice has a cost: in team hours, in maintenance and in conversations with clients.
The company website lists the full range of services: websites and online stores, maintenance, digital accessibility, performance marketing, and automation and AI. Here I write about what you can’t see from the outside: how we make technology decisions and why.
What teaches me the most is the tension between what’s technically best and what a client can maintain and pay for. A good decision is often the one that’s good enough and can be explained.