This entry records how I encountered and understood a particular situation as a software engineer, within the constraints and context of that time.
I first encountered the ORACLE database about thirty years ago.
At the time, I was a junior UNIX C programmer, working on enterprise systems.
By sheer luck, I was assigned to a large SIer project and given responsibility for one system module.
I was confident in my programming skills, but databases—ORACLE 7 at the time—and SQL were completely unfamiliar territory.
With help from a senior engineer from another company on the project, I wrote SQL, executed it, and information came back.
To me, it felt like a mysterious application that simply returned answers.
Curious, I tried to study it.
But what I found were manuals as thick as encyclopedias, filled with arcane terminology—more like spells than explanations.
It felt like trying to climb a smooth rock wall with no holds.
That was my first encounter with the ORACLE database.
Today, technical books are everywhere.
But back then, even large bookstores carried only a few shelves of computer books tucked away in a corner.
I still remember how much I relied on the few well-translated Japanese technical classics that existed.
The internet was barely usable, and if you wanted to improve your technical skills, there were only two paths:
learn directly from senior engineers, or struggle through technical books on your own.
I chose the latter—without asking anyone to mentor me (something I think my younger self deserves credit for).
When I asked,
"Are there any technical books on Oracle?"
I wasn't taken to a bookshelf.
I was taken to a conference room.
There, on a table in the corner, sat the Oracle manuals.
They were so thick they didn't even need bookends to stand upright.
They weren't placed on a shelf simply because they took up too much space.
At the time, programming itself rarely caused me trouble.
C was my domain—reliable, familiar, and forgiving.
Unless deadlines were insane or workloads absurd, programming was fast and enjoyable.
And then there was Oracle.
This black box—difficult, restrictive, and impenetrable at the time—stood in front of me.
Naturally, it ignited the spirit of a young engineer eager to conquer anything difficult.
The manuals were pristine, the paper high-quality, still carrying the scent of something untouched.
As I flipped through the pages, the reason quickly became clear.
This was hard.
Most Japanese-translated technical books were written with care.
Oracle's manuals showed no such kindness.
At the time I didn't understand it, but Oracle's unique terminology—often explained nowhere—made the manuals nearly unreadable unless you already knew Oracle.
A perfect irony.
That was likely why they sat untouched, sleeping quietly in the corner of the conference room.
I challenged those manuals head-on.
And eventually, like the senior engineers before me, I stopped opening them altogether.
And so, my long-standing relationship with Oracle began—
only to fall silent for a time.
Did that fire ever really go out?
Perhaps it simply continued burning, quietly, until today.
To be continued.
Closing note
This entry records how one engineer understood and navigated a particular situation.
The context matters more than the outcome.
Originally published on my Patreon, where I keep field notes from engineering work in Japan. The full archive is there; new notes appear as they are written.
Top comments (0)