Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Code by mass live committee. Yikes.

Let's lean into the chaos and see what it might give us. Imagine a production application deployed directly from a non-version-controlled directory. Anyone on the team can edit the files, at any time. Insane? Probably. The disadvantages are easy to see.

But the positives are really compelling: 1. make small, granular testable changes; 2. use feature toggles; 3. refactor intensely and concurrently; 4. always work on the latest code; 5. use in-code documentation instead of GitHub/etc workflows; 6. explore continuous, incremental, hot-swappable code deployment.

Doesn't thought of ditching all the wasted motion and ceremony around logging async work and just coding sound glorious? I'm actually not a "move fast and break things person" usually. But the idea of moving so fast that broken things will only stay broken for a tiny fraction of the time is pretty compelling. There is also an intensity that comes from real-time interactions where a team needs to reach consensus quickly.

Feature Toggles: https://martinfowler.com/articles/feature-toggles.html

BEAM (Erlang, Elixir) provides hot-swappable code and lots more



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: