Thanks for your reply.
Yes, bitemporal modeling helps with data lineage.
What I’m struggling with is reconstructing the process that produced an observation like ordering, constraints, fallbacks.. not just the data state.
Curious if you’ve seen that handled anywhere.
Whoever wants to write the underlying engines for virtually every browser: Apple and Google. They both have their agendas that they try to push via them.
If their experience mirrors my own there will be a follow up post, “Why having 50 individuals on your cap table is a pain, I should have gotten them into a syndicate”
A lot of it comes down to the context and a prompting strategy tailored to the particular model. I don’t believe the current benchmarks really take those optimizations into account.
I’ve personally been getting better results with Gemini as well, but I think it’s just because I’ve used it more.
I agree on this in general. The awkward things here are that:
a) textprotos aren't really touted by the protobuf folks as a thing to use outside Google. I'm not 100% sure why this is.
b) inside Google, there's a perception that you shouldn't use textprotos for much other than hardcoding proto values inside the monorepo (where there aren't really schema-versioning concerns). I think this perception is misplaced, you just have to be aware that a given schema is used in textprotos. Which is usually an easy thing to be aware of. This is just because the schema-versioning concerns are different than with binary photos (e.g. field renames are now breaking).
c) IIRC most parsers unconditionally reject unknown fields. I think the reason for this is highlighted in the docs: you can't safely go from a textproto with an unknown field to a binary serialisation of that proto. IIRC there are some parsers that let you parse unknown fields anyway but then I think you're a bit more tied to a specific implementation than you'd like...
One strange but quite handy alternative is actually the JSON representation. You can use .proto files as a schema but then serialise the values to JSON as there's a canonical mapping. Then you get something that's human readable but with the type safety of protos. Although of course it's not really writable since... It's JSON.
reply