Organization¶
General organization concepts¶
Resources for chief technology officers, with the emphasis on startups [reddit]
Company handbooks:
Building Self-Managed Teams: A Case Study from Riot Games [reddit]
Open Decision-Making (by John Ousterhout)
book on how to run a successful free software project: Producing Open Source Software
Software and Anarchy [HN] - Possibly interesting book (~50 pages) on programming as it relates to “social ecology” and “peer production”
Meetings¶
biweekly / monthly meetings on readings / interesting articles / potential new projects
people should talk about 1 (or more) articles, piece of news, or brainstorming idea of potential new/fun/interesting projects
meetings are audio-only, we don’t want webcam
It’s freer this way, less physical constraints to participate in meeting. We can use video for slides, images, etc.
own matrix server
meetings should be biweekly 2 hours, no planning or prepared questions, just open discussion where everyone raises whatever question is needed by them
anything goes as to what can be talked about, people are also encouraged to talk about their recent work if they have major changes they want to share with the others.
-> no need for minutes, no one wants to write them, and no one reads them. If anything important needs to be written, this should happen as a documentation writing item of some sort (eg: in linear).
Standard Operating Procedures¶
improvements to software should be made using RFC-style proposals (or BIP, EIP, etc., eg: https://github.com/fioprotocol/fips)
How to Stop Endless Discussions [HN]
rst/markdown template should be provided containing required sections (eg: NABC, etc. see HN comments, for instance also rename “competitors” to “alternatives”)
Documenting Design Decisions using RFCs and ADRs [HN]
check Linear’s method for issue tracking
code review should be a daily task, and we may need to dedicate up to 20% of a day to it. About code review processes and how to make it better/easier: code review decision fatigue (HN)
Code review¶
code review is meant to foster shared ownership of the code instead of one maintainer and various ad-hoc helper devs
The best modern code review tools (2022) [reddit]
Quick fixes to your code review workflow [HN]
From Google: Faster code reviews = 50% higher software delivery performance [reddit]
Empirically supported code review best practices [reddit]
Investigate stacking workflow / stacked PRs
Use checklists for code review such as this one
Git Branching strategies [reddit]
Stacked Diffs Stacking workflow aa Never wait for code review again: how stacking your pull requests unblocks your entire team [reddit]