<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: S. Kozeki</title>
    <description>The latest articles on DEV Community by S. Kozeki (@skozeki).</description>
    <link>https://dev.to/skozeki</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4247933%2F943169ca-782a-42e3-8df3-a5c1f3c4a71d.png</url>
      <title>DEV Community: S. Kozeki</title>
      <link>https://dev.to/skozeki</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/skozeki"/>
    <language>en</language>
    <item>
      <title>First Impressions with ORACLE</title>
      <dc:creator>S. Kozeki</dc:creator>
      <pubDate>Mon, 16 Nov 2026 14:16:29 +0000</pubDate>
      <link>https://dev.to/skozeki/first-impressions-with-oracle-363i</link>
      <guid>https://dev.to/skozeki/first-impressions-with-oracle-363i</guid>
      <description>&lt;p&gt;This entry records how I encountered and understood a particular situation as a software engineer, within the constraints and context of that time.&lt;/p&gt;

&lt;p&gt;I first encountered the ORACLE database about thirty years ago.&lt;/p&gt;

&lt;p&gt;At the time, I was a junior UNIX C programmer, working on enterprise systems.&lt;/p&gt;

&lt;p&gt;By sheer luck, I was assigned to a large SIer project and given responsibility for one system module.&lt;/p&gt;

&lt;p&gt;I was confident in my programming skills, but databases—ORACLE 7 at the time—and SQL were completely unfamiliar territory.&lt;/p&gt;

&lt;p&gt;With help from a senior engineer from another company on the project, I wrote SQL, executed it, and information came back.&lt;/p&gt;

&lt;p&gt;To me, it felt like a mysterious application that simply returned answers.&lt;/p&gt;

&lt;p&gt;Curious, I tried to study it.&lt;/p&gt;

&lt;p&gt;But what I found were manuals as thick as encyclopedias, filled with arcane terminology—more like spells than explanations.&lt;/p&gt;

&lt;p&gt;It felt like trying to climb a smooth rock wall with no holds.&lt;/p&gt;

&lt;p&gt;That was my first encounter with the ORACLE database.&lt;/p&gt;

&lt;p&gt;Today, technical books are everywhere.&lt;/p&gt;

&lt;p&gt;But back then, even large bookstores carried only a few shelves of computer books tucked away in a corner.&lt;/p&gt;

&lt;p&gt;I still remember how much I relied on the few well-translated Japanese technical classics that existed.&lt;/p&gt;

&lt;p&gt;The internet was barely usable, and if you wanted to improve your technical skills, there were only two paths:&lt;/p&gt;

&lt;p&gt;learn directly from senior engineers, or struggle through technical books on your own.&lt;/p&gt;

&lt;p&gt;I chose the latter—without asking anyone to mentor me (something I think my younger self deserves credit for).&lt;/p&gt;

&lt;p&gt;When I asked,&lt;/p&gt;

&lt;p&gt;"Are there any technical books on Oracle?"&lt;/p&gt;

&lt;p&gt;I wasn't taken to a bookshelf.&lt;/p&gt;

&lt;p&gt;I was taken to a conference room.&lt;/p&gt;

&lt;p&gt;There, on a table in the corner, sat the Oracle manuals.&lt;/p&gt;

&lt;p&gt;They were so thick they didn't even need bookends to stand upright.&lt;/p&gt;

&lt;p&gt;They weren't placed on a shelf simply because they took up too much space.&lt;/p&gt;

&lt;p&gt;At the time, programming itself rarely caused me trouble.&lt;/p&gt;

&lt;p&gt;C was my domain—reliable, familiar, and forgiving.&lt;/p&gt;

&lt;p&gt;Unless deadlines were insane or workloads absurd, programming was fast and enjoyable.&lt;/p&gt;

&lt;p&gt;And then there was Oracle.&lt;/p&gt;

