Kris Nova
medium.com/@kris-nova · Personal blog · on HN since 2022
Kris Nova, an engineer formerly at GitHub and Twilio, writes about Kubernetes, systems thinking, running Mastodon and engineering careers.
What HN saysCommenters link her posts on Hachyderm infrastructure and organic versus mechanistic systems as useful reading on how complex, fragile software grows.
15HN people shared it
3linked it in comments
17stories submitted
227story points
4 years agolast shared
2022people per year2026
Most-shared posts
- 1Experimenting with Mastodon Federation and Migrating Mastodon Accounts7 people · 12 points · first shared 2022 · 1 comments on HN
- 2Practical Systems Awareness2 people · 21 points · first shared 2022 · 2 comments on HN
- 3Hachyderm Infrastructure2 people · 8 points · first shared 2022 · discussion on HN
- 4Operating Mastodon, Privacy, and Content2 people · 8 points · first shared 2022 · 1 comments on HN
- 5Creating Value as a Principal Engineer2 people · 4 points · first shared 2022 · 1 comments on HN
- 6Organic and Mechanistic Systems2 people · 3 points · first shared 2022 · discussion on HN
- 7Why Fix Kubernetes and Systemd?1 people · 169 points · first shared 2022 · 117 comments on HN
- 8“What it is” and“What it does” thinking1 people · 2 points · first shared 2022 · discussion on HN
- 9Homepage1 people · first shared 2022
- 10Why i wrote hacking capitalism 5094d26d4fef1 people · first shared 2022
What HN people wrote when they linked it
CharlesW · 2022-11-14
A great article published after I posted this, by Kris Nóva (GitHub, formerly Twilio). She self-hosts hachyderm.io, which currently supports 6,000 users:
https://medium.com/@kris-nova/hachyderm-infrastructure-74f518bc7472
Forward-looking Hachyderm infrastructure requirements: https://hackmd.io/qrR8obReTlaHkQXkHQNXJw
wrycoder · 2022-09-18
You may be interested in this article:
https://medium.com/@kris-nova/organic-and-mechanistic-systems-e576ac47…
What you are dealing with is organically grown software. No one really understands it, and it's likely to be fragile.
I agree with all those here that say the first thing to do is to introduce version control. You don't want to break that money machine without a way to revert.
Second, introduce some lightweight form of code review, but don't tick people off.
Third, if you want to do something like revise the user interface, consider adding an API to the existing organic code base, and build the new UI with that API. Generally, take that approach and avoid jamming something into the middle of the existing code that no one fully understands.
kris-nova · 2022-08-11
Very familiar sentiment to thoughts I have been thinking and feeling over the past year or so. Interesting to see more of this stuff popping up. I am starting to think unionizing is going to be the path to start pointing the majority of folks towards.
https://medium.com/@kris-nova/why-i-wrote-hacking-capitalism-5094d26d4…