Explore >> Select a destination
|
You are here 
|
stevelosh.com | ||
| | | | |
ezyang.github.io
|
|
| | | | | When designing changes, it is important to keep in mind what parts of the system you can change and what parts you cannot. For example: If you expose a public API, you should prefer not to make a BC breaking change to the API, even if it would make your life easier if the API was different. If you interact with an external system, you have to conform to the API that actually exists, not some wishful thinking version that directly gives you what you want. | |
| | | | |
haacked.com
|
|
| | | | | Working on multiple branches simultaneously? I built tree-me to manage git worktrees without the ceremony. Convention over configuration for the win. | |
| | | | |
tarneo.fr
|
|
| | | | | Programming, Linux, self-hosting, ergo keyboards, IT ethics... | |
| | | | |
blog.dataumbrella.org
|
|
| | | |||
