News for hackers. Stuff that matters.

SnootyMonkey

Re:Why Git is no "good" for AI-generated code on Wednesday April 02, 2025 @11:27AM (#43557770)
You are correct! I removed the Show HN.

Why Git is no "good" for AI-generated code

https://github.com/specstoryai/getspecstory/blob/main/GOOD.md

When AI agents are generating some, most, or all of your code, then occasional git commits of the resulting source code aren't sufficient. You also need a tool that ties the generated code back to the prompts and AI interactions that generated it.Here’s a short technical explainer video of GOOD, a Git companion designed for this:...

( Read More... | 11 comments | 17 points | on HN )
This is an example of regulatory capture. In this case, by the legal profession.

https://en.wikipedia.org/wiki/Regulatory_capture

Re:Ask HN: What developer tools would you like to see? on Monday May 23, 2022 @09:56AM (#31479097)
Such a tool exists. Check out https://hexawise.com/
Re:Crux – open-source answer to Datomic on Sunday April 21, 2019 @06:29PM (#19714988)
Finally!
Re:Unslacking Tideways Company on Sunday October 28, 2018 @11:01PM (#18324735)
As did I. Actually, it never occurred to me that it could have come from anywhere else.
Re:Unslacking Tideways Company on Sunday October 28, 2018 @10:10PM (#18324479)
Shameless plug here, but this is exactly why we built Carrot ( OSS / SaaS https://carrot.io/ )

We've been remote founders and employees in numerous distributed startups, and have always found the same issue, the noisy nature of chat/Slack and lossy nature of email necessitates a 3rd place to keep the important decisions, announcements and history of the company.

Lots of companies use wikis and forum software for this, and those can work, but we're betting that a dedicated solution can work better.

My co-founder and I started building Carrot a few years ago as a result of our experiences at distributed startups. Our biggest challenge was always the same: communicating a clear direction, getting everyone aligned, and then keeping them aligned as conditions and strategy change.

Good leadership requires a real effort at transparency and a commitment to consistent communication. Employees need it, they crave it, they demand it, but it’s hard to do with the tools at hand. Even when leaders want to be transparent they end up communicating in ways that aren’t. Slack is too noisy, email is ignored, and all-hands meetings are unevenly attended and hard to pull off in distributed teams.

Teams, especially distributed and remote teams, benefit from a focused tool for leadership communication. Carrot isn’t focused on the minute-by-minute “where work gets done” of Slack, or the reference minutiae of a Wiki, it’s a place to focus on the big picture, and to make sure that transparent communication about the direction of the team is happening in both directions. It’s also well integrated with Slack.

As part of our commitment to product transparency, we’ve built Carrot as an open source platform ( https://github.com/open-company ). It’s ClojureScript/React on the front-end and Clojure microservices on the back-end.

I would love to hear about your challenges in startup and team leadership! And I’d love to know if you feel like Carrot is on track with what we think are some of the most important features: focused 2-way communications, awareness of who’s seen this, video updates, and deep Slack integration. You can weigh in on our open roadmap or email me directly at [email protected].

And, if you like what you we’re trying to do, I’d really appreciate your support on our Product Hunt launch today. https://producthunt.com/

Shameless plug: Carrot was built to help leaders in remote teams keep everyone on the same page. https://carrot.io/
We happened to have built an OSS / SaaS version of Asynch if you're interested: https://github.com/open-company / https://carrot.io
This is something I've never really thought about, the ethics of reference checks. Is anyone aware of a good guide or thoughtful article on the subject?
Re:Stripe Home on Thursday April 19, 2018 @10:21PM (#16881703)
We've got trials at https://carrot.io

It's not exactly the same as Stripe Home, which looks amazing for an internal project, but Carrot is available to everyone, it's all open source, and we're committed to solving this problem for every company that wants to be the Stripe of their industry some day.

Re:Stripe Home on Thursday April 19, 2018 @10:15PM (#16881678)
Not exactly what you'd hoped for, but there's a GH link for https://github.com/open-company
Re:Stripe Home on Thursday April 19, 2018 @10:11PM (#16881655)
We're built an open source project quite similar to Stripe Home, it's available as SaaS (https://carrot.io) or it's all OSS to host your own (MPL V2 License). Check it out if you'd like: https://github.com/open-company
Re:Stripe Home on Thursday April 19, 2018 @10:06PM (#16881630)
It's interesting, we've talked to a LOT of companies about this as customer research for our SaaS product (https://carrot.io) and 150 is actually where this problem become unbearable. We see this problem first come up consistently at 30 people, become a major problem at ~100 people that starts to get lots of attention inside the company, and becoming a real hindrance and burning issue if not addressed at ~150+.

It's not at all surprising to us that both Stripe and Square have spent a lot of time and money on this problem to support their quick growth past 1,000 people.

Re:Slack is the opposite of organizational memory on Monday February 12, 2018 @06:57AM (#16358095)
This is an important original post, and I wish the Slack community were having these conversations more often and openly.

The original post nails some important issues: companies really need topic focused discussions, intentional, thoughtful writing, not just chat, more asynch so there is time for deep work and time for more thoughtful discussion and replies, and much better, topic-based search.

I believe in the impact of this problem so deeply that a team of us have been working on an open source solution to it for a couple years now. https://github.com/open-company

What we're trying to build is a place for companies to have focused, asynch discussions about the things that really matter, outside the stream of chat. The UI we've come up with isn't "Reddit-like" really, but it's an attempt to supplement Slack with what's missing, and it will evolve as we learn more.

If anyone is interested in trying it out, you can sign up for early access (we'll get you in very quickly) at: https://carrot.io/

Re:Migration from Postgres to Datomic on Friday July 07, 2017 @08:32AM (#14717844)
I'm sure price is still the issue. I bet for the right price Cognitect would be happy to provide the source to a customer.

Note: I too wish Datomic was OSS, just disagree that price isn't the issue. It is.

Re:Kierkegaard’s Rebellion on Sunday October 30, 2016 @09:05PM (#12833565)
Except Camus wasn't driving the car when it crashed. His friend Michel Gallimard was.
Re:Whatever you set the URL to, that HTTP code will be returned on Wednesday January 27, 2016 @05:05AM (#10979231)
https://posthere.io/ implements 451, 420 and 100-103. It also doesn't return an Allow: header for 405.

I opened an issue for that: https://github.com/SnootyMonkey/posthere.io/issues/4

Re:Whatever you set the URL to, that HTTP code will be returned on Wednesday January 27, 2016 @05:01AM (#10979217)
http://posthere.io/ is also OSS and you can run it yourself if you want.
Re:Whatever you set the URL to, that HTTP code will be returned on Wednesday January 27, 2016 @05:00AM (#10979212)
Re:Httpbin – HTTP Client Testing Service on Tuesday September 08, 2015 @03:40PM (#10187766)
Similar to RequestBin is http://posthere.io/

(Disclosure: I wrote it)

Re:A Bitcoin miner in every hand on Tuesday May 19, 2015 @08:36AM (#9569560)
"And can be used by software on your personal device to give you extra functionality without again you having to do anything."

Without you having to do anything but pay for and power a dedicated chip. If the utility of having a tiny amount of BTC on device is so high, and the cost so low, why not just have the device manufacturer pre-load a lifetime supply on the device (purchased or mined in a giant wind powered data center)? Seems the cost of this buying this chip is much higher than just buying the BTC outright for the user.

Re: on Friday January 16, 2015 @07:49AM (#8898500)
Will this be OSS? It's not clear from the website.

Older »