Is there anything to back this up? The people I know who work out are always complaining about their muscles and joints.
I’m often complaining about soreness here, a lightly pulled there, a big joint that needs to be left alone for a few days. It’s annoying but also even kinda satisfying, and I know how to avoid serious injury.
I’m not complaining about lower back pain because my fitness activity has rid me of it. That pain would have stopped me from being able to move easily, work on my cabin, play with children, and would have eventually made me overweight and chronically ill.
The tradeoff is really a no-brainer in my case, and I don’t think my case is so unique.
It is a project for model based governance of Databricks Unity Catalog, with which I do have quite a bit of experience, but none of the tooling feels flexible enough.
Eventually I ended up with 3 different subagents that supported in the development of the actual planning files; a Databricks expert, a Pydantic expert, and a prompt expert.
The improvement on the markdown files was rather significant with the aid of these. Ranging from old pydantic versions and inconsistencies, to me having some misconceptions about unity catalog as well.
Yesterday eve I gave it a run and it ran for about 2 hours with me only approving some tool usage, and after that most of the tools + tests were done.
This approach is so different than I how used to do it, but I really do see a future in detailed technical writing and ensuring we're all on the same page. In a way I found it more productive than going into the code itself. A downside I found is that with code reading and working on it I really zone in. With a bunch of markdown docs I find it harder to stay focused.
Curious times!