1
point
gijoeyguerra
Joined 51 karma
[ my public key: https://keybase.io/joeyguerra; my proof: https://keybase.io/joeyguerra/sigs/mXact8bLuHcFG7Ii7vBlExK4U5rWoqnETeFE0dek-a4 ]
- Do these ad sites make money?
- I’m always skeptical when I see (or say for that matter) phrases that start with “just”.
- Cool.
- Yes.
- Make it do TDD. That'll slow it down.
- Yes.
- In 2006 when changing code that had lots of inheritance.
- There’s also git daemon.
- Would you care to share what you use it for? Im just super curious because it seems like the industry moved on from chatops and hubot around 2017.
- I have confirmed that at least three people are using it. I don’t trust npm download numbers.
I personally use it a lot for the same use cases people use postman.
- Thanks. It’s been cool to work on it.
- Created a Service Discovery script and adapter for Hubot to enable horizontal scaling of Hubot instances. Simpler and less powerful than the Redis Backplane.
- Leveraged Redis Consumer Groups to create a backplane for Hubots - enabling horizontally scaling Hubot instances.
- 13 points
- Um. This is awesome?
- It's always been the bottleneck.
- Does anyone else find it funny that LLMs need a protocol to execute tooling? Like, it understands language, right?
- I've always deleted tests. I've never heard anyone say not to delete tests.
Wide events as a strategy is expensive, even with sampling, and doesn’t address the fundamental problem - why do we log messages?
I was hoping the article would enumerate why we log messages. Nailing down those scenarios first will lead to a happy life.
Why do we log? - proof of life - is the system running? - what is the state (in memory) when an error occurred? - when did an error occur? - do I need to get up at 2 am and fix something? - what do I need to fix?
I feel like every team operating a system has their own reasons for logging.