Public Medium Doc - Technology Guiding Principles Framework

	A	B	C	D	E	F	G	H	I	J	K	L	M	N	O	P
1	Guiding Principles (how we want to operate)	Theme	Team Voting
2	Guiding Principles (how we want to operate)	Theme	AR	LP	UB	BS	JB	OP	AS	FB	DJK	DK	CT	DKK	AD	# Total Votes

3	Develop good expertise with a limited set of tools; let's be careful of what we adopt to make sure we move fast	Technology Selection	1	1			1		1			1		1	1	7
4	Keep it simple, approachable and accessible, low barrier to entry, always think MVP	Simplicity	1	1				1	1	1	1		1	1		8
5	We live in the codebase, let's keep it clean; proper coding standards, style guide, do what works for all	Codebase Hygiene	1	1	1	1	1	1		1		1	1	1		10
6	Leverage technology that solves a particular problem, not just because it's cool	Technology Selection	1	1		1						1		1	1	6
7	Think outside-in, ensure you are building what your customers want	Thought process		1		1		1	1	1		1	1	1		8
8	Be transparent with new ideas, try to get buy-in	Collaboration	1					1	1							3
9	Leverage innovative/creative thinking when solving problems	Innovation				1									1	2
10	Write clear, concise documentation; make it easy for others to pick up your work	Documentation			1		1			1						3
11	Refactor or Re-write only when the asbsence of refactoring/rewriting causes pain; ask a colleague if you aren't sure	Refactoring		1					1	1						3
12	Leverage open source and existing libraries whenever possible; don't reinvent the wheel but also ensure projects are well-maintained and have a future	Open Source	1								1		1		1	4
13	Hacks should go in only when something is on fire. Also, we must revisit the hack once things are stable and fixing this should be the highest priority.	Codebase Hygiene	1		1	1					1				1	5
14	If it helps the business get it done and don't complain	Attitude										1		1		2
15	Avoid unnecessary abstraction; if it's only used in one or two places in the code, it may be too soon.	Speed / Legibilitiy	1	1	1		1	1		1	1	1	1	1		10
16	Be ethical and empathetic to the user; it's never their fault.	Thought process					1	2					1			4
17	Apps: Write automation covering the happy path of your feature	Testing			1		1		1	1					1	5
18	Fix immediately whenever you encounter small code quality issues	Codebase Hygiene		1	1	1					1	1	1	1		7
19	Everything else being equal, prefer "verbose but straightforward" over "concise but abstracted". Reduce mental burden for newcomers and sleep-deprived coders	Simplicity	1						1		1	1	1		1	6
20	Write code in paragraphs, and provide headings in the form of comments. The "storyline" should be clear to anyone reading your code	Legibility					1									1
21	Help others who are in need of help	Collaboration		1	1	1	1	1	1	1	1	1	1	1	1	12
22	Avoid policies that pit developers against each other	Collaboration			1	1									1	3
23	Prefer task prioritization over long hours	Sustainability				1				1	1		1			4
24	No cultural/school/achievement-related elitism	Collaboration			1											1
25	Skepticism and disagreement is fine, but do it respectfully	Collaboration				1	1	1	1		1	1				6
26	Minimize context-switch as much as possible (e.g. formatting style, naming style, toolset)	Simplicity													1	1
27	Aim for iterative improvement over getting it perfect the first time	Thought process	1	1	1		1	1	1	1	1			1		9
28																0
29																0
30			10	10	10	10	10	10	10	10	10	10	10	10	10	120
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100