325 karma · joined March 24, 2014
https://blog.sulami.xyz
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: hire@sulami.xyz
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.
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.
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.
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.
Feel free to dig through the source if you want to see how it works: https://github.com/sulami/sulami.github.io
I know next to nothing about AI, beyond the basics of RNNs, so I'm hoping to learn a lot.
Raw css is here: https://github.com/edwardtufte/tufte-css
My additions on top (and all other source) here: https://github.com/sulami/sulami.github.io/tree/develop/css
org-mode already does tables with formulas and all[1], if you’re interested in text-based spreadsheets
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.
I don't know if I could ever going back to an imperative language full-time, I think I'd feel very hampered.
Remote: Yes
Willing to relocate: Yes
Technologies: Python (Django/Flask), Haskell (Yesod/Scotty), Go, D, C, SQL, HTML/CSS (, Git, AWS, Linux)
Resume: https://sulami.github.io/raw/resume.pdf
Email: sulami@peerwire.org
Github: https://github.com/sulami
Blog: https://sulami.github.io
I'm a German dev (fluid in English) with about five years professional Experience developing Backends, REST APIs and a whole bunch of mixed tools and software to go along, also some quite low-level. I like complex systems and the challenges that come with scaling them, and I'm also sort of religious when it comes to code quality and productivity enhancements.
Remote: Yes
Willing to relocate: Yes
Technologies: Python (Django/Flask), Haskell (Yesod/Scotty), Go, D, C, HTML/CSS, SQL, Racket/Scheme
Resume: https://sulami.github.io/raw/resume.pdf
Email: sulami@peerwire.org
Github: https://github.com/sulami
Blog: https://sulami.github.io
I'm a German dev (fluid in English) with about five years professional Experience developing Backends, REST APIs and a whole bunch of mixed tools and software to go along. I like complex systems and the challenges that come with scaling them, and I'm also sort of religious when it comes to code quality and productivity enhancements.
I get the point, but feel different. When a project becomes large enough, changes can result in breakage in the weirdest places. Proper testing can help discovering this breakage before shipping. For me, tests are a safety net for changes in the tested code.
Large projects without any tests are effectively unmaintainable, often times even for the original author, and most certainly for others.