626 karma · joined August 21, 2014
Taste is subjective. Having 1 million todo apps, great. Maybe someone I know will find one they like and tell me about it. Maybe I'll find one that doesn't suck. Maybe I'll just make my own.
One thing I won't do though, is complain about how there's now 1 million todo apps that aren't up to my standards. Everyone being able to make their own apps however they want is a beautiful thing.
If anyone has any ideas on what the point of violence in art is, I'm open to hearing it. Obviously horror is a genre and so is gore, and people seem to enjoy being shocked. I don't think that is what McCarthy was going for though. And he wasn't going for the vengeance-catharsis angle like Tarantino either.
I've been assuming the people who are having issues are junior devs, who don't know the vocabulary well enough yet to steer these things in the right direction. I wouldn't say I'm a prompt wizard, but I do understand context and the surface area of the things I'm asking the llm to do.
Being a senior engineer means having confronted a shitload of different minutia type problems from network stuff, compiler bugs, language nuances, threading nuances, etc. and having spent time figuring each one out. Not that senior engineers can reiterate all that minutia off the top of their head, but it gives them a good intuition for how to solve problems when they hit them making them significantly more productive than junior devs that have to figure them out from scratch.
I don't understand what's so hard about this, testing algorithmic knowledge tests if the individual studies and implements algorithms. It's very simple. And yes, people have stress reactions in test type settings (I don't for paper tests in school but apparently I do for live coding mostly because I don't know how to implement different algs).
Stress during interviews is insane. Once I was at the tail end of solving an interview problem but it came down to multiplying 9 * 3 and my brain wouldn't fucking do it (apparently I can't fucking multiply).
I'm not a codec developer, I'm only coming at this from an outside/intuitive perspective. Generally, performance concerned parties want to minimize heap allocations, so I'm interested in this as how it applies in codec architecture. Codecs seem so complex to me, with so much inscrutable shit going on, but then heap allocations aren't optimized out? Seems like there has to be a very good reason for this.
In any case I get what you're saying and I understand why codecs are going to be dynamically allocating memory, so thanks for that.