Goals: Add links that are reasonable and good explanations of how stuff works. No hype and no vendor content if possible. Practical first-hand accounts of models in prod eagerly sought.

Powerline
is a statusline plugin for vim, and provides statuslines and prompts for several other applications, including zsh, bash, fish, tmux, IPython, Awesome, i3 and Qtile.HTTPie
but miss the features of curl
, curlie
is what you are searching for. Curlie
is a frontend to curl
that adds the ease of use of httpie
, without compromising on features and performance. All curl
options are exposed with syntax sugar and output formatting inspired from httpie
.The first post has been published: https://www.swyx.io/writing/cloud-distros
The second post has been adapted for Temporal: https://www.swyx.io/why-temporal/
these are bullet points of a blogpost on a topic i know very little about but i feel like there is something there that is happening as we speak
I've designed a lot of RPC protocols in my career. One pattern that's worked well basically goes as follows:
// Client calls: print('Hello World\n')
-> [1, "print", "Hello World!\n"]
// Server sends return value (or lack of return vvalue)
<- [-1]
// Client calls: add(1, 2)
-> [2, "add", 1, 2]
This is meant to be used as a bookmarklet, where you click it and it'll apply some basic styling rules to the page you're on.
Primarily, this is designed to be used on those old websites that don't have any styling rules, e.g. http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm
A hastily-written strawman for how bare imports could be resolved in browsers — see this convo.
Businesses with high strategic control have more sustainable profitability, stronger competitive advantage, and higher valuations. Many business hit multiple strategic control points, and it's possible for businesses to combine multiple control points, even low control, to achieve a much greater level of strategic control in aggregate.
High strategic control:
A page-rank-like approach to scoring code libraries for quality and dependability. This is a quick-pass attempt at translating metrics we have readily available in the code community into a conversion funnel that might be familiar to marketers.
Conversion funnel equivalent | Metric | Description |
---|---|---|
awareness |
github stars | Equivalent of "likes", but only slightly better than visits (it's possible to have many stars per one visitor). This metric only proves awareness, no causal relationship to actual interest, "real" popularity, code quality, trust, intent to use, or advancement in the conversion funnel. |
interest |
dependents | Dependants are a sign of awareness and commitment from the authors that chose to depend on the library, but no correlation to actual usage, commitment from upstream implementors and users to use the dependent, and is just as likely to represent herd mentality or a reaction to recent awareness as it is to be a p |
# <type>: (If applied, this commit will...) <subject> (Max 50 char) | |
# |<---- Using a Maximum Of 50 Characters ---->| | |
# Explain why this change is being made | |
# |<---- Try To Limit Each Line to a Maximum Of 72 Characters ---->| | |
# Provide links or keys to any relevant tickets, articles or other resources | |
# Example: Github issue #23 |