Needs more bots.
Watching AI drive Microsoft employees insane
91–100 of 580 posts
Re: Watching AI drive Microsoft employees insane
#92>I can't help enjoying some good schadenfreude
Fun facts schadenfreude: the emotional experience of pleasure in response to another’s misfortune, according to Encyclopedia Britannica.
Word that's so nasty in meaning that it apparently does not exist except in German language.
Re: Watching AI drive Microsoft employees insane
#93Malicious compliance should be the order of the day. Just approve the requests without reviewing them and wait until management blinks when Microsoft's entire tech stack is on fire. Then quit your job and become a troubleshooter on x3 the pay.
Might as well when they’re going to lay you off no matter what you do (like the guy who made an awesome TypeScript compiler in Go).
Re: Watching AI drive Microsoft employees insane
#94reddit may not have the best reputation, but the comments there are on point! So far much better than what has been posted here by HN users on this topic/thread. Anyway, I hope this is good fodder to show the limits (and they are much narrower than hype-driven AI enthusiasts like to pretend) of AI coding and to be more honest with yourself and others about it.
> reddit may not have the best reputation
reddit is a distillation of the entire internet on to one site with wildly variable quality of discussion depending upon which subreddit you are in.
Some are awful, some are great.
Re: Watching AI drive Microsoft employees insane
#95Earlier quoted context omitted.
Depends on team but seems management is pushing it from https://news.ycombinator.com/item?id=44031432 "From talking to colleagues at Microsoft it's a very management-driven push, not developer-driven. Friend on an Azure team had a team member who was nearly put on a PIP because they refused to install the internal AI coding assistant. Every manager has "number of developers using AI" as an OKR, but anecdotally most d…
The question is who is setting these OKRs/Metrics for management and why? It seems to me to be coming from the CEO echo chamber (the rumored group chats we keep hearing about). The only way to keep the stock price increasing in these low growth high interest rate times is to cut costs every quarter. The single largest cost is employee salaries. So we have to shed a larger and larger percentage of the workforce and th…
Yep. I heard someone at Microsoft venting about management constantly pleading with them to use AI so that they could tell investors their employees love AI, while senior (7+ year) team members were being “randomly” fired.
Re: Watching AI drive Microsoft employees insane
#96I’m all for AI “writing” large swaths of code, vibe coding, etc.
But I think it’s better for everyone if human ownership is central to the process. Like I vibe coded it. I will fix it if it breaks. I am on call for it at 3AM.
And don’t even get started on the safety issues if you don’t have clear human responsibility. The history of engineering disasters is riddled with unclear lines of responsibility.
Re: Watching AI drive Microsoft employees insane
#97>I can't help enjoying some good schadenfreude Fun facts schadenfreude: the emotional experience of pleasure in response to another’s misfortune, according to Encyclopedia Britannica. Word that's so nasty in meaning that it apparently does not exist except in German language.
+1 to the Germans for having linguist honesty.
Re: Watching AI drive Microsoft employees insane
#98Earlier quoted context omitted.
> How are people reviewing that? 90% of the page height is taken up by "Check failure", Typically, you wouldn't bother manually reviewing something until the automated checks have passed.
I dunno, when I review code, I don't review what's automatically checked anyways, but thinking about the change/diff in a broader context, and whatever isn't automatically checked. And the earlier you can steer people in the right direction, the better. But maybe this isn't the typical workflow.
It's a waste of time tbh; fixing the checks may require the author to rethink or rewrite their entire solution, which means your review no longer applies.
Let them finish a pull request before spending time reviewing it. That said, a merge request needs to have an issue written before it's picked up, so that the author does not spend time on a solution before the problem is understood. That's idealism though.
Re: Watching AI drive Microsoft employees insane
#99Interesting that every comment has "Help improve Copilot by leaving feedback using the or buttons" suffix, yet none of the comments received any feedback, either positive or negative. > This seems like it's fixing the symptom rather than the underlying issue? This is also my experience when you haven't setup a proper system prompt to address this for everything an LLM does. Funniest PRs are the ones that "resolves" t…
> How are people reviewing that? I agree that not auto-collapsing repeated annotations is an annoying bug in the github interface. But just pointing out that annotations can be hidden in the ... menu to the right (which I just learned).
or press “a”
Re: Watching AI drive Microsoft employees insane
#100I find it amusing that people (even here on HN) are expecting a brand new tool (among the most complex ever) to perform adequetely right off the bat. It will require a period of refinement, just as any other tool or process.
People have grown to expect at least adequate performance from products that cost up to 39 dollars a month (* additional costs) per user. In the past you would have called this a tech demo at best.