824 karma · joined May 2, 2011
My conclusion is, that i want neat markdown. Hence it needs to be linted/formatted.
Developed a linter/formatter https://mdsmith.dev to specifically do that. Includes tooling for progressive disclosure, etc.
In general, what helps is to instruct ai to use test coverage to ensure the cover all edge cases with tests.
In the old days it would take me weeks to get a good document out of door. Now a it is days. While the absolute number of iterations polishing is higher.
I take a spare sensor, spare pump (Omnipod), spare insulin, and an insulin + dextro.
On vacation, I take a spare phone, in case my phone that manages pomp and sensor breaks down.
It happened already twice on vacation in the past 5 years.
I have regularly sessions open for multiple days.
Is that a pattern that is not advised?
Further, i don't trust code anymore that hasn't been reviewed 3x or more by co-pilot.
If you have asked me 6 months ago I wouldn't have expected this change so soon.
Was wondering if using front-matter instead of a "custom" encoding for parseble data was considered?
Is these more related to the existing source code or is this a bad pattern thar you would never do regardless of the existing code?
Quickly scanned the programming guide - but wasn't able to find it. Did i miss a section?
15. Content that may violate the rules and standards set forth by Steam’s payment processors and related card networks and banks, or internet network providers. In particular, certain kinds of adult only content.
See discussion here for example: https://steamcommunity.com/discussions/forum/0/6019100814124...