I've been arguing that "AI" has very little impact on meaningful technical interviews, that is ones that don't test for memorization of programming trivia: https://blog.sulami.xyz/posts/llm-interviews/
The clicking to restart is there mainly for phone users, I realized after sharing with a friend that hotkeys aren't very mobile-friendly. I don't have a good way to detect desktop vs. mobile clients, and technically one can also have a keyboard connected to a phone.
I've also been thinking about zooming, I'll see what I can do over my next lunch break :D
Location: Tokyo, Japan
Remote: Preferred, but not required, been remote for ~5 years
Willing to relocate: No
Technologies: Rust, Clojure, Go, Python, SQL, k8s
Résumé/CV: https://blog.sulami.xyz/pages/robin-schroer-cv.pdf
Email: [email protected]
Hi,
I'm Robin, (Senior) Staff Engineer with 10 years of experience. On the Will Larson staff archetype chart I register mostly as Architect and/or Solver, and I enjoy figuring out what is needed for organisational success. I've most recently worked at CircleCI on the core pipeline orchestration platform as well as config processing. Relevant experiences here include high throughput distributed systems and compilers.
I'm somewhat conversational in Japanese, but by no means business level (yet). Native in German, and can get by in French or Dutch, if need be.
I had a similar kind of idea for a long time, which I put into action a few weeks ago via a standalone transpiler of Emacs' rx macro to common regexp syntaxes.[0] I ended up getting interrupted and didn't completely finish it, but it generally works, though is probably riddled with edge cases.
The basic idea of rx is to use S-expressions to describe regular expressions, and my elevator pitch would've been to embed rx invocations in shell scripts using $(syntax), the main use case being something like sed invocations.
I still think it's a neat idea, and complex regular expressions tend to be hard to parse for humans.
> a good terminal mode so I don't need to switch to another terminal, the builtin terminals either lag badly after 10K lines of input or render/behave strangely when used with ncurses programs
I found vterm[1] to be pretty reliable for any kind of "advanced" terminal use. Also much faster when dealing with large amounts of output.
I'm on the backend, but all I've seen of the new frontend is TypeScript. There has been a decision to switch languages for reasons that someone else can probably explain better than I could, a lot of us lurk here.
The only problems we are seeing is the significant startup time cost (hence the Go bits, where it matters).
Memory usage also isn't always great, but that's more a JVM problem, as it's not releasing reclaimed memory as quickly as you'd like it to. Fine on servers, annoying on a 16GB laptop.
The Common Lisp problems you outlined don't really apply to Clojure, it's a modern lanaguage and has been stable and versatile for us.
I wouldn't call it good, but I'm using Pandoc to generate LaTeX. The whole thing is wrapped in Hakyll, which already uses Pandoc to generate the HTML from the source (org/markdown).
I’ve recently built a thing at work to generate an OpenAPI spec from Clojure specs and some annotations, which worked out surprisingly well. We already have a collection of endpoints through compojure, and we just spec the handler functions and add some annotations for docstrings, and that’s basically it. As an added bonus we have the test suite validate all api calls against the spec, so in theory the OpenAPI spec should always be accurate.
For the curious, we took and hacked https://github.com/metosin/spec-tools to output OpenAPI 3, and added a very thin shim to hook that up to our routes.
We’ve had this (or something similar) at Amsterdam Schiphol for a while now. With the scanners here, everything stays in the bag, electronics and liquids. The time savings are quite noticeable, because people are so slow at taking apart their baggage. Now they just throw on their bag, take off their coat, and maybe their boots, and they’re done, easily saving 1/3 of the time spent at other airport security lines.
Not allowing people to call their custom docker tooling "docker-custom-tooling" on eg. Github seems like they're shooting themselves in the foot. Of course, it might be bad and damage their brand, but it could also enable a great ecosystem of surrounding tooling, some of which they could bless if they wanted to. Imho a poor PR move.