Location: Palo Alto, CA, USA
Remote: Much prefer in-person but if compelling I can be flexible
Willing to relocate: Yes, anywhere in the world
Technologies: Software (Go, Swift, Gleam, Ruby, Python, WebDev, Deployment), Hardware (CAD, rapid prototyping, DfM, drafting, mechanical engineering), Systems Thinking
Résumé/CV: https://figbert.com/files/cv.pdf
Email: figbert [at] figbert [dot] com
I'm an industrial design junior at Stanford University looking for summer work at the intersection of software and hardware. Want to have a tangible impact on the creation of meaningful products. Love working on diverse problems, diving in on areas where progress has stalled and getting things going again. Feel free to reach out.
I was tricked into trying Gleam earlier this summer, and really liked it! I anticipate that I will at least use it for all future web projects (one example: https://github.com/FIGBERT/bdab) due to my serious JavaScript allergy.
Gleam Decoders are something I haven’t fully wrapped my head around, but are supposedly very powerful and do exactly what this article is focused on (parsing input data into Gleam types) in a more(?) idiomatic way.
I increasingly have come to believe that it is the screen itself that lies at the root of the ills of technology. It brings so much benefit—and so much convenience, from its flexibility—but it is in its fundamental glow-y rectangular nature that sucks us in, crushing our attention, posture, and so much else. Was incredibly fun to experiment with something radically different.
If this is your website, as a heads up it doesn't work well on my browser. Firefox on Android, I believe I have a dark mode and the text is still black but on a very dark background.
ChatGPT?
Seriously though, this is such a weird reply and doesn't fit at all with the account's previous comments. Also has that kind of not-quote-right feel that a lot of ai generated content has
