ccwilson10

Not related to the Hume team in any way, but I couldn't help laughing throughout most of my conversation. Seems like a seismic shift that felt straight out of HER.

Was honestly blown away by the responsiveness of the chat. At risk of getting carried away... I can't imagine this being anything short of a game-changer?

Also, any ideas how it responds so quickly to conversation? Seems like GPT 3.5-level speed with the awareness of 4+.

Can check out https://signalgtm.com and https://simplyput.ai, two players in the space

I used this but, upon asking which model it is, it replied as being a "fine-tuned version of GPT 3.5". Any clue why? In a second chat it replied "You're chatting with one of the fine-tuned versions of the OpenAssistant model!".

Posthog has a strong emphasis on developers, with features like feature flags and upcoming warehouses / CDP.

Flywheel is focused on go-to-market teams and non-technical users.

They have this via Jira Work Management

Nice to see you here too, Sascha :)

www.theflywheel.app

Product description: Flywheel is instant analytics for product-led growth (aka freemium or free trial products). You'll learn which marketing tactics drive in-app product adoption with zero configuration after integrating a data source. Recent companies have onboarded in <3 minutes if they use Segment / Intercom, or <1hr to install our custom Flywheel.js tracking script.

Testing: Sign up is free with no CC. We want to validate that our calculations work for a wide variety of use cases and event formats, and learn how much value the tool can provide for smaller companies with few, or no, data analysts.

Contact info: You can ping me directly at [email protected] or use Intercom inside the app

Wife is a dentist. There certainly are practices where treatments are recommended as a function of money and cashflow (laser treatment and other "optional" treatments are a great example of this). However, crown / cavity recommendations are largely dependent on how aggressive that particular dentist's philosophy is. E.g. my wife only goes to her father for treatment because he focuses on saving teeth whenever possible.

Unlikely that a dentist would ever recommend filling cavities if they didn't believe it was necessary – they're not very profitable for practices. Crowns are sometimes recommended when a filling will suffice, but that's usually because crowns last ~10 years and fillings only delay the inevitable crown for a few years.

I wish HN was like this more often

Not sure if this is intentional, but anyone can watch this stream and the content is... sometimes questionable.

Totally, I'll bring it up with some people post-break! The JSW marketing team is really open to any kind of work that'll help product usability. Interesting fact, a couple of them are actually prior Jira Admins.

Haha fair enough. The issue will be, and currently mostly is, the effect you see on performance at scale. Small instances don't have instantaneous interactions but they're still much faster. Here's a quick video (https://imgur.com/a/8ZJrhMZ) of a dev instance (slower than prod) with the new feature. Loading of this view feels way faster than the board does.

The work I'm doing is separate from the performance improvements, so hopefully the two initiatives combined will get us a lot closer to what you're asking for! Again, we'll have to see what it looks like in production at scale, but I'm optimistic it'll be a much better experience.

Whew. At 8 seconds I'd probably call for the tool to be removed. I had a similar experience while at Atlassian at one point and then we found a way to speed up the (Jira Core) boards by ~5 seconds after changing some JQL for the board logic. That change should be in effect for your org but you'd need to use Classic Business projects.

Fun fact, next-gen might actually be a reason why your instance is running slower. A side-effect of NG can be the slowdown from each project with its own custom fields and that effect multiplied hundreds of NG projects across an organization. Then (I think), when loading your project it calls all the fields to see which fields it should show. Not an ideal rec, but I'd check out Classic projects and see if that speeds things up for you and your org.

Speeding up Jira Cloud is a top priority for Atlassian this year so you should see some improvements coming. I'm working on a new view right now in Jira and we've been able to load about 100 issues in ~1-2 seconds. It lazy loads, but we can flip through 500 easily once you've scrolled to the bottom. Should be able to get that in your hands this coming year.

I honestly wish it was that simple for us but convincing management is a fairly sales-driven approach and our marketing model is heavily self-serve. We do have a product called Jira Align that's targeted closer to what you're describing. I'd attribute more of the spread to the concept of "Jira is the defacto" fwiw.

Chuckled at convincing managers to track less data. Internally we subscribe to a "less is more" approach and try to limit required fields as much as possible. I bet we feel more willing to contact Jira admins to make changes, though, since we own the product itself.

Concur that migrating away from Jira is tough and probably helps keep people in the ecosystem. I haven't met anyone at Atlassian, though, who ever wanted that to be the reason why people stay. I think Jira can be awesome when it's set up well but some stakeholders can get a bit, uh, heavy-handed when deciding on "the process".

Good point, not sure why we don't make more of a fuss about it. I think there should be some content about how our HR teams use Jira coming out soon so that could be a good first step.

Ironically, I was part of the group that just did the first ever official Atlassian Twitch stream the other day! Seems like an easy way to fire off content without needing a lot of approvals and checks. I'll chat with some people on the marketing side to see how hard it would be to just walk through our own setups. Saw this in a comment somewhere, but confirming we have a culture where process and setup are determined mostly on a department-by-department basis (at least for the non-tech side of the house). Our Marketing org generally works in an "agency" model where there are teams responsible for specific marketing disciplines (SEO, Video, Branding, etc etc).

Just on a side note, I'm happy to walk you through how we use it personally — Zoom, email, or whatever. Always trying to learn how we can make Jira better and try to share advice where I can.

[Current Atlassian employee here] This might be biting off more than I can chew, but if anyone has tangible ways they think Jira can be improved for non-tech team members I'd love to hear them. Happy to chat via email or Zoom about them and try to add some of the fixes into the upcoming roadmap.

Welp... fun fact, every team (even the non-tech teams) uses Jira so I'll happily send over my venmo account :p

This was great! Loved it and the time per level felt good as in I wasn't inordinately stressed. Got to 249 the first time but had some scares for sure.