_sharp

7 ms·

1. 1.▲
   by _sharp 28d ago

   Haven't tried it yet, but they just added a concise mode https://x.com/ClaudeDevs/status/2090245922685063634
2. 2.▲
   by _sharp 5mo ago

   Right, just like all the productivity lost when people stopped using paper ledgers to mess around with these so-called 'databases'
3. 3.▲
   by _sharp 11mo ago

   The point of the article was to choose your language based on economic impact, rather than technical debates that are a facade of an engineer's identity beliefs. With that pov, I don't see any contradiction by saying the language
4. 4.▲
   by _sharp 1y ago

   You should consider documenting your durability requirements, failure modes, important context related to the feature/component your working on, as you would a junior engineer. Then, you can re-use the context documents. If the AI doe
5. 5.▲
   by _sharp 1y ago

   This is amazing! Thank you!! The quickfix window is so small, so I added the "-c only" option to make it the only window that first pops up. Then made it a function so it's easier to call: ``` vgrep() { rg --vimgrep &quot
6. 6.▲
   by _sharp 3y ago

   Our team recently adopted the Diataxis framework, I guess. We followed this guide: https://documentation.divio.com/ We've been referring to it as the Divio system though, which appears to be the same thing.
7. 7.▲
   by _sharp 7y ago

   I've used RocketChat at a previous company, basically a clone of slack. I didn't have to manage it, but it seemed to work great.