fumplethumb
Joined 10 years ago
Karma
79
Submissions
52
Member since
Jul 8
brian [at] vskr.net
View on Hacker NewsRecent submissions
Comment · 4 hours ago
https://ampcode.com/ is amazing! Surprised the community here does not discuss it more.
Comment · 1 month ago
I appreciate the link.
Comment · 5 months ago
https://www.getoutline.com is pretty good!
Comment · 1 year ago
Just added my email to my profile. Feel free to shoot me an email!
Comment · 1 year ago
DISCLAIMER: I work on the SIG Connect app.
SIG Connect does exactly that: https://www.sigsauer.com/sigconnect
I suspect, since this is HN, you're looking for something more open and hackable. But you might want to check out SIG Connect if you just want something that works out of the box.
Sorry I can't get into "how it works". Feel free to DM me for any questions.
Comment · 1 year ago
Most other places are closed. Chinese restaurants are typically open on Christmas!
Comment · 1 year ago
How about humanitarian toolbox? https://www.htbox.org/
Comment · 2 years ago
What about… GitHub, Gitlab, Gitkraken, GirButler (featured on HN recently)? The list goes on forever!
Comment · 2 years ago
With Docker compose, there is a more idiomatic way to achieve this with zero dependencies using healthchecks[0]. Works well!
I used wait_for_it.sh for the purpose described in the OP until I found healtchecks could be used instead.
[0] https://github.com/peter-evans/docker-compose-healthcheck
Comment · 2 years ago
One thing I see missing from some other replies to your comment is a discussion of determinism. That is given the same input, always produce the same output.
Determinism is often valued in safety critical systems. The system can't work _sometimes_. The system can't even work correctly _eventually_. It must produce the desired result in the time allotted. Actuating the thing 20ms too late could be as bad doing it incorrectly depending on the application.
I'm no ML expert, but that seems to be a problem for those types of solutions in some spaces.
Comment · 2 years ago
We’ve had some success with similar methods. In addition to the simplicity(it just “plugs into” the existing board), it’s nice to get metrics on the bottlenecks happening on the product side of things. If we can show that it historically takes 2 weeks to refine requirements, we can tighten up our estimates and shine a light on potential problems occurring there. If you only have metrics on the dev work, the more business-minded folks tend to focus improvements only on what they can measure.
I’ve also found that folding product workflows into the Kanban board gives the team more visibility and ownership over that end of the pipeline. We can observe how those items age before it ever gets to the dev team and swarm to fix things as a team earlier in the process.