1
Write libraries instead of services, where possible
For any developer with limited resources, this means a library (where viable) can provide the same functionality to the user, at a lower cost to the developer than a service.
¯\_(ツ)_/¯
Contact me via email or Twitter , or guess my username on other platforms. Send me questions, comments, random links, requests, thoughts, compliments, complete nonsense, etc.
- Popular posts
- 7
- Total points
- 1,993
- HN comments
- 1,656
- Rank
- #843 personal
Visit catern.com → On Hacker News Oct 2014 – Mar 2023
Software Engineering 6Systems & Performance 5Infrastructure & DevOps 2History & Retro Computing 1
2
You need to be able to run your system
"Run the unit tests" doesn't count. The complexity of your system is in the interactions between the units.
3
The Unix process API is unreliable and unsafe (2021)
It is difficult to write software which reliably and safely manages processes on Unix; this is because of flaws in the API. I know of no Unix system which has solved these problems, but in this article I'll be specifically talking about the Linux process API.
4
Your computer is a distributed system
Many have observed that today's computers are distributed systems implementing the abstraction of the shared-memory multiprocessor. The wording in the title is from the 2009 paper " Your computer is already a distributed system. Why isn't your OS? ". Some points from that and other sources:
5
Terminals Are Weird
Terminals 1 are quite weird. Most modern users assume that they can just have straightfoward keybindings. Right? To bind Ctrl+i to something, they listen for Ctrl+i in their application. If they want to bind Ctrl+Shift+i to something different, they certainly can, they just listen for Ctrl+Shift+i as well. Naturally…