Edit: Sounds like an enjoyable, low commitment book. Will give it a try, thanks for the feedback.
There are things he does not stand out at, but those don't take you out of the story. As people work through things on Earth a lot of the nontechnical parts are, I guess, simplified, but I can't care that much; I didn't pick this up wanting a bureaucratic or psychological thriller. And he (or he + early readers and editors) usually make sure to quickly and efficiently get you through all of that to the next fun part.
To be fair, I read it months before the movie announcement and it really felt like reading a movie plot. If you prefer, I thought that the author had a great story idea but cared very little about writing a book, like he already knew this was for Hollywood.
I think with good production it’s going to be a better movie than the book.
Never read the Martian but I was told it was the same thing.
The Martian was actually originally published in a serialized form, one chapter coming out every so often.
> It didn't start out that way though. "The Martian" began as a series of self-published chapters on Weir's personal blog.
> Then Weir decided to put the book on Amazon, selling it for the website's lowest possible price ($0.99).
* https://archive.is/https://www.businessinsider.com/how-andy-...
> Having been rebuffed by literary agents when trying to get prior books published, Weir decided to put the book online in serial format one chapter at a time for free at his website. At the request of fans, he made an Amazon Kindle version available at 99 cents (the minimum allowable price he could set).[9] The Kindle edition rose to the top of Amazon's list of best-selling science-fiction titles, selling 35,000 copies in three months, more than had been previously downloaded free.[9][11] This garnered the attention of publishers: Podium Publishing, an audiobook publisher, signed for the audiobook rights in January 2013. Weir sold the print rights to Crown in March 2013 for over US$100,000.[9]
* https://en.wikipedia.org/wiki/The_Martian_(Weir_novel)#Publi...
Hail Mary felt like it was trying to capture the same magic but missed the mark. The plot felt constructed rather than spontaneous and I couldn't relate much to the main character at all. I agree about the Hollywood motive. I'll probably watch the movie.
That's the very feeling I had when I read 'The Martian'. While I was reading it I actually thought something to the tune (It's been years now) "This reads like a movie".
Guess that explains why the movie is so faithful to the book.
The scenario is definitely contrived to introduce interplanetary travel to a near future setting.
The amnesia parts of of the book are not very coherently written.
However what Weir IMHO excels at is having fun self insert characters solving problems. When you get past the cruft and get to the "This is a book about troubleshooting in space" sections, it takes off.
I do think the movie will probably end up better than the book: having a screenwriter go over the dialogue alone will do a lot, I think.
Additionally, in terms of genre I actually find Weir's books to be more like detective novels than sci-fi, though obviously lots of sci-fi elements in them.
Check out Dragon’s Egg while you’re at it. It’s like Project Hail Mary’s much nerdier older brother.
My verdict is that Project Hail Mary was way much more engaging in terms of story-telling. The concepts were cool, and tbh I look forward for the movie and see if the adaptation will be nice
If you enjoyed The Martian (book or film), then this is just more of the same.
PHM, from the same author, I was very much expecting to be very good to amazing. It delivered, but it's a different feeling when you see it coming
Don't watch the trailer for the movie though, it's very spoiler-heavy.
The story is also just sentimental enough in an unusual enough way that I fell into it enough to be moved where it counts.
If you want to read it for anything resembling hard science concepts though, forget about it maybe. Weir lays on just enough of his usual technical babble to give a richer scifi feel to the book, but much of the core events are hand-waved into existence well away from anything resembling realism. That's okay though, because realism isn't really the point of the book anyhow.
In "The Martian" I thought the technical stuff was closer to touching on realistic details, since it was about a comparatively simple Mars mission gone wrong. Here though, we're talking about using near-current technology -with a clever plot device for an exotic fuel source- being used to zip around nearby star systems at just a hair under the speed of light, and most of that is complete, utter fantasy in disguise.
I'll give this to Weir though, he's damn imaginative at crafting a lot of very plausible sounding, deeply detailed technical talk, despite it mostly being completely invented.
Also the main character is a tough girl which is nice.
I liked the Martian but it was a bit too cheerful for a pretty rough situation. And the characters a bit one dimensional. Artemis is a bit grittier.
Project Hail Mary didn't quite resonate with me somehow. It's ok but not a rereader.
It's maybe not a literary masterpiece and it's suspiciously similar to The Martian if you squint. But not many books can get me laughing out loud the second or third time through.
It's a really fun read and I find the aliens particularly compelling in a way that most Sci-Fi doesn't get right.
TBF I am trying to write fiction for the first time in my writing career, and I also suck at characters and non contrived story engagement, so I’m not trying to throw stones here. I do hope, however, to do better in my first published fiction.
Definitely read The Martian if you haven’t already.
Listening to audiobooks is still 'reading'. It's very uncommon to get abridged auto books now, so every word is still being consumed. It's just a difference in which sense you are using to consume it.
What's the beef between PlanetScale and Neon? Benchmarking, uptime, vibe coding?
The quote at the end doesn't really help me. Which one is good for what?
- PlanetScale for predictable load. You pick a config (CPU, memory) and if you don't have traffic it sits idle, and if you have traffic it's limited by the config you picked.
- Neon for scalability. You pay for compute hours, so if your traffic is spikey (e.g. concert ticket sales), you don't pay for idle resources during low traffic, and get all the compute you need during high traffic.
So if you get at least one request every five minutes, neon will charge you for 24 hours of compute a day.
Sam Lambert tweeted this [1], which may or may not (I genuinely have no idea) have been poking at Neon, or maybe just the idea of vibe coding in general.
IMO, reading [0], Neon (and most of the industry tbf) is suggesting bonkers ideas. “Oh, did the AI accidentally give you SQL Injection? No problem, we’ll catch it.” Maybe - just spitballing here - if you don’t know how to prevent the most basic of attacks, you have zero business putting anything into prod, and need to spend time learning fundamentals.
[0]: https://neon.com/blog/oops-proof-your-vibe-code-with-neon-be...
They excel in their respective areas based on the architectural decisions they've made for the use cases they wanted to optimize for.
PlanetScale, with their latest Metal introduction, optimized for super low latency (they act like they've reinvented the wheel, lol), but they clearly have something in mind going in this direction.
Neon offers many managed features for serverless PostgreSQL that were missing in the market, like instant branching, and with auto-scaling, you may perform better with variable workloads. From their perspective, they wanted to serve other use cases.
There's no reason to always compare apples to oranges, and no reason to hate one another when everyone is pushing the managed database industry forward.
I’ve spoken to them personally, and didn’t get the impression at all that they think they’ve “re-invented the wheel.” More like they realized that separating compute and storage was a god-awful idea, and are bringing back how things used to be in the days of boring tech.
Also, re: branching, PS MySQL definitely has that. I assume they’ll bring it to Postgres.
I’ve learned (sometimes the hard way!) that every design choice comes with real trade-offs. There’s no magic database architecture that optimizes every dimension (e.g., scalability, performance, ease-of-use) simultaneously.
Social media often pushes us into oversimplified "winner vs. loser" narratives, but this hides the actual complexity of building great infrastructure.
Recognizing and respecting these differences makes us smarter engineers, better community members, and frankly, just more enjoyable people to chat with.
PS Thank you for helping me add a new book to my list :-)
