About

My day job is helping small and mid-sized companies that do not have an IT team audit their processes, choose systems, wire them together, and then keep them running afterwards. That spans ERP, internal management systems, NAS and file permissions, network segmentation, and getting AI applications into daily use.

"Bao" is what people call me, not a pen name. This site and my work at YUTUO Technology are the same person; I do not separate the two.

How this differs from the company site

I write the same topics twice, for different readers:

	yutuo-tech.com	Here
Written for	Business owners	Other engineers
Answers	Whether to do it, what it costs, how to judge	How to do it, why it broke, what the commands look like

The same piece never runs in both places. Where topics overlap, one side covers the judgment and the other the implementation, and they link to each other.

What I write about

Only the three kinds of thing I have done myself:

• Infrastructure: static site deployment, S3 and CloudFront, DNS and certificates — the parts that fail quietly
• System delivery: data migration, permission design, keeping an audit trail
• Tools and process: approaches one person can still maintain

Not industry commentary, not tool unboxings, and not write-ups of technology I have never shipped.

How I write

1. Only things I have actually done
2. Numbers, commands and settings are copied out of real environments
3. Where I am unsure, I say so
4. Revisions are listed at the foot of the post rather than quietly applied
5. Any commercial relationship with a product or company I mention is disclosed

Point 4 is where this site's layout comes from — every entry carries a number, a timestamp, and a revision record. Anyone who builds internal systems knows that a record edited without a trace is not worth trusting. The same applies to what I publish.