Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AI for developers and Google Workspace

blog.google

Post reply on HN
Print view View original

151–160 of 249 posts

Re: AI for developers and Google Workspace

#151

Post by Veen »

ren_engineer wrote: post #84
mabbo wrote: post #48

If I'm following this all here... We're going to have AI help us generate long pieces of text from very small blurbs of information. Then the reader is going to have AI read the long pieces of text, and condense it down into just small blurbs of information. Will my self-driving car also take unneeded detours through pretty places, making it take longer to get where I'm going?

Google is also effectively giving up on Search if they are willing to help people generate more SEO spam at scale by directly providing AI text generation in Docs. OpenAI/Microsoft shook them up so hard that they are doing stuff that is most likely self-destructive long term

AI-generated SEO spam is here regardless of what Google does. But they don't also want everyone to stop using Google Docs because it lacks features that are definitely coming to Microsoft Word and every other competitor.

Re: AI for developers and Google Workspace

#152

Post by politician »

jon-wood wrote: post #4

> So if you’re a manager onboarding a new employee, Workspace saves you the time and effort involved in writing that first welcome email. If you really can't be bothered to write the welcome email maybe just don't, rather than throwing some ML generated drivel as the first impression a new hire gets of your management. The direction this is going in is so focused on automating away the hassle of email, with the end s…

> with the end state surely being that both sides of an email exchange are ML models churning away at each other.

The end-state is an ML model running on a client device in isolation. Why bother using SMTP?

Re: AI for developers and Google Workspace

#153

Post by whoisjuan »

They just keep putting out press releases talking about private betas and tests with "selected trusted partners" but nothing the regular consumer can play with.

If that's the pace at which they're planning to compete with Microsoft/OpenAI, they already lost.

Re: AI for developers and Google Workspace

#154

Post by generalizations »

scottyah wrote: post #150
pxtail wrote: post #127

Earlier quoted context omitted.

Well, that google post probably was written with the help of AI and itself looks like it could benefit from keypoints extraction service, it's full of corporate mumbojumbo with occasional "Select developers can access", "stay tuned for our waitlist soon", "to testers in the coming weeks.", "more to come in the weeks and months ahead." In general, very low energy and conservative compared to bold MS moves

At least somebody is trying to get it right before they ship

Nah. They’re just more scared of failure than they are motivated to capture the market.

Re: AI for developers and Google Workspace

#156

Post by tantalor »

ukuina wrote: post #111

Golly, can you just _imagine_ GPT integration in Google Reader? Overview: "Summarize my tech feed" In an informative article: "Didn't I Star something similar last week?" In a news article: "What does website X think about this event?" The future is bright!

@conesus add to NewsBlur!

Re: AI for developers and Google Workspace

#158

Post by bleuchase »

indymike wrote: post #90
Swizec wrote: post #79

Earlier quoted context omitted.

Less frequent than that and people start forgetting the gripes and inconveniences they need help with. Managers are supposed to work on the system, at least in theory. 1on1’s are for the manager like server metrics are for the SRE. An early warning system of future problems. Ideally you can fix issues before the problem blows up into an alarm.

> 1on1’s are for the manager like server metrics are for the SRE. I'm not sure that is accurate. As a manager, I have a bunch of production metrics on my people. I can tell who's getting work done, who isn't, who has high defect rates in their work, who makes fewer defects, who is positive ROI, and who is not paying their keep. Where the one on ones are useful is when they are informed by the metrics, and those conve…

If you’re only talking to your directs for 10-15 minutes every two weeks you are neglecting your duties as a manager. The standard is 30 minutes 1x week with every direct report.

Re: AI for developers and Google Workspace

#159

Post by yencabulator »

zamnos wrote: post #56
Buttons840 wrote: post #37

Earlier quoted context omitted.

The middle manager thinks, "the time and effort I spend on my job can be automated, yay!", never considering the second order effects.

Fortunately for middle and line managers, the vaunted 1:1 hasn't been automated yet, nor does it scale, so the technology doesn't allow managers to have more than, say, 60 direct report effectively. Meeting with each of them for 1 hour every other week only leaves 20 hours every other week for work that isn't a 1:1. I think middle management will be safe for a little while longer.

Just wait until employees are told to do their 1:1 with a chatbot...

Re: AI for developers and Google Workspace

#160

Post by andrewmutz »

indymike wrote: post #90
Swizec wrote: post #79

Earlier quoted context omitted.

Less frequent than that and people start forgetting the gripes and inconveniences they need help with. Managers are supposed to work on the system, at least in theory. 1on1’s are for the manager like server metrics are for the SRE. An early warning system of future problems. Ideally you can fix issues before the problem blows up into an alarm.

> 1on1’s are for the manager like server metrics are for the SRE. I'm not sure that is accurate. As a manager, I have a bunch of production metrics on my people. I can tell who's getting work done, who isn't, who has high defect rates in their work, who makes fewer defects, who is positive ROI, and who is not paying their keep. Where the one on ones are useful is when they are informed by the metrics, and those conve…

> I can tell who's getting work done, who isn't, who has high defect rates in their work, who makes fewer defects, who is positive ROI, and who is not paying their keep

I've been doing engineering management for ten years and I've never seen a set of metrics that can tell you these things.

What software engineering metrics tell you who has positive ROI?

Post reply on HN