josefrichter
On one hand, you set some boundaries on user interface layout, flow, allowed components, etc. so that the interface looks & feels like belonging to the same product every time.
On the other hand, you may decide to leave more "creative freedom" in some other areas. The fun part comes when you let it work in semi-realtime in production, and get sort of generative/organic UI. I enjoy experimenting with that these days.
- I'd hire someone who keeps building even when jobless.
What you build is your CV/Cover, and your learning opportunity. These days, you have to know LLMs inside and out, which means using them heavily to learn.
- The subscription is probably below or around the daily rate, so it pays off quickly.
I'd argue that it's an investment in your education - not only learning to work with LLMs, but also using LLMs to teach you almost anything (even beyond tech).
Location: Czechia, EU
Remote: Yes
Willing to relocate: No
Technologies: Figma, Paper, Claude Design, Open Design, Elixir, Phoenix, LiveView, Hologram, BEAM, Node, TypeScript, React, Next.js, React Native, Swift, Swift UI, Ruby, some Rust, Go
Résumé/CV: https://josefrichter.design/cv
Email: [email protected]
Equal parts designer and developer (not vibe coder)
Focusing on agentic design systems these days - full validation loops, smarter governance, proper testing, etc. Building some design factories, experimenting with genUI - check the latest snippets at https://www.linkedin.com/in/josefrichter/ too, and https://josefrichter.design/blog
Past: T-Mobile, Vodafone, Medable, Enaia, various fintech
Location: Czechia, EU
Remote: Yes
Willing to relocate: No
Technologies: Figma, Paper, Claude Design, Open Design, Elixir, Phoenix, LiveView, Hologram, BEAM, Node, TypeScript, React, Next.js, React Native, Swift, Swift UI, Ruby, some Rust, Go
Résumé/CV: https://josefrichter.design/cv
Email: [email protected]
Turns out "design engineer" is the new name for what I've been doing for 10+ years. Product/ux/ui design of complex Saas and mobile products. Full-stack development in Elixir, JS/TS, Swift,.. Shipped production apps, agent-ready/agent-first, mcps, apis, agents, loops..
See https://josefrichter.design/blog and https://github.com/josefrichter
Past: T-Mobile, Vodafone, Medable, Enaia, various fintech
Using @apply totally KILLS Tailwind - that's the clearest tell that the author didn't have that moment yet. Hence the other arguments in the article that feel somewhat petty.
It’s been around for years now. The great thing about it is it works worldwide - so if you come to a country and have no clue which company operates there, you just open Obi.
you get a snippet from LLM, compile it to module, and hot-load it into the running node. the module lives in the node's code table, so it persists and every other agent can call it. not just the one that wrote it.
the agents themselves are seaprate supervised processes, so if one crashes - e.g. because the snippet was crap, it doesn't take down whole system.
of course you can do that in just elixir too, the lisp is just cosmetics really.