opinionated quotes - into my own blog
https://github.com/dwmkerr/hacker-laws
this one not that great
https://github.com/castorm/engineering-principles
1.25 ^ 10 ≈ 10
https://news.ycombinator.com/item?id=39413832
let small fires burn
https://swizec.com/blog/let-small-fires-burn/
By centralizing services and standardizing your tooling, Backstage streamlines your development environment from end to end. Instead of restricting autonomy, standardization frees your engineers from infrastructure complexity. So you can return to building and scaling, quickly and safely.
release form
https://www.aprilsoetarman.com/Unfinished-Projects-Release-Form
kwargs large hammer
http://ivory.idyll.org/blog/on-kwargs.html
50x 44 (or even 50)
that poster is 60 x 85 really
or small 42 by 60
We believe in a community-driven approach of open-source tools that are composable and extensible.
longer toolchains are more brittle
Hyrum’s law of complete API
one second solutions
https://www.bitecode.dev/i/110396390/if-this-is-all-true-why-didnt-i-read-that-somewhere-else
developer focus is not a fungible commodity
https://news.ycombinator.com/item?id=20958455
US national security room
https://x.com/ettingermentum/status/1779245872313671708
if your PR sits open for more than an hour, your team has failed you.
, if your PR takes more than 15-minutes to review, you have failed your team.
If you can decompose your large problems down into a series of smaller problems, then the cost of context switching approaches zero.
https://www.bennadel.com/blog/4013-an-opinionated-guide-to-handling-pull-requests-prs-on-my-team.htm
Code is a liability, not an asset. So goal of software engineer is delivering the maximum amount of desired functionality at the cost of the least amount of code complexity, even as desired functionality evolves over time.
Greg Brockman
https://twitter.com/gdb/status/1606485739679932416?lang=en
start with a simple system
https://personalmba.com/galls-law/
monorepo vs multirepo tradeof
https://stackoverflow.com/questions/56990419/multi-repo-vs-monorepo-and-nested-monorepos
observation: With minimum bespoke we can afford more variance across deployments. Also a lower switching cost, arguably
devastating
https://github.com/dwmkerr/hacker-laws?tab=readme-ov-file#the-dead-sea-effect
unrelated changes in a PR
Single responsibility principle is for software, not code changes imo
https://github.com/dwmkerr/hacker-laws?tab=readme-ov-file#the-scout-rule