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

This looks interesting, anyone tried it yet?

Is this significantly different that the subagents that are already in CC?

Think of it as Just-In-Time context injection/enhancement

That’s a separate tool though. You don’t want to have to open another terminal to git diff every 30 seconds and then give feedback. Much better UX when it’s inline.

My main hooks are desktop notifications when Claude requires input or finishes a task. So I can go do other things while it churns and know immediately when it needs me.


I had this exact experience. Growing up I had nothing but good memories of reading Dilbert over my breakfast cereal, and then laughing as I got into the workforce and realized how accurate the satire was. And then seeing what "he" was actually like just completely threw me for a loop.

I had an opposite experience. I found his comics not-funny when I was a kid, but then as a grown-up who had worked in a corporate environment, I found many of them funny.

I had 100% the same experience. I thought they were stupid when I was young, after working in an office for a year or two I thought they were peak humor.

At some point he had a mailinglist called Dogbert's New Ruling Class (DNRC) which would soon come to rule the world. In it he wrote lots of really weird, unhinged, occasionally funny stuff. At the time I thought it was all one massive joke, layers of irony and trolling. But more recently I've been wondering if he was actually serious.

I still read coworkers as "cow-orkers"

If you could share any links to DNRC related content, I'd love to see it. Can't find anything online, just broken links.

This is cool but like...a docker container running locally works fine too?


So this article itself is literally content chunking.

> So you end up with short paragraphs, sometimes with just one or two sentences

The average number of sentences per paragraph in the article is... 2.4


Most of it seems fine, although eating even more meat than we already do is a bit perplexing.

The new "guidelines" for alcohol are pretty laughable though. I say that as someone who enjoys his fair share of beers. “The implication is don’t have it for breakfast," <- direct quote from celebrity Dr Oz during the press conference.


Steve Jobs died 14 years ago. If we're attributing this to those in charge, Jony Ive's departure is much more correlated.


Apple's UI design started going downhill with the iOS 7 "flat design" release which was very shortly after Steve's death, and seemed to correspond to Ive being given a little too much free rein in the leadership vacuum that followed.

Jobs had his own flaws, but he was definitely a huge part of why Apple's UI design (and product design in general) has historically been as good as it has.


> Apple's UI design started going downhill with the iOS 7 "flat design" release which was very shortly after Steve's death, and seemed to correspond to Ive being given a little too much free rein in the leadership vacuum that followed.

This was so obvious to me. The damage done to Apple by losing Jobs as their most vicious editor was almost instantly noticeable.


I agree. Jobs being around for the birth of the GUI probably played a big role in that. Pushing past text-based terminals to graphical interfaces meant having to spend every moment thinking about purposeful interaction and design.


Maybe we could use Vison Pro to recreate a visit to Xerox Parc in 1979 to inspire the current designers to use UI patterns that gave been working well for fifty years.


Pretty sure iOS 7 was regarded as awful on launch and then a little while later people decided it was amazing and lovely to look at once the kinks were ironed out.

People just don't like new things that change what they are used to.


Apple spent the next several years walking lots of the changes back, in particular the thin text and overdone translucency


One thing I'll definitely give Apple is that they have walked back some design decisions that were total flops in the past, such as the butterfly keyboard and the touchbar (though I found it more than a bit annoying when I'd see reviews saying how great and visionary Apple was for simply undoing bad decisions - it deserved an "OK, good" not an "OMG Apple is amazing!!)

I like this article because it points out how undeniably awful some of these decisions were in a "this signifies something is seriously, fundamentally wrong with Apple design" way. I really hope Apple listens a does a major course correction.


Count me as someone who never turned around on the iOS 7+ flat design being a usability degradation.


> then a little while later people decided it was amazing and lovely to look at

Sorry, who decided this? Which people exactly?


Alan Dye designed IOS7 as well.


iOS7 was great; it had mistakes but they ironed them out. Aqua under Jobs had mistakes too... OS X was hated at first.

Apple often took bold steps and then improved things.

But Liquid Glass seems like a step in the wrong direction.


Jony Ive’s elevation was the problem: neither he nor his protege Alan Dye (who worked on the boxes) had UI training or experience and that has shown since iOS 7 where the focus shifted to things which looked nicer on the side of the iPhone box than they are in actual use - stuff like Liquid Glass shipping with an illegible lock screen keyboard is possible because they never put the lock screen in a presentation or product screenshot.

As a complete outsider, my impression is that this started slow because they had to politically overpower Apple’s actual UI group. Liquid Glass probably managed that with a unified look across all devices pitch which should’ve weighted the relative impact on the popular platforms much higher than the niche Vision Pro.


Yea. Nobody wants to be a full-time code reviewer.


Hi it's me, the guy who wants to be a full-time code reviewer.


If you really did that full time and never wrote code, you’d be a terrible reviewer.


This is fine for us who've been building code by hand for many years before the advent of LLMs but it's definitely going to be a problem going forward.


strong +1 here :-)


Be careful what you wish for.


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

Search: