Location: Switzerland
  Remote: Yes (hybrid or on-site for a good fit)
  Willing to relocate: If it's a a good fit
  Technologies: LLMs (Anthropic, OpenAI), TypeScript, Bun, React, Remix, Next, Node, Django, Python, Tailwind, SQLite, OCaml, Nix
  Résumé/CV: https://www.linkedin.com/in/josef-erben-90a002b1/
  Email: josef@erben.systems
  Blog: https://www.joseferben.com/
  Github: https://github.com/joseferben

I thrive in small and highly autonomous teams with a strong focus on product and go-to-market.

If you're looking to switch from foundation models to smaller custom models for faster & cheaper inference, I have experience with fine-tuning and reinforcement learning.

I run my own LLC and I'm open to contract work.

  Location: Switzerland
  Remote: Yes (hybrid or on-site for a good fit)
  Willing to relocate: If it's a a good fit
  Technologies: LLMs, TypeScript, Bun, React, Remix, Next, Node, Django, Python, Tailwind, SQLite, OCaml, Nix
  Résumé/CV: https://www.linkedin.com/in/josef-erben-90a002b1/
  Email: josef@erben.systems
  Blog: https://www.joseferben.com/
  Github: https://github.com/joseferben

Recently, I’ve been using Typescript, React, Bun/Node, Django and Python to build web apps and agentic workflows on top of foundation models. I have some experience with fine-tuning and with reinforcement learning, so I’m also interested in work that is closer to research.

I have my own LLC and I am also open to contract work.

Comments URL: https://news.ycombinator.com/item?id=44101302

Points: 1

# Comments: 1

sometimes all it takes is sitting 20min in the morning just observing sensations in my body, and saying good morning to various organs haha. sounds silly but creates a solid foundation for my day.

imo it's easier to spot the authn/authz issue here

export default function handler( req: NextApiRequest, res: NextApiResponse ) { // updating user details without authn/authz }

than here

"use server"

export async function updateUser(email: string, age: number) { // updating user details without authn/authz }

without having read any next docs. engineers got trained to consider authn/authz the moment they see "http route/endpoint", maybe being more explicit about what happens in the api would help?

or next could provide an authn api for server actions that authn providers would implement?

the main issue i wanted to highlight is that things are not caught at type-check time. maybe vercel could provide eslint plugins? this could codify a lot of the caveats

> There's no way to get around thinking about AuthN/Z with any server APIs

very true! maybe there is a way to make the default secure somehow by making it awkward to publicly expose a POST route by accident. awesome that next.js 15 is doing things in that regard.

thanks for addressing the points leerob, shows the great governance mentioned in the end of the post :)

tl;dr

- Next.js 14 is fast, but App Router caveats increase cognitive load

- Server Actions are awesome, once secured

- Everyone is using Next.js, this is its greatest strength

- Vercel as hosting platform is a joy to use and they save us tons of time

Comments URL: https://news.ycombinator.com/item?id=42794523

Points: 12

# Comments: 4

what do you think?

Comments URL: https://news.ycombinator.com/item?id=42609516

Points: 2

# Comments: 1

one of my favorite books about this that i can not recommend enough is “the miracle of mindfulness” by thich nhat hanh.

you won’t be free from hunger, but it may reframe our relationship with food so there is less compulsion and mindless consumption.

it won’t take away fear in the face of imminent danger (that’s a good thing, we have to survive) but it may reduce background anxiety that’s present in our daily lives.

- fine-grained design tokens (p-63 doesn't exist)

- freedom from having to name things prematurely

- not having to jump back and forth between index.html and styles.css