Hello, I'm Kuhrt

If people struggle with my application, they won't use it.

1. Dig deep to find the real "why" – Most problems have been solved already, the art is understanding what we're actually building
2. Accessibility is a requirement, not a feature – Great software works for everyone from day one
3. UX/UI professionals are force multipliers – I rely on designers heavily because frustrated users don't become successful users. This also means nailing the implementation
4. Automate the small friction points – The best solutions make tedious processes disappear entirely

Later means never - fix the code now or it decays rapidly

1. Sign your work with pride – Taking ownership transforms code from "works" to "crafted"
2. Business logic should be readable in code – If requirements aren't easily visible in code, something's wrong
3. Testing code isn't optional – Testing can define requirements and small, testable functions create maintainable systems
4. Small interfaces, deep implementations – Clean abstractions hide complexity, don't eliminate it

20% of features deliver 80% of the value

1. Relentless focus on what moves the needle – Perfect execution on the wrong thing is still wrong
2. Communication is a core technical skill – The right questions early prevent months of wrong solutions
3. Root cause analysis over feature requests – What users think the problem is isn't always the problem
4. Measure what matters, ship what works – Data-driven decisions separate successful products from feature factories

Agile means how fast a team can change direction when needed

1. Change is inevitable – Great teams anticipate and adapt. Build systems and culture that embrace evolution, not resist it
2. Lifetime learning is non-negotiable – Technology changes, curiosity is constant
3. Leadership is service – Point the right direction, supply your team with what they need, and remove obstacles
4. Trust is the foundation of velocity – Teams that trust each other, and what they can do, ship faster and better