jackpepsi

You may find this unasked for scan humiliating, but we can mathematically prove we're not humiliating you. Any feelings of discomfort or humiliation are therefore invalid and should be set aside.

Edit: I'm sure a greater good argument can be made. I just don't think they are making it in a way that justifies the invasiveness.

  Location: Berlin, Germany
  Remote: Yes
  Willing to relocate: Only To Australia (I'm from there)
  Technologies: Full Stack Product Engineer 17 years experience (Frontend leaning, with automotive and hardware interface experience)
  Résumé/CV: https://tobyk.com.au/cv.pdf
  Connect on LinkedIn please, email has too much spam. https://www.linkedin.com/in/toby-knyvett/

I'm a specialist if you need to build an AI assisted cockpit, either in a literal physical sense or giving that feeling to a web/mobile interface. My strength is finding how to give users a truly intuitive feeling of control when they use a product, like their own capabilities are extended.

As an engineer I'm frontend UX design leaning, though I do love making an API and not afraid of migrating a database.

Broad experience across B2C + B2B, SaaS, manufacturing (Volkswagen) and streaming (events). Shipped for 250K+ viewers, 10K+ production vehicles and one self driving car on public roads.

Got technical complexity? I'm on it. Shipping on the stack you got today.

Got organisational complexity? I'm on it. Experience shipping from Europe into China market via Joint Ventures.

---

And now the glorious list of technical trenches in which footguns have blossomed into experience:

  Frontend - Typescript - React - Tailwind

  Backend - Go - some Rust - good ol Typescript

  Infra - CloudFlare - AWS - Terraform

  Dare I say Figma? Prefer to design in code myself but it's good for collabs and sign off.

  Was working with AI since before the LLM era, using ML for user detection in automotive interiors.

Reach out on LinkedIn https://www.linkedin.com/in/toby-knyvett/

SEEKING WORK: Berlin based, Remote possible.

Full stack product engineer. 17 years experience.

Frontend UX design leaning, though I do love making an API and not afraid of SQL.

Broad experience across B2C + B2B, SaaS, manufacturing (automotive) and streaming (events). Shipped for 250K+ viewers, 10K+ production vehicles and one self driving car on public roads.

Got technical complexity? I'm on it. Shipping on the stack you got today.

Got organisational complexity? I'm on it. Experience shipping from Europe into China market via Joint Ventures.

--- And now the glorious list of technical trenches in which footguns have blossomed into experience:

Frontend - Typescript - React - Tailwind

Backend - Go - some Rust - good ol Typescript

Infra - CloudFlare - AWS - Terraform

Dare I say Figma? Prefer to design in code myself but it's good for collabs and sign off.

Some recent projects https://tobyk.com.au/portfolio/

Reach out on LinkedIn Toby Knyvett (too much spam on email sorry)

From the perspective of "The general purpose computing device I own should be able to run any instructions written by anyone without legal issues" then copyright sucks. Massively abused by corporations to unproductively charge rent by squatting on obvious implementations.

From the perspective of "I'm an artist and I want to make a living off the things I create" copyright has some utility. (Although also gets in the way at times, as in bad faith music plagiarism cases)

I feel both perspectives. On a moral level not sure how to unite them in a way that doesn't enable some kind of abuse.

I'm sure we can improve the current systems though.

This is blocked for me. Can anyone post an archive link?

I think they explain a compelling problem about typical commerical software vs FOSS, then they dive into their GPU accelerated VM solution. I don't see how it helps solve the original problem.

Is is that FOSS needs a standard sandbox and they think some kind of peer to peer app store that disturbes images for VMs is the way to do it?

I resonate with what the author said about losing track of the Mental Model. I think that's the key to enjoying the process or not. I.e. the building up or utilising of that mental model (my own understanding) is they key to finding software development joyful.

Specifically:

"Easy but boring project" case: For projects where I am already familiar with a strong and sensible architecture then I find AI enjoyable to work with as a simple speed boost. I know exactly what I'm asking AI to do at every stage and can judge it's results well. It's not that interesting to me to code these components myself because I've done it before several times. My mental model of the problem space and a good solution is complete. I get some satisfaction from using my mental model.

"Challenging but interesting project" case: For projects where I don't yet understand the best architecture then I will inevitably ask AI to connect Component A to Component B without yet understanding that there should be a Component C. Because I don't have the understanding of the problem space. The thing is before AI I may have made this mistake myself, I just would have had the satisfaction of learning at the same time.

Given the time with these type of projects I basically write them twice: First pass making it work but as a huge mess, but building a mental model of the real problem space along the way. Second pass refactoring and getting it right, creating now a mental model of a good solution. Only after two passes would it be a project I would feel is done correctly and be happy (joyful) to publish it.

I have found AI enables you to get the first pass working much quicker, but without the learning along the way of the mental model to inform how to make the second pass properly. So If I want the challenging project to be joyful I still need to invest the time to learn from the first pass.

And that specific learning task I enjoy more if I do it iteratively as the AI and I build together, it's less enjoyable if I sit down afterwards and only inspect the code.

SO if I want a challenging project to be joyful I have to continue investing the time in the first phase to do the learning. AI just gives the opportuntity to produce a messy working prototype without learning anything, which may or may not make sense for the business side of things.

We expect comitted founders to make the best of their constraints.

This founder is doing that by putting a positive spin on their constraints in their social media posts.

Fallibility is important and I hope that founder is honest with their team, but at the same time keeping a positive public narrative about your company is also important. Not everyone has to perform their growing pains in public.