Do any of these options support communicating via an http API instead of stdin/out?
Ideally I'd like to have a standalone websocket service that handles long-running connections and then calls my specified API eg. `POST <my-http-service>/websocket/client/<client_id>`. Then the service can respond by sending a `POST <my-websocket-service>/websocket/client/<client>`, like an opensource https://pusher.com? I realise it'd be fairly easy to build myself, just wondering if there is something off the shelf that achieves this?
Start writing things down. If you have a terrible memory like me you might regret not documenting more of your life, especially because so many things happen in your 20s. I've started a weekly journal in my 30s and I'm so happy that I did.
It's also worth doing the same for things at work. Having a few stories written down about features you've implemented or bugs you've fixed may help you get through a few interviews.
Yeah I thought it was really interesting, spoiler alert - in a random sequence of events Lena, the model from the JPEG study ends up becoming a Kodak Shirley girl too.