Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kschrader
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
kschrader
10mo ago
Also stuck in this endless loop.
2.
▲
by
kschrader
1y ago
One other note: We've seen teams where people are now using Korey as the main surface to their work tracking tool. They show up in the morning and say "what was I working on yesterday?" "what else do we have to do in thi
3.
▲
by
kschrader
1y ago
I'm not 100% clear on what the scope of ChatPRD is at this point (beyond PRDs) but Korey has a fleet of specialized subagents running underneath for everything from status updates to writing specs to breaking them down into subtasks to
4.
▲
Korey: AI Product Manager
(korey.ai)
14 points
by
kschrader
1y ago
|
4 comments
5.
▲
by
kschrader
1y ago
Hi all, we started an experiment a few months ago to see if we could build an actual useful PM agent for software teams, and I think that we've come up with something pretty cool. Korey can take your ideas, flesh them out, and then bre
6.
▲
Show HN: Korey – a product management agent for software teams
(korey.ai)
7 points
by
kschrader
1y ago
|
2 comments
7.
▲
by
kschrader
1y ago
The Anthropic models are running underneath everything (Claude Code, Windsurf, Cursor, etc). Whenever someone is using MCP they (in the generalized case, until now) ultimately end up using Anthropic as their LLM and Anthropic gets paid when
8.
▲
by
kschrader
2y ago
For reference: https://www.pivotaltracker.com/blog/2024-03-12-subscriptions...
9.
▲
by
kschrader
3y ago
Having spent 7 years now building https://www.shortcut.com/ it's very clear to me that at a certain point in the life-cycle of many organizations a bunch of people get hired who can only "think in Jira" and t
10.
▲
by
kschrader
3y ago
As soon as we add a new feature to Shortcut people inevitably use it in a way that's complex and unexpected and that causes a large portion of the team to hate it. It's a very hard dance to do.
11.
▲
by
kschrader
4y ago
Depends on the size of the organization using it. It is until you hit the wall on it and then you end up with a lot of tough tradeoffs.
12.
▲
by
kschrader
4y ago
One of the big problems here is that there's no agreed upon mental model for how people think about the pieces fitting together (and I don't think that we could come up with one that would work for everyone). Even if people do hav
13.
▲
by
kschrader
4y ago
Maybe it's just me, but other than ad-free articles what value does Blue bring to the table? (Just an edit button?) Anyone here paying for it and feel like they're getting their money worth?
14.
▲
by
kschrader
6y ago
We do a lot of work at Clubhouse to keep things fast. We have alerts set up that fire if the p50 or p95 of certain actions spike and we treat it as a bug if things are headed in the wrong direction. We still see a lot of random cases of thi
15.
▲
by
kschrader
7y ago
Just to clarify, we think a lot about product managers, but when there's a tug-of-war between making life easier for developers vs making life easy for PMs we lean towards the former.
16.
▲
by
kschrader
7y ago
One of the lenses that we look at things through when making product decisions is making it hard to do things that end up feeling like paper cuts for developers all day long. I've always seen Jira as the "manager's tool"
17.
▲
by
kschrader
9y ago
I'd argue that we're stretching a bit with the word "need" here. Are we still at the point where every software development team has to come up with their own special process? I feel like, as an industry, we should be mo
18.
▲
by
kschrader
10y ago
One thing that we've built[1] is a way to hook a Branch to a story (by including the story ID in the branch name, which also starts it) which causes all of the commits on the branch to feed into the ticket and allows you to use Pull Re
19.
▲
by
kschrader
10y ago
"Something along the line of themes" is coming soon...
20.
▲
by
kschrader
10y ago
Perhaps you confused "it feels like" (implying that it feels bloated with many esoteric and/or generally useless features) with the statement "there's literally never been a feature that they've said no to"
21.
▲
by
kschrader
10y ago
To be fair, they did say "no" to this. (After 11 years. :-) )
22.
▲
by
kschrader
10y ago
Agreed. It feels like Atlasssian never met a feature request that they didn't say "no" to. Unfortunately, most of the tools out there don't scale well, so most teams reach the point where Jira is the only reasonable choi
23.
▲
by
kschrader
10y ago
Just for comparison purposes, once a large portion of your housing is safety deposit boxes here's the sort of thing you can get for $300K: http://streeteasy.com/building/5-tudor-city-place-new_york/3... 275 s
24.
▲
by
kschrader
10y ago
It literally says in the article that Hastings fired the Chief Talent Officer that came up with the "Would you hire them again today?" litmus test that they use because she no longer passed it.
25.
▲
by
kschrader
11y ago
Is the install base for high-end PCs (of the level needed to push an Oculus) really larger? They've sold 36 million PS4s. An Oculus needs a Nvidia GTX 970 or better graphics card (which goes for $300+ on it's own). I highly doubt
26.
▲
by
kschrader
11y ago
We're focusing on teams of 3-150 developers right now. We have some of the building blocks in place for bigger teams, but it's not a priority right now.
27.
▲
by
kschrader
11y ago
The software is built so that we can ship an on-prem version at some point in the future, but we don't have the processes in place yet to make that a reality. Nothing planned yet, but if there's enough interest we'll consider
28.
▲
by
kschrader
11y ago
It's on the list of things to do at some point soon. Here's a blog post that one of our users wrote a few months ago that covers some of the same ground: https://medium.com/humans-in-space/clubhouse-is-the-bes
29.
▲
by
kschrader
11y ago
We tried to price things fairly but still make enough to grow and invest in the what we're building. PT uses tiered pricing, so if you have 16 people we're only $10 more a month than PT and at 26 people we're $40 less expensi
30.
▲
by
kschrader
11y ago
We tried to use rather generic agile terms. Here's a reference to most of the same concepts on the Jira site, for instance: https://www.atlassian.com/agile/delivery-vehicles/ (I've worked with Pivotal on
More ›