u/NK534PNXMb556VU7p

Generally speaking, Duke Energy can absolutely get fucked filthy and sideways all day everyday. They're the undeniable embodiment of American enshittification.

But their linemen and crews have been working tirelessly amid driving rains, violent storms, and dangerous conditions to ensure my neighbors and me get the conveniences of modern living back as soon as possible. Our power came back on at 3 am this morning, meaning there were linemen (both men and women) working away from their families and the comforts of home in the dead of night to get my family power. Just wanted to share my appreciation for their dedication to the job. They deserve a raise no matter what they get paid.

Just a passion project - no profit or promotion. Feedback welcome.

If there's a better place to ask this, please point me in the right direction. Our team is considering where both user-facing and agent-facing documentation and data will live long-term in order to meet the future needs of our AI-driven solutions, including copilot. Github is the obvious decision for the authoring layer, but we also know that Bigquery and Looker are things we should be concerned about and considering. GIthub allows us to lint our own documentation, use json format with metadata and tags, and obviously track changes over time and by whom. How are other teams addressing this need for storing documentation where it's easiest to ingest by multiple AI-driven solution?