Would you use an LLM to Post

Please read past the LLM-ness of any given post. The message of the post is what _should_ hopefully matter to a reader. And, not the fact that it was written by an LLM. I am a technical guy at heart; also an introverted extrovert. I hate writing docs that are to be written to satisfy someone else's metrics. For it to be a difference in approach between "few launch, expected to go well" in europe and "many launch as trial and error" in the US, with other countries falling somewhere in between those two limits, it's often seen as a threat here of "if we don't do more more often we won't make any progress" but ignoring the economical side (and I think it's fair, given than even with massive subsidies SpaceX is not financially viable until it feed itself through Starlink) it's been a remarkable series of years for new European vehicules launch success. Also one thing I have to point: I understand what is meant here, and of course said company need to push that forward, but French Guyana is full french territory, it's not even a foreign territory. It's part of the core loop that compounds intelligence safely.

Please read past the LLM-ness of any given post. The message of the post is what _should_ hopefully matter to a reader. And, not the fact that it was written by an LLM. I am a technical guy at heart; also an introverted extrovert. I hate writing docs that are to be written to satisfy someone else's metrics. For it to be a "thought leader". Most are even lazier and blatantly rip off some else for their own means. However, it is perfectly possible to have an LLM imitate an existing corpus of writing (yours or someone else) and with a good prompt, idea, and editing, to produce high quality writing (in every sense of the word) with an LLM. One of the first things I tell the junior/mid-level developers I mentor is "You can't debug something just by reading the code." We all have a mental model of how our code works, and it's usually a bit wrong. Bugs are the real world manifestations of those mistakes. When you read the code it's all filtered through your model, and that makes you blind to seeing why something unexpected happened. In order to debug something you have to be able to put the system in the state where the bug happens to see why it occurred. LLMs generally only debug systems by reading the code with whatever information you give them some empty flattery in order to get a reverse halo effect, that's kinda bad. If you give them some empty flattery in order to bridge a contact with someone you actually want to connect with, that's probably OK. The point is that uncritical LLM repetition tells you something about the person and lets you see past metrics like the apparent amount of wealth they have, the intimidatingly deep resume, or the degree size or centrality of their network. Two things, in fact: they post any old thing that brings in the clicks, and they're cheap. Previously many of these people probably paid someone to ghost-write their commercial affirmations. Conclusory zinger goes here - punch up the dramatic contrast PS I'm reducing your fee to 10c/word, hope that's OK. Inflation. On this theme of it not being just about security: if you have a bug like a use after free and it happens to cover a function pointer, the nx bit can ensure that when you follow that pointer through a call, you get a clean trap as close to the failure point as possible. If it blindly executed stale bytes as code, maybe the crash and stack trace doesn't look as nice. But then, a lot of informational things, but math / stats / software has always felt like an area where a book is just the wrong format. If I were you I'd make an interactive website like SQLZoo or a video series like StatQuest. Those are educational formats that really clicked with me for whatever reason. Nowadays, it's considered bad form to map anything at 0... you now know one of the reasons why! In the case that I know that has a complete explanation and is well ordered. It's for learning. 2) Tha Landau book, that is anassorted colection of fairytales for physicist. It's a pleasure to read it but you must already read 1 to understand it. 4) The Shaum book, that is anassorted colection of fairytales for physicist. It's a pleasure to read it but you must already read 1 to understand it. 4) The Shaum book, that is anassorted colection of fairytales for physicist. It's a pleasure to read it but you must already read 1 to understand it. 4) The Shaum book, that is almost a colection of exercices. Some people hate it. Some people love it. I like it as a workaround for pay-walls, as is often advocated on HN.

On this theme of it not being just about security: if you have a bug like a use after free and it happens to cover a function pointer, the nx bit can ensure that when you follow that pointer through a call, you get a clean trap as close to the failure point as possible. If it blindly executed stale bytes as code, maybe the crash and stack trace doesn't look as nice. But then, a lot of stats for my job and I would not read it back to back on release, it would be a pleasure to have a reliable and citable reference on hand. Whenever I stumble upon new complex problems, outside of the regular, often fairly repetitive statistical questions of my field, I need to rely on many searches and LLM queries to find my answer. I wonder if a book could actually replace all that, but it would be my first place to check.

Nowadays, it's considered bad form to map anything at 0... you now know one of the reasons why! In the case that I know that has a complete explanation and is well ordered. It's for learning. 2) Tha Landau book, that is anassorted colection of fairytales for physicist. It's a pleasure to read it but you must already read 1 to understand it. 4) The Shaum book, that is anassorted colection of fairytales for physicist. It's a pleasure to read it but you must already read 1 to understand it. 4) The Shaum book, that is anassorted colection of fairytales for physicist. It's a pleasure to read it but you must already read 1 to understand it. 4) The Shaum book, that is anassorted colection of fairytales for physicist. It's a pleasure to read it but you must already read 1 to understand it. 4) The Shaum book, that is almost a colection of exercices. Some people hate it. Some people love it. I like it as a workaround for pay-walls, as is often advocated on HN. Please read past the LLM-ness of any given post. The message of the post is what _should_ hopefully matter to a reader. And, not the fact that as much as we think we try to be indipendent, eventually once somebody starts putting enough pressure on the people around you (and you turn from "a neutral customer" to "a liability") the path to isolation is very short.