Matthias Lohscheidt

@mattiloh.de

Co-founder and CTO @picter.com. Leading talented people to build great digital products. 3D printing, dancing Lindy Hop. Dad of two daughters. Posting about tech, software engineering, web development, react, postgres. mattiloh.de

@eslint.org is even more valuable in times of agentic coding. A very fast automated feedback loop. Best part: if weird patterns emerge that are specific to your project, let AI write custom linting rules to prevent them in the future. And be careful that it doesn't disable them too lightly…

Biggest moat for SaaS against vibe-coded solutions: all the laws out there regulating digital products and services. At least when public facing. (CRA, DSA, GDPR, to name just a few EU-based ones)

This line in my personal preferences in Claude is gold. I got honest pushback on some assumptions in my conversations with Claude recently: > When I present flawed ideas, I like to be challenged and offered alternative approaches.

Using Wispr Flow since two weeks now. Funny to see how my writing brain seems not to be the same as my speaking brain, and how I need to "merge" them to effectively use a speech-to-text tool like this.

🌐 next-intl 4.5: useExtracted → For humans & AI → Next.js-first by design → Full Turbopack support → SWC-based parsing

Code sample that demonstrates useExtracted

User deletion from Mailchimp lists via API is a mess. A regular delete only archives the user (not #GDPR compliant). A permanent delete means you can’t re-add them later if they sign up again – unless you do it manually through Mailchimp’s UI.

I rarely used GitHub Actions, mostly CircleCI in the past. Just reviewing some GH actions and the integrated Copilot AI is proving to be helpful for gaining more insights without the need to context switch.

A screenshot of a conversation with GitHub Copilot. The user asks if multiple events, like pull_request and workflow_run, in a GitHub Actions workflow are connected using boolean logic, specifically whether all triggers must occur or if just one suffices. Copilot responds by explaining that the events are connected with an OR logic, meaning the workflow will trigger if any one of the events happens. The interface includes a prompt bar labeled "Ask Copilot" with icons for attachments and actions.

We had a weirdly ineffective decision situation this morning which reminded me of that blog post by @industrialempathy.com. I believe the 'vetoes instead of approvals' principle is very powerful and it will be part of our decision framework moving forward. www.industrialempathy.com/posts/organi...

Organizations are distributed systems

The assertion that “corporate organizations are distributed systems” hovers between being a tautology—since it is literally true—and a hot...

industrialempathy.com

Playing with the agent mode in Cursor is really fun. Interestingly, the same principle applies here as it does with less autonomous AI assistants: quick, small steps over giant leaps. This approach helps maintain control and steer in the right direction.

Claude's artifacts feature is incredibly helpful for iterating on texts. But one thing that's missing is the ability to edit artifacts directly. Being able to make adjustments myself and then provide further instructions would speed things up significantly.

I really enjoy @bsky.app! Control over your feed is a game-changer: No trapping algorithms No energy-draining outrage posts No engagement-chasing clickbait The world suffers from algorithmic feeds prioritizing attention at the cost of mental health, societal division, and stress. Let's be better!

Data models provide excellent context when working with AI assistants. I usually start by creating schemas or TypeScript types as a foundation, then prompt for specific functions or components. This approach sets clear boundaries and minimizes the need for adjustments to the generated code.