9,137 karma · joined October 7, 2007
But as skills and memory are populated over time, Plan mode isn't as necessary. It becomes simpler to let Claude just build and get something general in place that works, and then refine from there. Auto mode will ask essential questions.
I still use Plan mode for big feature changes, to confirm that I've asked for what I want in the right way. I tend to prompt casually, with only a few specific details. Plan mode helps me see the whole picture before committing. In a few cases, it also helped me decide the feature I asked for was wrong.
I think we can still buy ice, but I don't think we can buy coffee anymore. Coffee was a fun excuse to go to center camp every afternoon.
That's not a long history of pricing fixing, just accusations.
Why are you installing random extensions?
It's simply a clever way to satisfy the current administration's ambitions. Nothing had to change, just the semantics.
Sorry, but all of that is obtuse. The fact that some digital audio can be perceived as much louder than others –– yet it's all limited to the same digital range –– proves they aren't similar at all.
There is no such thing as a standard curve for compression. Source levels vary almost infinitely. Accurately separating and reducing sound after the fact, without turning the whole thing to mud, is considered to be an impossible technical challenge.
Next, TV broadcasters worked on a predetermined schedule with predetermined advertising. This gave them time to inspect and approve ads in advance.
Streaming ads are generally served just in time from third-party services to the streaming host. FFMPEG gets the output from the stream host, but the host has to combine content together from multiple sources (entertainment + multiple ad servers) into that single stream. Currently, sound-level is completely at the whim of each ad server, as well as each ad producer. Meanwhile, the final output is at the whim of the streaming host: 24-hour-news streaming sites probably have different audio standards than Apple TV+.
Ultimately, AI could potentially be used to solve it, since it can generate / make-up new sounds as part of reverse-compression. But it would still have to be done in advance by the third-party ad servers.
To verify your request, follow the instructions below Use the keyboard in this order:
1 Press ⌘ Command HOLD + Space TAP 2 Press Terminal + Enter 3 Press ⌘ HOLD + V TAP 4 Press Enter TAP
And if your company has any web presence or apps, you usually can't cherry pick which browsers your customers can use. That means some portion of your company will need access to other browsers for QA purposes.
But if they all use Chrome, wouldn't those be really weak ad blockers?
Same here, but only on Chrome. Firefox works fine.
> You write up what you learned in an interesting, useful and persuasive way.
Very curious (and appreciative) that some company cultures allow this. I haven't had such experience (although I work in a parallel role). It's usually just grinding out tickets.
Sorry, that's simply not true. The tech was ahead of its time. The implementation was intuitive. Only developers and Steve Jobs hated it, because Flash made it way too easy for anyone to make something fun.
By the time mobile could run Flash, it was too late. Between Apple & Adobe, it had no shot of making the transition. But before that, Flash was pretty amazing.
Billions of people enjoyed using Flash for games, video, music, and animated entertainment.
I'm currently working on a responsive app in Swift and had to develop my own responsive layout system. SwiftUI simply isn't up to the task, except for one very specific, generic layout.
Tangential: it's always made me wonder about teams that believe "80% effort" is optimal.