About Smart Life US

Smart Life US documents the work automation and AI workflows I build while working in the United States. I write under the pen name Sophia, and I only cover methods I actually use.

The material is what I built and ran, not textbook theory — including the attempts that failed and why. Every post aims to leave you with one thing you can copy and run.

Posts with code are pasted in and actually run before they go up. Readers have caught errors in published posts more than once; those posts get fixed, and what I learn from them goes into the next one.

Who writes this

I manage warehouse operations for a site of roughly 1,700,000 sq ft in the US, and most of the automation here came out of that floor. The company runs an enterprise WMS; the tools I build do not replace it. They fill the gap that is left between the enterprise system and the floor — taking appointments, confirming arrivals, assigning docks, and making the current state visible on one screen.

The largest series, a dock appointment system built on Google Sheets, is in daily use — appointments, arrival check-in, dock assignment and status, each part written up as its own article.

AI assists with the coding. What to build, which workflow the floor actually needs, and how to handle exceptions are decisions I make from operating experience. AI-generated code is not published as-is: it gets run against real data and revised first.

What I write about

Spreadsheets & Automation — cutting repetitive work with Google Sheets and Excel: input panels built with Apps Script, aggregations solved with formulas, reports that run themselves. Code is published in full, split by function, with a plain-language note on each line so non-developers can paste and use it.

IT & AI — assigning work to several AI models by role, building a personal AI assistant, and the automation experiments behind it, successes and failures alike.

Life, Insurance & Tax in the US — practical things encountered while working here: filling out a W-4, payroll pitfalls, and the procedures that come up in everyday life.

Education — notes from raising kids in the American school system.

Editorial principles

Every post draws on real experience, but company names, individuals, and contract details are replaced with fictional equivalents or removed. Public places and services are named plainly, because vagueness helps no one. Figures are illustrative examples, checked and stated without exaggeration. Code is published complete — no placeholders, no pseudocode.

What happens before code is published

Code here is not published on a "should work" basis. Before a post goes out, these are checked by machine:

• Syntax and truncation — every code block is actually parsed. Code cut off mid-way never ships.
• Non-existent APIs — every Apps Script method used is checked against what actually exists.
• Things that break at run time — whether a stray letter in a cell turns a total into NaN, whether an if/else actually branches, whether a function the text says "prints to the log" really does.
• Text vs. code — whether the function and setting names written in the prose exist in the code, and whether a condition the text claims to exclude is really excluded.
• The whole series merged — readers end up pasting an entire series into one project. Every part is concatenated and checked for name collisions and errors before publishing.

It can still fail in your environment. Tell me through Contact and I will check and fix the post — that has happened several times already.

How posts get chosen

Rather than filling a quota, I write about what I am actually building and using — when it is worth explaining. Multi-part series form the backbone, with US life, tax and school experiences in between.

Each part of a series builds on the previous one, so following them in order leaves you with a system that actually runs. Use the Posts menu at the top to browse by category or series.

Published posts keep getting fixed. When code turns out to break in a different setup, or an explanation is wrong, I correct that post and check whether the same problem exists in the others.

Contact

For suggestions or inquiries, see the Contact page; for privacy matters, see the Privacy Policy.