The Effective Software Architect - Work Smarter, not Harder
summary
Conversations across Atlassian, MongoDB and Manfred surface concrete habits: prioritise simplicity over cleverness, show code to juniors as a canary test, follow code review rules from Bitbucket (criticize ideas not people, be gentle, suggest rather than spoon‑feed), and reserve time for structured experiments like ShipIt 24‑hour hackathons or MongoDB’s half‑year Skunk Works week. Try tooling such as structuralizer by Simon Brown and Gitpod. Measure outcomes: Jira Service Management starts as a ShipIt prototype and becomes a multi‑billion product; quarterly hackathons cost ~0.7 hours/week but reveal what to build.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 8:08Architecture as teamwork
- 15:36Code reviews best practices
- 23:21Continuous learning strategies
- 34:57Innovation through experimentation
- 40:36Focus on customer value
- 44:34Effectiveness vs efficiency
related talks
50mThe Effective Developer - Work Smarter, Not Harder
31mThe Effective Developer - Work Smarter, Not Harder
01h 03mThe Effective Developer - Work Smarter, Not Harder.
33mHow Minimalism Helps Build High-Quality Products
38mAgile Architecture
01h 01mKeynote: Software Craftsmanship – Growing a Technical Culture
01h 00mThe Influential Software Engineer
25mThinking Architecturally