391–400 of 412 posts
Earlier quoted context omitted.
>Word is basically an operating system. And .doc files are basically a memory dump.
That was certainly true once, but now all that state is serialized to xml amd zipped up. You can unzip it and look at it if you don't value your sanity.
Earlier quoted context omitted.
An autopsy is an exam that is performed postmortem. And that’s really how people are using postmortem as a noun for the analysis that they perform after the “death” of a company, so it is a synonym at least approximately, if you don’t see that I guess you don’t have a very good imagination.
Try and find me some sentences out there on the internet in which one of the words could be reasonably substituted for the other one. They don't mean similar things and they aren't used similarly. A postmortem is, as you note in part, a report or a meeting for the purpose of producing or discussing such a report; an autopsy is a surgical procedure. They're as "synonymous" as the words "cigarette" and "cancer".
Now you get it.
Earlier quoted context omitted.
The job-hopping followed from companies not investing in their engineers, not the other way around. It was billed as the only way to get a promotion (which usually would come every 1-2 years).
I've been in this industry for a few decades at this point and I was around when this meme was started. It was purely about maxing your compensation because changing jobs nets you more than promotions & raises. I've never met an engineer in my life who truly earned a promotion every year and very few every two. Very few companies have org charts that even support that or have that many levels. This logic/advice only…
I'm similar to many people, I wouldn't have left some jobs in the past had I been treated with a modicum of respect and if my compensation went up with my tenure. But time and time again, pay ranges go up as new hires join in, but you're treated like you're insane for asking your compensation as a senior to match the compensation of a newly joined junior.
I just got a github notification on an old Bun bug report when it was still coded in zig. The bun-bot had completely solved the bug in the new rust codebase, added comprehensive tests, did the write up, pushed the commit all without human interaction. The fix looked sound and changed minimal lines of code. This AI is the real deal. Programmers should be concerned.
Earlier quoted context omitted.
They drive the TUI from the same thread that actual does stuff.. causing frequent freezes. No GUI developer would ever put this on the same thread.
Just ask Claude to fix it, what’s the problem??????? /s
Earlier quoted context omitted.
jared was OK making this rewrite as an experiment branch in the public why shouldnt upcoming work be as public as the rewrite itself was?
You may continue to hold your breath. You may die as a result. The maintainers continue to do what they want regardless.
The beauty of FOSS tho is Jarred owes the community nothing, and anyone can fork bun previous to migration and keep maintaining it on zig if they so wish.
long live open source
Earlier quoted context omitted.
I think this is perfectly fine. If you explore Github, you're gonna see thousands of abandoned game engines, compilers for made-up languages. And that has been happening since before the LLM era. I used to be part of an OS messaging board in the early 2000s and almost everyone had their own OS. A dozen people or so could even run Firefox! I remember (now legend) Terry bothering us to check out LoseThos or GodOS or wh…
> If you explore Github, you're gonna see thousands of abandoned game engines, compilers for made-up languages. And that has been happening since before the LLM era. Yeah, but the people authoring those learned something. > I used to be part of an OS messaging board in the early 2000s and almost everyone had their own OS. Great example! I, too, once had my own toy OS, and browsed OSDev wiki nonstop. The thing is no o…
I've built tools myself with AI assistance and I've learned a bunch, and will still keep learning.
Earlier quoted context omitted.
I'd like more people to be writing about this, because I find it fascinating. I have my own private project that is heavily LLM-coded, just to learn about what it's like. It's amazing how everything is different yet everything is the same. Big complicated features can start working quickly and give a massive endorphin boost, but then fixing them up and integrating them in properly and polishing the UI? It all feels e…
To build a robust piece of deep-functionality software (like an MS Word clone) with an LLM, you have to start from the underlying architectural decisions, particularly how data is structured and how it flows through the system. If you have an LLM or human just start coding up something without nailing down those decisions first, then he/she/it will implicitly make those decisions arbitrarily in the moment (usually ba…