🥵 Low effective development environments:

- constant false positive alerts from production
- error reports scattered across numerous logging systems
- dependencies to other silos (QA, architecture, security, ops)
- multiple "important" status meetings break up-days
- test suites running for hours and almost always red
- outdated or non-existent documentation
- communication happens via ticket systems

🤑 Highly effective development environments:

- clarity about what to work on next
- CI/CD practices and green pipelines
- incremental changes validated locally by tests
- documentation and API specs found easily and kept updated
- pair & mob programming used without hesitation
- possibility to focus on a task for few hours without interruptions
- commits pushed to production after automated checks pass
- impact of new features analyzed through business and operational metrics

Follow

Tim Cochran wrote a nice article about these two environments. Check it out. martinfowler.com/articles/deve

· · Web · 0 · 1 · 1
Sign in to participate in the conversation
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!