Introduction
Hello from Japan! 🇯🇵
I am an active truck driver in Japan self-studying Python, leveraging my logistics domain knowledge to become a Web Engineer.
(English is my second language, but I'm excited to share my journey with developers around the world!)
This is a record at 20 days into my learning journey (81 cumulative hours), starting May 12, 2026. (As of late May)
In this article, I summarize the background and decision-making criteria for halting my initially planned "In-Vehicle Local Server Operations Management System" and pivoting toward Web development.
Check out my GitHub here👈️
(🇯🇵Note: Most repository documentation and commits are currently in Japanese.🏯)
1. Initial Concept: Considering In-Vehicle Local Infrastructure
For independent transport operators, I considered using an affordable secondhand PC (running Lubuntu) as an in-vehicle server to store and manage daily reports and operational data offline.
- Goal: Build a low-cost operations management infrastructure while eliminating monthly telecommunication subscription fees.
- Tech Stack / Architecture: Power inverter, local network setup using a Lubuntu PC, and automated Excel generation for daily logs.
2. Challenges Leading to the Pivot
As I progressed with the design, I determined that continuing was infeasible due to the following technical and operational challenges:
① Hardware Maintenance Risks
If running multiple secondhand PCs, it would be difficult for an individual to permanently cover failure risks caused by aging hardware, making it tough to guarantee infrastructure reliability.
② Divergence from Learning Goals
This project primarily revolved around Linux infrastructure setup and network configuration. I judged that this had little direct relevance to my primary goal: acquiring skills in "Web Application Development (Python/Flask, Ruby on Rails)".
③ Insufficient Market Need Analysis
The system architecture was tailored solely to a specific operational environment, failing to adequately account for broader market needs or the operational complexities of other logistics businesses.
3. Future Roadmap
Removing emotional attachment, I prioritize the shortest path toward achieving my primary goal.
- Mastering Deployment with Flask: Experience the Web app publishing process and understand fundamental architecture.
- Transitioning to Ruby on Rails: Learn a high-demand Web framework used in production to begin building my portfolio.
Going forward, I will focus on building a track record through Web development projects. My daily learning progress and development history are available on GitHub below:
