Using encapsulated development to code on my phone
The article discusses the author's experience of using encapsulated development to code on their phone while managing family and work commitments. By ensuring that each change is stable, verified, and stateless, the author has been able to maintain productivity despite the limitations of mobile coding. The author reflects on the challenges of planning and design when working solely on a phone, noting that while some measures are beneficial, they also hinder the exploration of complex features.
- ▪The author has averaged two commits per day to a side project while primarily coding on their phone.
- ▪Encapsulated development allows for stable, verified, and stateless changes to the codebase.
- ▪The author faced challenges with planning and design due to the limitations of mobile coding.
Opening excerpt (first ~120 words) tap to expand
I’m lucky enough to have a wife, two young children and a job as an AI Engineer at Notion. I’m also lucky enough to have a side project. Some weeks, I’ll get half an hour on my laptop to work on this side project. Most weeks, I won’t. Yet, I’ve averaged two commits to the project per day for the last three months. How? By building on my phone. But, really, by making it possible to build on my phone. The broad approach: encapsulated development. Each prompt leaves the repo in a known, stable, verified, stateless condition that permits the next change. Known My mental model of the project must be functional enough that I can make future changes. This doesn’t mean I understand everything. I may not know the architecture of some parts of the system.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Maryrosecook.
Discussion
0 commentsMore from Maryrosecook
