In the summer of 2025, from June to August.
I spent a time when I vividly felt the possibility of developing with AI
by completing five Rails-based services almost consecutively.
The development at that time was about speed.
It was a pace of quickly designing, quickly creating, and quickly deploying.
AI added speed like a helper,
and I solidified the structure and piled code on top of it.
However, after September, with multiple projects and operational tasks overlapping,
I had to pause Byb Coding for a while, and that time had already become four months.
December.
As I opened the code again after a long time,
and resumed development with the new Claude Code Opus model,
I realized.
That a new era of development, unexplainable by past senses,
had already arrived.
The period of June to August was the era of possibilities for Byb Coding
The AI at that time was quite impressive,
but compared to the current Opus, it feels like it skipped a step.
I had to organize repetitive files myself,
and if the design wavered, the code wavered as well,
and I had to write CLAUDE.md in great detail.
The AI at that time was
evolving into something beyond a tool,
but it was still close to a stage that absolutely relied on the developer's intentions and structure.
Looking back, that period was
when we were first experimenting with
what possibilities AI-based development methods could open up.
The four-month gap was not a break but a reorganization
During the time I set the code aside for a moment,
AI evolved, the technological environment changed,
and I found myself looking at the development flow with a broader perspective.
Those four months were not a time of falling behind,
but a process of rearranging thoughts.
What is important for developers
is not the time they hold onto,
but the changes they see when they come back.
As the perspective deepens, the evolution of tools becomes clearer.
In December, resuming development with the Opus model
When I resumed Byb Coding,
there was a significant change immediately felt.
AI's way of reading the code,
its ability to understand the entire structure of Rails,
and even its comprehension to fill in missing designs
were all higher than before.
If Byb Coding from June to August
felt like "developing with AI,"
Byb Coding in December
was closer to "feeling like I've become a better developer thanks to AI."
This difference is not just a simple performance improvement,
but a signal that the development method itself has changed.
CLAUDE.md is no longer a design document
Previously, CLAUDE.md
had to be written meticulously by hand,
including feature definitions, DB structure, business rules, and screen flows.
But now that I have returned with Opus,
CLAUDE.md is not a finished document,
but more like "a brief guide pointing the direction."
AI reads the entire flow of the project
and fills in the empty structures on its own.
It deduces even the parts that users don't specify
and reorganizes them into consistent code.
It is a moment of transitioning
from document-centric development to conversation-centric development.
Rails remains the same, but
the developer's perspective has completely changed
The role of the developer does not diminish
just because AI writes the code.
On the contrary, it becomes clearer.
I started thinking more structurally,
modeling became clearer,
prototyping speed increased.
The flow between UI and backend continued smoothly.
AI is not just writing the code,
but pushing developers into deeper thinking.
Programming is not disappearing.
It is getting closer to its essence.
Conclusion of Night Coding
The four-month gap did not set me back.
Instead, it became a time to prepare for a new era.
Byb Coding from June to August
showed the potential of AI development.
Byb Coding in December
is an era of finely honing the sense of actually creating and refining services.
AI has quietly moved on to the next generation,
and as soon as I returned, I could accurately feel that change.
And now,
I want to create more than before.
As a Rails developer,
as an entrepreneur in the AI era,
as a person who continues to experiment under the name Night Coding.
This change is just the beginning.
We have just stepped into the development method of the next generation.