#altswe Introduction: alternative approach to SWE
This is an introduction page for the #altswe series, where I describe ideas for an alternative approach to software engineering.
I've been fortunate to work on software with a lot of smart and hard-working people, in a lot of cool places. And while the companies I worked for were often very different: their business, products, size, growth, etc., the way software engineering was organized, was actually very similar.
I feel like generally, we just keep doing things “as we did them at my previous company”, and very rarely anything truly different is being considered.
I'm a natural contrarian, and I'm always on the lookout for alternative approaches. I just couldn't help myself but to develop a list of things that I really wish I could have an opportunity to try one day.
If I am ever in charge of a team or a company, I'd like to try some or even all of them, and see how well (or bad) they work.
For now, I am just gathering them here, under the #altswe tag. The ones without a link, are yet to be written.
- Kill Instant Messaging – less is more.
- Less is more – cut unnecessary tools, projects, features.
- Work in pairs
- 4x7 – 4 days a week, 7 hours – again: less is more.
- No Scrum, No Standups, No “Wish Points”
- Ownership – Root of safety in Rust, prosperity in the markets, and quality in SWE.
- Avoid success at all cost