This is too close to Idiocracy

Yeah I’ve had this same idea for the same reasons, and came to the same conclusions that without legislation, no incentive exists to send statements as attachments in emails or to store them with a 3rd party where they can’t be tampered with when a mistake is discovered

> Dubs

Not sure if anyone else noticed the item id of this comment does indeed end in 88?

Dubz get!!!

Particularly ironic since it mentions nazis...

I'm interested to hear more about this. I think I have a tendency to want to do this myself. Any additional reading on this concept?

Taking real disconnect breaks (more than one week) also help a lot. Some people, including me until recently, don’t seem to do this often or at all

To be pedantic, its purpose is for verification testing of systems that allow for testing of the type you describe

I think this is still possible with access points that require installing and trusting a custom certificate. The example in my mind is WeWork's WiFi

Installing a WiFi client certificate (in lieu of a PSK) and installing a root certificate used for TLS (in lieu of those distributed with the OS) are two completely different things, no?

Seriously?! That’s insane and would get my work laptop quarantined in minutes.

It seems like even the Startup School signup is limited to students. I applied anyway, and will comment again if I receive a response

Can it do React yet?

I can run a dev server in the app and access it from an iframe, so adding React support is straightforward, and I plan to do it. I’ll then feed screenshots of the rendered output to AI to evaluate if it’s rendering correctly at various widths. The hard part will be scaling Otto to work on larger bodies of code!

I think going from code to OpenAPI makes a lot more sense, at least for strong typed languages. And even if not directly translated from code, at least closer to the actual code, in annotations or something. Generating the spec from code removes a step, where you simply need to update code, rather than update the spec then update the code

Completely agree. Keeping the openapi spec as tightly coupled to types in code builds a single source truth from your development to your deployment