7,488 karma · joined November 1, 2019
I guess I can't blame PHP because it comes down to the devs to enforce decent boundaries, but I think PHP makes it easier than others to do so.
PHP is so much better now, but if you're writing PHP, there's a very good chance you're not working with that new, clean PHP.
Nvidia seems strange to me because they don't have that kind of software history (not nearly as much application software history as others), but they have capital.
Meta has the application experience, but I don't think it fits the "developer trust" portion of the initial question.
> Two, I actually don't have any personal criticisms of Jarred
The author says two things that really popped out to me that you could say are "professional" and not "personal" criticisms, but I think they're still rude and contrast this statement.
> Jarred was already writing slop well before he had access to LLMs
> The grapevine was large and healthy and full of juicy grapes, and all those grapes contained the juice of the same message: Jarred was a stinky manager. Poor communication, unrealistic expectations, low empathy, no experience
Now, both of these may be true. I don't have any evidence though, so I don't know how to take it.
All this to say, I'll take both of these posts without a ton of salt when it comes to the non-technical parts.
Is it that much better than Opus? It's definitely up there, but Opus is my cheaper workhorse for the kind of work I do.
I saw some old code of mine that used PLY a few weeks ago and god damn is that a fine library. Fast, to the point, and a beautiful API.
Go gives you a bunch of goodies in the standard library.
Rust provides things like your build system, testing, and package management all together, which is what I assume OP meant.
If I'm not misremembering that case then, it sounds like this should've never been an issue (well, as long as this is after basic version control and make). Curious if I'm missing something.
https://cybersecuritynews.com/arch-linux-aur-packages-compro...
Not to mention that working at Oxide sounds like a modern Sun Microsystems with the ideology that team has. Highly recommend their podcast "Oxide and Friends", and their original "On The Metal" show.
I've attempted to apply to their company multiple times over the years, only to be stun locked by the application process. Not because it's a bad process, but because I feel I'm not up to par as an engineer. Maybe one day I'll go through with it.
I will say though, optimizing memory usage is easier than ever. Doing a scan of your codebase with an LLM for _large_ memory gains can probably shave a decent chunk off of any application with ease. You don't have to go down the rabbit hole, but taking the top 3 large things it catches would probably result in notable gains for minimal time usage.
Hell, I've hunted down code that was causing an OOM from a coworker that ran a regex that would have to search the entire string of a base64 payload that was often around 24MB, when it very easily could have been a basic string operation on the first 50 characters or so. I caught it myself, but went back after with an LLM about 8 months ago and it also spotted it with a vague point in the direction of where it could be.
There are probably a lot of small slip ups across a codebase that are simple fixes that add up over time, but we never catch because we're not actively profiling.
I expect to see this repeatedly with new powerful models from all providers.
Best I can do is root for local models (already was), but I'll keep my Anthropic subscription for their "lesser" models without an ID (for now).
Now of course there are areas you can make trade offs. A lot of people like MacBooks despite them not supporting other operating systems very well and Apple still mostly being hardasses about outside repair, but they come with good performance and battery life.
Making sure to keep maintainability in mind when making a product decision is critical to making an informed purchase.