Hacker Newsnew | past | comments | ask | show | jobs | submit | joeldo's commentslogin

That's no longer the case - a large portion of teams are now using cloud variants of Confluence/Jira.


> There’s more details here than I can explain today, but you can use the QR code to find a detailed article, including the documentation we use for the skills.

Why not just provide a clickable link given this is an article on the web?


> This is a transcript of my keynote presentation for the Regional Scrum Gathering Tokyo conference on January 8th, 2025.

Because the images are slides from a presentation that the audience could scan.

>Thank you for listening.

The text of the article appears to be the "talk-over."


The clickable link is in the right margin just underneath the (first) QR code image:

https://www.jamesshore.com/v2/blog/2024/update-on-software-e...


The impact of this will be profound!

Obviously bugs are inevitable, but why this wasn't progressively rolled out is beyond me.


My understanding is that multiple recent versions are affected.


Yeah, progressive rollout would have dramatically reduced the impact, I think that should be mandatory for any of these systems.


I think there is some confusion with the term 'public' here.

The Graphql server itself is still publicly exposed to the internet, but the ability to query is not. Queries have to be whitelisted ahead of time (persisted queries).


You can review the bash script first. Regardless, they provide a few different installation options https://zed.dev/docs/linux


I guess the difference is ChatGPT is less likely to cause death if it makes a mistake.

Users generally have time to decide if the output ChatGPT provides is accurate and worth actioning.


At this point, I'd be surprised if ChatGPT has not yet given someone a response which caused them to make a mistake that resulted in a death.

We found out about the lawyers citing ChatGPT because they were called out by a judge. We find out about Google Maps errors when someone drives off a broken bridge.

https://edition.cnn.com/2023/09/21/us/father-death-google-gp...

For other LLMs we see mistakes bold enough that everyone can recognise them — the headlines about Google's LLM suggesting eating rocks and putting glue on your pizza (at least it said "non-toxic glue").

All it takes is some subtle mistake. The strength and the weakness of the best LLMs is their domain knowledge is part way between a normal person and a domain expert — good enough to receive trust, not enough to deserve it.


"Better" depends heavily on the parents.


Closing down within a year of it finally becoming profitable.. That would be a plot twist!


But also not out of the question for Google, who don't seem at all rational about what they kill vs let live.


75 / (1/6) = 450. Still very exciting!


You forgot the 40 workers vs 1 worker.


The way I read it, it was taking that amount of time before they split it into workers.


Correct, it was 75 minutes total compute time. That was spread across workers to make the walltime more reasonable


Indeed, I really need to improve my reading comprehension.


The one joy I have while using Azure :)


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: