Insensitivity

4 ms·

1.
by Insensitivity 17d ago
The smooth scroll / animation or whatever it is makes it so hard to read / use
2.
by Insensitivity 3mo ago
Interesting scam, hadn't seen a re-captcha like that before, you'd have to be pretty technically illiterate to follow the instructions
3.
by Insensitivity 5mo ago
No matter what I wrote in the audio profile, AI Studio never followed it, regardless of scene or context. For example, I tried to get a male voice and kept getting female ones. Not sure if it's an AI Studio bug or I was doing something
4.
by Insensitivity 5mo ago
> LLMs are pretty good at picking up the style in your repo. So keeping it clean and organized already helps. At least in my experience, they are good at imitating a "visually" similar style, but they'll hide a lot of coup
5.
by Insensitivity 6mo ago
They could've come out and said "Hey, due to increased demands, we're reducing the limit", but instead they chose to do a rug-pull, in the guise of "off-hour" limit increase, while absolutely butchering the lim
6.
by Insensitivity 6mo ago
Maybe, I do suspect _some_ parts are codegen or source map artifacts. But if you take a look at the other file, for example `useTypeahead` you'd see, even if there are a few code-gen / source-map artifacts, you still see the core
7.
by Insensitivity 6mo ago
the "useCanUseTool.tsx" hook, is definitely something I would hate seeing in any code base I come across. It's extremely nested, it's basically an if statement soup `useTypeahead.tsx` is even worse, extremely nested, a t
8.
by Insensitivity 6mo ago
Funny how before the announcement, people who were experiencing this were being gaslighted on different platforms, to think they have a "skill" issue using Claude Code Additionally, this was practically predicted and expected by s
9.
by Insensitivity 6mo ago
Are you within an organization? they can control which subset of models are available to you maybe it's related to the supply chain risk designation
10.
by Insensitivity 7mo ago
I personally don't mind React, but I do acknowledge, after using it for a couple of years, that it seems to be a magnet for issues. It's the kind of framework, where if you're not writing properly, mostly like [Thinking in Re
11.
by Insensitivity 7mo ago
I was looking at the Meet repository as an example, people literally don't know how to write React, without drowning in `useEffect`, `eslint-disable`, `any`. React has it's issues (and a ton of them), but writing code like this, I
12.
by Insensitivity 9mo ago
As impressive as it sounds, the game is riddled with people cheating
13.
by Insensitivity 10mo ago
I'm not sure if React Native is much different from React itself, but a few things that made me give a side eye, when looking at this write up: 1. The instant 5 levels of providers (and additional one later) seems excessive. 2. The usa
14.
by Insensitivity 11mo ago
I’ve been using jj for a few months now and still love its workflow, but I keep running into the same problem you mentioned. The advantages of jj far outweigh this issue, so I’d really like to figure out a clean way to avoid these conflicts