Coding Relic
Random musings on software in an embedded world.
Friday, July 28, 2017
Software Engineering Maxim #16: Spreading knowledge makes it thicker
›
(This is one of a series of Software Engineering Maxims Which May or May Not Be True, developed over the last few years of working at Googl...
Wednesday, July 26, 2017
Software Engineering Maxim #15: Sometimes the hard way is the right way
›
(This is one of a series of Software Engineering Maxims Which May or May Not Be True, developed over the last few years of working at Googl...
Monday, July 24, 2017
Software Engineering Maxim #14: Churn wastes more than time
›
(This is one of a series of Software Engineering Maxims Which May or May Not Be True, developed over the last few years of working at Googl...
Friday, July 21, 2017
Software Engineering Maxim #13: Cadence trumps mechanism
›
(This is one of a series of Software Engineering Maxims Which May or May Not Be True, developed over the last few years of working at Googl...
Wednesday, July 19, 2017
Software Engineering Maxim #12: No postmortem prior to mortem
›
(This is one of a series of Software Engineering Maxims Which May or May Not Be True, developed over the last few years of working at Googl...
Monday, July 17, 2017
Software Engineering Maxim #11: Don’t shoot the monitoring
›
(This is one of a series of Software Engineering Maxims Which May or May Not Be True, developed over the last few years of working at Googl...
Friday, July 14, 2017
Software Engineering Maxim #10: Risk is multiplicative
›
(This is one of a series of Software Engineering Maxims Which May or May Not Be True, developed over the last few years of working at Googl...
Wednesday, July 12, 2017
Software Engineering Maxim #9: Evolve systems as a series of incremental changes
›
(This is one of a series of Software Engineering Maxims Which May or May Not Be True, developed over the last few years of working at Googl...
Monday, July 10, 2017
Software Engineering Maxim #8: Money is not the only motivator
›
(This is one of a series of Software Engineering Maxims Which May or May Not Be True, developed over the last few years of working at Googl...
Friday, July 7, 2017
Software Engineering Maxim #7: The service is the product
›
(This is one of a series of Software Engineering Maxims Which May or May Not Be True, developed over the last few years of working at Googl...
Wednesday, July 5, 2017
Software Engineering Maxim #6: It’s a marathon, not a sprint
›
(This is one of a series of Software Engineering Maxims Which May or May Not Be True, developed over the last few years of working at Googl...
Monday, July 3, 2017
Software Engineering Maxim #5: There is an ideal rate of breakage: no more, no less
›
(This is one of a series of Software Engineering Maxims Which May or May Not Be True, developed over the last few years of working at Googl...
Friday, June 30, 2017
Software Engineering Maxim #4: Bricking the fleet is bad for business
›
(This is one of a series of Software Engineering Maxims Which May or May Not Be True, developed over the last few years of working at Googl...
Wednesday, June 28, 2017
Software Engineering Maxim #3: Project plans should have top-down and bottom-up elements
›
(This is one of a series of Software Engineering Maxims Which May or May Not Be True, developed over the last few years of working at Googl...
Sunday, June 25, 2017
Software Engineering Maxim #2: Enthusiasm improves productivity.
›
(This is the second in a series of Software Engineering Maxims Which May or May Not Be True, developed over the last few years of working a...
‹
›
Home
View web version