The DX·Tooling projects are switching from dxcli to mise:
dx-tooling.org/blog/2025-11...
01.11.2025 16:14
👍 0
🔁 0
💬 0
📌 0
The DX·Tooling projects are switching from dxcli to mise:
dx-tooling.org/blog/2025-11...
Erste Gehversuche im Format Video: Ich habe eine Live Coding Session im Rahmen des DX·Tooling Projekts aufgezeichnet, bei der ich unter anderem aufzeige, wie man mit speziellen Software-Tests die Einhaltung von Architekturregeln in einer Codebase garantieren kann: www.youtube.com/watch?v=i0l7...
I've put Toxiproxy between the app and the database (app connects to Toxiproxy, Toxiproxy connects to database), added a bit of latency to the connection, and voilà, realistic behavior (and realistic performance degradation) on my MacBook.
It allowed me to pinpoint a performance issue in one of my applications, where the severity of a N+1 query pattern was not really visible on my dev system (where app and database live on the same host), but was painfully visible on the production system.
Just found out about Toxiproxy, a network proxy that can be used to simulate network conditions locally:
github.com/Shopify/toxi...
It's the Playwright MCP hosted through playwright-mcp.develop-build-deploy.com (which is a brilliant service propped up by @manuelkiessling.bsky.social !)
New long-form blog post:
Senior Developer Skills in the AI Age: Leveraging Experience for Better Results
manuel.kiessling.net/2025/03/31/h...
- you need battle-tested engineering experience
- understand the problem and solution domains
- write precise and thorough, well-structured requirements
- have encompassing Quality Tools in place — tests, linters, static analysis etc; agent mode is a bliss with these in place
I have done my fair share of „vibe coding“ over the past few months, and it’s been a blast.
Turns out the key to successful and sustainable results is the same stuff we as a craft valued since basically forever: ↓
You had me at "hello, world".