this repo has no description
📝 Update Teamwork guidelines with iteration cycle recommendations and emphasize dogfooding
+4
-2
+1
-1
Programming.md
+1
-1
Programming.md
···
82
82
- [Laws of Software Development](http://www.globalnerdy.com/2007/07/18/laws-of-software-development/)
83
83
- [Famous Laws Of Software Development](https://www.timsommer.be/famous-laws-of-software-development/)
84
84
- [Laws of Computing](https://gist.github.com/sorahn/905f67acf00d6f2aa69e74a39de65941)
85
-
- [Hacker Laws](https://github.com/dwmkerr/hacker-laws)
85
+
- [Hacker Laws](https://github.com/dwmkerr/hacker-laws) ([website](https://hacker-laws.com/))
86
86
- [Engineering Axioms](https://martinrue.com/my-engineering-axioms/)
87
87
- [CUPID](https://dannorth.net/2022/02/10/cupid-for-joyful-coding/)
88
88
- [Things they didn't teach you about Software Engineering](https://vadimkravcenko.com/shorts/things-they-didnt-teach-you/)
+3
-1
Teamwork.md
+3
-1
Teamwork.md
···
69
69
1. Question everything.
70
70
2. Remove more than you add.
71
71
3. Optimize what works.
72
-
4. Shorten iteration cycles. **[Boyd's Law of Iteration](https://blog.codinghorror.com/boyds-law-of-iteration/): speed of iteration beats quality of iteration**.
72
+
4. Shorten iteration cycles. **[Boyd's Law of Iteration](https://blog.codinghorror.com/boyds-law-of-iteration/): speed of iteration beats quality of iteration**. No tasks longer than one week. You have to ship something into live production every week – worst case, two weeks.
73
73
5. [[Automation|Automate]] and keep standards.
74
74
- Keep great global [[coordination]] and incentive local experimentation.
75
75
- Being able to run small and compounding experiments (on the product or company [[processes]] and systems) is important. **Work smaller**.
···
144
144
- There may be certain functions where at your current stage that don't need a team yet.
145
145
- Each team runs its own processes. This must be done transparently.
146
146
- The team has the final call in which of its features get into production, with no need for external QA/control.
147
+
- Dogfooding is a superpower. Ship, use, iterate.
148
+
- Prototypes over RFCs and discussions.
147
149
148
150
## Getting Started
149
151