&lt;p&gt;This black box—difficult, restrictive, and impenetrable at the time—stood in front of me.&lt;/p&gt;

&lt;p&gt;Naturally, it ignited the spirit of a young engineer eager to conquer anything difficult.&lt;/p&gt;

&lt;p&gt;The manuals were pristine, the paper high-quality, still carrying the scent of something untouched.&lt;/p&gt;

&lt;p&gt;As I flipped through the pages, the reason quickly became clear.&lt;/p&gt;

&lt;p&gt;This was hard.&lt;/p&gt;

&lt;p&gt;Most Japanese-translated technical books were written with care.&lt;/p&gt;

&lt;p&gt;Oracle's manuals showed no such kindness.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;A perfect irony.&lt;/p&gt;

&lt;p&gt;That was likely why they sat untouched, sleeping quietly in the corner of the conference room.&lt;/p&gt;

&lt;p&gt;I challenged those manuals head-on.&lt;/p&gt;

&lt;p&gt;And eventually, like the senior engineers before me, I stopped opening them altogether.&lt;/p&gt;

&lt;p&gt;And so, my long-standing relationship with Oracle began—&lt;/p&gt;

&lt;p&gt;only to fall silent for a time.&lt;/p&gt;

&lt;p&gt;Did that fire ever really go out?&lt;/p&gt;

&lt;p&gt;Perhaps it simply continued burning, quietly, until today.&lt;/p&gt;

&lt;p&gt;To be continued.&lt;/p&gt;

&lt;h2&gt;
  
  
  Closing note
&lt;/h2&gt;

&lt;p&gt;This entry records how one engineer understood and navigated a particular situation.&lt;/p&gt;

&lt;p&gt;The context matters more than the outcome.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.patreon.com/SKozeki/posts/first-with-148370342" rel="noopener noreferrer"&gt;my Patreon&lt;/a&gt;, where I keep field notes from engineering work in Japan. The full archive is there; new notes appear as they are written.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>oracle</category>
      <category>database</category>
      <category>career</category>
      <category>programming</category>
    </item>
    <item>
      <title>From a Rural Programmer to Tokyo</title>
      <dc:creator>S. Kozeki</dc:creator>
      <pubDate>Mon, 16 Nov 2026 14:16:20 +0000</pubDate>
      <link>https://dev.to/skozeki/from-a-rural-programmer-to-tokyo-2o6p</link>
      <guid>https://dev.to/skozeki/from-a-rural-programmer-to-tokyo-2o6p</guid>
      <description>&lt;h2&gt;
  
  
  Where My Understanding of Engineering Began
&lt;/h2&gt;

&lt;p&gt;I moved to Tokyo when I was twenty-five, intending to start over.&lt;/p&gt;

&lt;p&gt;There were two reasons for that decision.&lt;/p&gt;

&lt;p&gt;One was deeply personal.&lt;/p&gt;

&lt;p&gt;The other was simple and practical: if I was going to work with computers, Tokyo was where the opportunities were.&lt;/p&gt;

&lt;p&gt;At the time, I was employed in a regional city.&lt;/p&gt;

&lt;p&gt;Ironically, much of my actual work already took place in Tokyo through long-term business trips.&lt;/p&gt;

&lt;p&gt;A senior colleague used to say, half joking and half complaining:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Our local office only survives because we come to Tokyo to work."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;It was an uncomfortable truth.&lt;/p&gt;

&lt;p&gt;Tokyo had the largest concentration of projects, the highest budgets, and the most demanding schedules.&lt;/p&gt;

&lt;p&gt;My hometown had fewer opportunities and lower margins.&lt;/p&gt;

&lt;p&gt;What we were doing was, in effect, commuting long distances to access the real center of gravity of the industry.&lt;/p&gt;

&lt;p&gt;The comment carried frustration, but also pride.&lt;/p&gt;

&lt;p&gt;Tokyo was tough, and not everyone wanted to work there.&lt;/p&gt;

&lt;p&gt;There was an unspoken contrast being drawn between the intensity of work in the capital and the slower pace back home.&lt;/p&gt;

&lt;p&gt;After leaving that company, I spent several months uncertain about my next step.&lt;/p&gt;

&lt;p&gt;Eventually, the conclusion became unavoidable.&lt;/p&gt;

&lt;p&gt;If I was going to continue as an engineer—if I was going to take this work seriously—then I needed to do it where the chances were highest.&lt;/p&gt;

&lt;p&gt;That decision brought me to Tokyo.&lt;/p&gt;

&lt;h2&gt;
  
  
  Learning What It Means to Be an Engineer
&lt;/h2&gt;

&lt;p&gt;My first role in Tokyo was at a small, relatively unknown company.&lt;/p&gt;

&lt;p&gt;My very first assignment placed me inside a large project led by a major system integrator.&lt;/p&gt;

&lt;p&gt;The project structure was roughly as follows:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Eight engineers from the lead SIer, responsible for client coordination and team leadership&lt;/li&gt;
&lt;li&gt;More than a dozen engineers from partner companies&lt;/li&gt;
&lt;li&gt;And me—one junior programmer from a small firm&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;At the time, I was in my third year as a programmer.&lt;/p&gt;

&lt;p&gt;In experience and confidence, I was clearly the most junior person in a team of over twenty engineers.&lt;/p&gt;

&lt;p&gt;The office itself was in a high-rise building overlooking the sea in Yokohama&lt;/p&gt;

&lt;p&gt;(not Tokyo, strictly speaking—but let's not dwell on that).&lt;/p&gt;

&lt;p&gt;Despite my position, I was welcomed without reservation.&lt;/p&gt;

&lt;p&gt;Senior engineers on the team—many of them technically from competing companies—treated me as a colleague.&lt;/p&gt;

&lt;p&gt;They answered questions, offered guidance, and intervened when I was struggling.&lt;/p&gt;

&lt;p&gt;For a young engineer, that support was difficult to overstate.&lt;/p&gt;

&lt;p&gt;From a narrow corporate perspective, helping an engineer from another company offers no direct benefit.&lt;/p&gt;

&lt;p&gt;Yet they went beyond that logic.&lt;/p&gt;

&lt;p&gt;They taught and guided me as senior engineers, even though there was no guarantee we would ever work together again.&lt;/p&gt;

&lt;p&gt;Perhaps they never considered it an "investment" at all.&lt;/p&gt;

&lt;p&gt;Looking back, I believe they were simply passing knowledge forward—&lt;/p&gt;

&lt;p&gt;maintaining a continuity of engineering that extends beyond individual projects or employers.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Stayed With Me
&lt;/h2&gt;

&lt;p&gt;I cannot repay those engineers directly.&lt;/p&gt;

&lt;p&gt;What I can do is try to act in the same way toward younger engineers today.&lt;/p&gt;

&lt;p&gt;I believe that is the only meaningful form of repayment available.&lt;/p&gt;

&lt;p&gt;The experience of that project became the foundation of how I understand engineering—not as a job title, but as a responsibility carried across time.&lt;/p&gt;

&lt;p&gt;This blog exists as a return to that starting point.&lt;/p&gt;

&lt;p&gt;By revisiting difficult moments, failures, small successes, and quiet lessons,&lt;/p&gt;

&lt;p&gt;I hope to document the work of engineers who operate without glamour,&lt;/p&gt;

&lt;p&gt;but whose steady efforts contribute to technological progress and, ultimately, to more reliable and humane systems.&lt;/p&gt;

&lt;p&gt;This is a record of that work.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.patreon.com/posts/from-rural-to-148013940" rel="noopener noreferrer"&gt;my Patreon&lt;/a&gt;, where I keep field notes from engineering work in Japan. The full archive is there; new notes appear as they are written.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>career</category>
      <category>japan</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
