Hello, I am Jan

25 YEARS BUILDING SOFTWARE, STILL LOOKING FOR A BETTER WAY TO DO IT

I am an Oracle developer. PL/SQL and APEX mostly, professionally since 2000, with the Oracle database since 9i and APEX since 3.2. I am in Prague and I work remotely, worldwide.

Oracle developer by experience, product engineer by mindset. On a project I end up doing whichever part is missing: the data model, the architecture, the interface, the deployment pipeline, the mentoring. And I want to know why we are building the thing, so I challenge requirements and I focus on delivering value and on what users truly need.

I write a blog, I speak at an Oracle conference most years, and I am an Oracle ACE Pro. I also use AI in my daily workflow, well beyond writing code: analysis, design, testing, documentation, the business side. It lets me deliver things I could not before, faster and better.

How I got here

2000

Started my first business on my 18th birthday. Websites and web applications, PHP and MySQL.

2004 – 2007

First job after school as a PHP programmer. Became development manager, and realised I wanted to be doing Oracle.

2007 – 2012

Landed the Oracle job, learned as much as I could while doing it, and touched APEX for the first time. Wrote my first DevOps tool there too, after a colleague said it could not be done.

2008

Went all in. Logic belongs in the database. Still my position. The two halves joined up in APEX: database engineering and interfaces people actually touch.

2012 – 2022

Went contracting. Banks, insurers, retail. Big regulated systems, where the hard part was rarely the code.

2021

Went fully remote. Started the blog, and the certification habit that has not stopped since.

2022

Started working for US companies, and became an Oracle ACE.

2026

Released ADT.ai, my deployment tool rebuilt from scratch with AI agents in the loop, next to a full-time client.

Today

AI agents in the daily environment, across analysis, code, tests, docs and design. Doing things that were not possible before.

How I work

I take the whole problem

Give me the badly defined business problem. I will analyse it, challenge it, design the data model, build the backend, make the screen usable, automate the delivery and explain it to the users.

I say the difficult thing early

If the design is wrong, the estimate is optimistic or the requirement will not survive contact with users, you hear it in week one.

I work remotely

International teams for years: colleagues across Europe, the USA, Asia and Africa, and nobody has lost anything by it.

I learn on my own time

Certifications, side projects, conference talks and technical writing, at my own expense. Learning is not something I do when an employer schedules a course.

I publish my tools

I have been writing open source for years. The tools I build for myself end up public sooner or later, and they all live on GitHub.

APEX Deployment Tool Core Locks

What I offer

I am most useful where the job needs more than closing tickets

What I doData models, packages, APIs, reports and APEX applications. An empty schema through to a trained user, or dropped into your team on the parts nobody wants to touch: the legacy package with no tests, the query that got slow last quarter, the integration that fails every Tuesday, the system complicated enough that nobody fully remembers how it works.

What you getWorking software, and a database another developer can still read in six months. I care about naming, structure and whether the thing survives the next person, because I have been the next person often enough. My code is on GitHub; read it before you decide.

What I doAnalysis, architecture, product thinking and UI/UX. I ask what the process is for, cut the steps that only exist because the old system needed them, and say the data model is wrong before it gets built rather than eighteen months after. Then I design the interface, because whoever decided where the logic lives should also care what the user has to click.

What you getAn application that is obvious to use, and users who stop working around it. If a team keeps a spreadsheet on the side, that spreadsheet is the real specification and I would rather read it early.

How I designBusiness software does not have to be ugly or confusing. I care about hierarchy, interaction and simplicity, and about a complicated application feeling like a small one. I prototype in front of a user in an afternoon, keep what survives contact with reality, and throw the rest away.

What I doCI/CD for Oracle and APEX teams, unit testing with utPLSQL, performance work, code review, development standards and mentoring. Repetitive manual work bothers me: when people run the same sequence of steps by hand every week, I build the thing that runs it for them.

What you getDeployments that are boring, a test suite that fails before your users do, and a team that is stronger rather than dependent on one senior person. The goal is to leave, not to become the person everything depends on. My own deployment tool, ADT, moves database objects, APEX applications and table data between environments with nobody editing a script by hand.

What I doAgents, structured context, reusable instructions and the tooling built around them. Not prompts pasted into a chat window: a working environment where the agents do the work and people hold the review gates.

What you getExperience rather than opinion, including the parts that did not work. I will tell you which pieces of your process AI should not touch yet, before you have paid for the experiment.

How can I help?

Emailjan@kvetinovi.cz LinkedIn/in/jankvetina

Based inPrague, Czech Republic, EU