But I'm not sure where to start automating this. It would be great to have some examples.
I plan to migrate this to a more flexible Roswell script in a near future.
This is basically a way to create menus and submenus for recurrent utilities. You can use a rofi or dmenu frontend. Once you bind it a key shortcut, rofi/dmenu will come up asking you what to do.
Right now I can directly access my favorite websites, open my favorite programs, do web search (and also switch web engine), all without touching the browser directly. The idea is to group a lot of things in a lightweight script, and have a keyboard-only interaction with no extra extensions or programs.
I agree that the README is a little poor right now, and screenshots/gifs would also help on this regard. I'll start working on it pretty soon.
I think his OOP is closest to what we'd call actors today.
Erlang is another story: it would probably be better to call it just actor model. But again, Kay himself says[2] that there is not a lot of difference between actor model and his OOP.
[1] https://www.youtube.com/watch?v=oKg1hTOQXoY
[2] https://www.quora.com/What-is-the-difference-between-Alan-Ka...
Having commands for each DAG operation will just add more complexity and expose a structure which you shouldn't be handling manually.
Maybe it was a bit of a cattle-call experience, but IBM is sorting through thousands of similar grads and needs some way to screen them for technical positions when many will have no professional history.
If being asked to take some tests, then flown out for a stay in a nice hotel and a big mixer (with some great networking opportunities, btw), then offered a six-figure salary at your first job out of school requires a "name and shame," then the OP sounds a bit entitled.