So, our commit notifications in hipchat all come from the same user(s) who pushes changes to master.
So, our commit notifications in hipchat all come from the same user(s) who pushes changes to master. You can't always tell who made the commit, and not all commit messages are informative. And even then, not everyone religiously watches chat or issue boards, so monitoring what your teammates are doing using that mechanism doesn't work for everyone. And in a multidisciplinary team, standups help with cross-pollination. I'm an ops guy, but in standup I find out what the design guy is doing. He doesn't commit to a repo that posts notifications, but I get an idea of where future ops work is going to land. If standups don't work for your team, don't do them. But they're not an anti-pattern.
Posted by vacri on Apr 8, 2015, 2:56 AM
Tags
Related issues
- The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
- The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
- (My comment is about detached houses).
- The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
- > steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
- Why is there no comparison with FLUX 3 Image?
Raise real-world problems, find people facing the same issue, and discuss solutions.7,000 issues0 comments
hackernews (Other)
The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
(My comment is about detached houses).
The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
> steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
Why is there no comparison with FLUX 3 Image?
> our Git monorepo was developing an annoying problem Sentences like this are so common from people using monorepos that I am convinced ...
Why is there no contact form?
So, our commit notifications in hipchat all come from the same user(s) who pushes changes to master.
So, our commit notifications in hipchat all come from the same user(s) who pushes changes to master. You can't always tell who made the commit, and not all commit messages are informative. And even then, not everyone religiously watches chat or issue boards, so monitoring what your teammates are doing using that mechanism doesn't work for everyone. And in a multidisciplinary team, standups help with cross-pollination. I'm an ops guy, but in standup I find out what the design guy is doing. He doesn't commit to a repo that posts notifications, but I get an idea of where future ops work is going to land. If standups don't work for your team, don't do them. But they're not an anti-pattern.
Comments (0)
No comments yet. Start the discussion.