Those of us old enough to remember BBS servers or even rainbow banners often go down the nostalgia hole about how the internet was better “back in the day” than it is now as a handful o…
That’s fair, and government work can feel kind of like its own parallel business ecosystem in some ways. Sort of like how most of us think of the shops and businesses that are visible to us but not the massive B2B ecosystem just under the surface.
But I think the hope is that gov can standardize and define a certain net positive thing, and use its contracts to start requiring that thing, slowly making it more widespread and therefore common. Ideally the kinks get ironed out over time, and eventually it’s in a state where you can make the leap and start to require it be in place for any application / service above a certain user count.
Bit pie in the sky, but we should be at least trying to find ways to use govt to improve our situation. Things at policy level that don’t require chronically status quo politicians to vote in our best interests.
Interoperability is a big job, but the extent to which it matters varies widely according to the use case. There are layers of standards atop other standards, some new, some near deprecation. There are some extremely large and complex datasets that need a shit-ton of metadata to decipher or even extract. Some more modern dataset standards have that metadata baked into the file, but even then there are corner cases. And the standards for zero-trust security enclaves, discoverability, non-repudiation, attribution, multidimensional queries, notification and alerting, pub/sub are all relatively new, so we occasionally encounter operational situations that the standards authors didn’t anticipate.
I’ve had to implement wave after wave of compliance with European laws in the last several years. We tend to just comply with something like GDPR everywhere because that’s simpler and it’s a best practice. But without the teeth of legislation we’d never bother. There’s always too much to do. I would have a hard time doing something that’s better for consumers but takes a lot of effort or might even undermine our ability to monetize as aggressively as we choose to. Not without those teeth. Not a chance. Even with teeth, tech companies often find some shitty way to meet the minimum bar but really do nothing. We must offer an API? Okay. It has almost nothing in it, but enough to say we did something. We’d never stand up an API that competitors or scammers could benefit from.
Oof, well, point taken and sorry for your loss lol. I hear where you’re coming from. And I’m sure we’d get a worst of both worlds situation here in the US where we spent a ton of time and money developing whatever standards and definitions, and then we make it an optional guideline like you’re saying and it never goes anywhere.
Dunno. The fundamental problem is tech is always able to move faster and smarter than legislation.
That’s fair, and government work can feel kind of like its own parallel business ecosystem in some ways. Sort of like how most of us think of the shops and businesses that are visible to us but not the massive B2B ecosystem just under the surface.
But I think the hope is that gov can standardize and define a certain net positive thing, and use its contracts to start requiring that thing, slowly making it more widespread and therefore common. Ideally the kinks get ironed out over time, and eventually it’s in a state where you can make the leap and start to require it be in place for any application / service above a certain user count.
Bit pie in the sky, but we should be at least trying to find ways to use govt to improve our situation. Things at policy level that don’t require chronically status quo politicians to vote in our best interests.
Interoperability is a big job, but the extent to which it matters varies widely according to the use case. There are layers of standards atop other standards, some new, some near deprecation. There are some extremely large and complex datasets that need a shit-ton of metadata to decipher or even extract. Some more modern dataset standards have that metadata baked into the file, but even then there are corner cases. And the standards for zero-trust security enclaves, discoverability, non-repudiation, attribution, multidimensional queries, notification and alerting, pub/sub are all relatively new, so we occasionally encounter operational situations that the standards authors didn’t anticipate.
I’ve had to implement wave after wave of compliance with European laws in the last several years. We tend to just comply with something like GDPR everywhere because that’s simpler and it’s a best practice. But without the teeth of legislation we’d never bother. There’s always too much to do. I would have a hard time doing something that’s better for consumers but takes a lot of effort or might even undermine our ability to monetize as aggressively as we choose to. Not without those teeth. Not a chance. Even with teeth, tech companies often find some shitty way to meet the minimum bar but really do nothing. We must offer an API? Okay. It has almost nothing in it, but enough to say we did something. We’d never stand up an API that competitors or scammers could benefit from.
Oof, well, point taken and sorry for your loss lol. I hear where you’re coming from. And I’m sure we’d get a worst of both worlds situation here in the US where we spent a ton of time and money developing whatever standards and definitions, and then we make it an optional guideline like you’re saying and it never goes anywhere.
Dunno. The fundamental problem is tech is always able to move faster and smarter than legislation.