make has a ton of useful stuff for detecting build changes, but with go, it’s not *as* big of a concern, so more simplistic justfiles work really well imo
make has a ton of useful stuff for detecting build changes, but with go, it’s not *as* big of a concern, so more simplistic justfiles work really well imo
Devs can scrape, at least an API key you can track usage and charge appropriately 😉
Devs can scrape, at least an API key you can track usage and charge appropriately 😉
Is it a chart?
Is it a chart?
“What caused that massive spike in downloads? Oh, a spike in Bluesky refereed downloads that day”
“What caused that massive spike in downloads? Oh, a spike in Bluesky refereed downloads that day”
- it never finishes loading
- even once loaded, a cache is used. Clicking refresh does a hard pull. I modified my internal user filter as a demo.
Solution here is probably “let it load, then click reload if still persists”
- it never finishes loading
- even once loaded, a cache is used. Clicking refresh does a hard pull. I modified my internal user filter as a demo.
Solution here is probably “let it load, then click reload if still persists”
I don’t believe Go gets much benefit from file-awareness. Might be helpful for building frontend? My prod is built in ci docker, though.
Plus, “just run” is way more fun than “task run” 😝
I don’t believe Go gets much benefit from file-awareness. Might be helpful for building frontend? My prod is built in ci docker, though.
Plus, “just run” is way more fun than “task run” 😝