I generally prefer to let one value mean one thing.
Allowing the presence of a dateTime (UserVerificationDate for example) to have a meaning in addition to its raw value seems safe and clean. But over time in any system these double meanings pile up and lose their context.
Having two fields (i.e. UserHasVerified, UserVerificationDate) doesn't waste THAT much more space, and leaves no room for interpretation.
I can jump to one tab look at the code, jump back over and talk to claude for a little.
I can spread this all across several projects using herdrs workspaces.
I still write code when it makes sense.
Sometimes i annotate the code with comments, hop back over and ask the LLM to consume the annotations i just added and make changes.
Sometimes i ask the LLM to analyze lots of code, and come up with a plan of attack for me, then i go implement it myself.
For Personal projects I write much more of the code myself still, because i enjoy it. For work, i do whatever gets the best outcome most efficiently.