> “If you are bored with this novel after three pages, you shouldn’t read any further.”
The concept of DNF (“did not finish”) is pretty familiar to people who read regularly, but three pages seems far too early to make that call. The general rule of thumb I’ve encountered is closer to 100 - 150 pages.
Some of the most memorable works of literature I’ve read are books I didn’t particularly enjoy for the first hundred pages or more. I stuck with them mostly because I deliberately give books time to develop before deciding whether they’re for me.
My favorite example is A Tale of Two Cities. I didn’t enjoy it all that much until Book Three, Chapter 12. From there, it was smooth sailing. It’s now one of my favorite stories I’ve ever read, and I still think about it often, especially that entire final book.
That doesn’t mean every book takes that long for me. There are plenty I enjoy from the very beginning, particularly stories retold from a character’s perspective, adventure stories like Watership Down, and pretty much any Sherlock Holmes novel.
I understand the idea of putting a book down after a few pages if you don’t connect with it, and ultimately everyone should read however they want. But I do think that, by doing so, you risk missing out on some genuinely great books simply because they needed more time to become what made them worth reading.
Side note: My actual criteria for dropping a book are a little different. I tend to stop when reading it gives me a kind of vertigo or that strange feeling where your throat tightens and you start to feel sick.
> The general rule of thumb I’ve encountered is closer to 100 - 150 pages.
Practically all novels I've gotten to page 50 on I've finished. The only book I ever made it anywhere close to page 150 without getting anything back was The Fellowship of the Ring, and I think I got to page 200 before giving up (because I felt that I should be a person who liked The Lord of the Rings). It was a grueling experience. I can't fathom putting in 100 pages of joyless reading on a regular basis.
I just HAD to use it today, I avoided them as much as I could.
We have a figma design that's not really enterprise level with different components and not really coherent in some ways, and the management want the web pages to be the exact same as the figma designs.
Knowing the hell that awaits me in trying to be pixel perfect between about 40 pages, I set up the Figma MCP with my codex, and low and behold... it actually did what I needed, so that's one thing I'm grateful for.
For reference, feeding screenshots to the AI didn't do that well of a job at first.
best books I could recommend are fiction, they teach you much more than non-fiction, lessons learned in stories are better tha unordered lists of advice you'll forget in a few days.
Some of my favorites include: a moveable feast, watership down, 11.22.63
I remember how lost when I was 16, truly it was just a massive wave of depression and fear and loss. I encourage you to do what I did and explore as many facets as you can possibly imagine (coding, guitar practice, drawing, 3D modeling, pixel art, car tuning, botany, gardening, astronomy...) and if you find something you love and you find yourself doing it for months almost like second nature, you should follow that in whichever career direction it leads you or wherever it takes you with school and opportunities.
There's no one set path, and I did struggle with that as a 16 year old as some paths appear better than others. In my time, html, css, and js bootcamps were literally everywhere and now, look at the development space. you never know and you can never predict the future, but you can follow what you love and opportunity will present itself for you to shine and feel comfortable.
I second the fiction reading. Any and all types of story books. It's not so much about learning something for you yet, it's about learning how to learn. Storing books in your head helps you build up the abilities for that.
Fun Fact: in king of queens, most of the pcs (for example airport episode with doug's parents) are just RCT tvs with paper printout of a screen taped over it.
PCs (and screens in general, particularly old CRTs) are a b*tch and a half to film.
You typically film at E.G. 21 FPS, while your PC runs at 50 / 60 (which isn't an integer multiple of 21), so you get Vsyncs somewhere during each frame, making each filmed frame a superposition of two frames onscreen. You also have to be careful about how long the film is exposed for, as, on a CRT screen, the electron gun goes left-to-right, top-to-bottom, and the top-left corner of the frame is no longer visible when the gun reaches bottom-right. If your film isn't exposed for the entire duration of the frame, parts of it may never be visible.
This is why there was a cottage industry of PCs and PC monitors designed to run at Hollywood frame rates. Cathode Ray Dude has an excellent video on why this was a problem and how the problem was solved[1].
Wow, I also wrote a game 8 years ago and have been using AI to rebuild upon it. I'm excited to tell people that I wrote it from scratch without AI! Love these new rules!
Out of 557 total commits in the repo, 510 have been done before the past 2 weeks. All those (minus 5 in 2023-2024) have been done on or before July 2022, months before ChatGPT had even launched.
Out of the 47 commits in the last 2 weeks, 26 were README updates / CI / docs. The remaining 21 commits are clearly cleanups, speedups, bugfixes, and tangential features like Blender import/export. Which leaves us with 505/557 commits (90%) if we're not generous --or 531/557 commits (95%) in the best case-- of non-AI commits to the repo.
OP clearly wrote most of the project by hand and has just been cleaning things up for public release the last couple weeks. Exactly as he disclosed in his comment.
It all boils down to what each of you individually understands as "made with AI", which could be anything between using autocompletions and braindead vibecode.
I think it's not the issue with the added PR count, but the fact they have to review them. 1 big PR review is the same as 5 small PR reviews if you have to look at how it holds, edge cases and what not...
Well, then add some backpressure. Each contributor gets only a few small PRs a month, until they prove themselves. Contributors that don't have a credible online presence are automatically rejected. Etc
You know any AI war heroes? You went full AI engineer, man. Never go full AI engineer. You don't buy that? Ask Roy Lee, 2025, "Cheat On Everything." Remember? Went full AI engineer, went home empty-handed.
Imagine buying a TV. The TV works perfectly, but some of its features depend on the manufacturer’s servers.
Years later, the company decides those servers are no longer profitable to maintain. Instead of allowing users to keep using the product in a limited form, releasing server software, enabling community maintenance, or transferring support to another party, they remotely disable the functionality entirely.
Now imagine they could physically come to your house and take the TV back because they no longer want to support it. Most people would immediately recognize how unreasonable that sounds.
That is the core concern behind Stop Killing Games: consumers pay for a product, yet publishers can make it unusable after sale even when there are technically feasible alternatives that would preserve access without obligating indefinite support.
The argument is not “force companies to run servers forever.” It is: when official support ends, there should be a reasonable end-of-life path that leaves what people purchased in a functional state.
The answer is I wouldn't buy a TV that depends on online services. Just like I already wouldn't buy a video game like that, unless maybe it's very cheap. Some people do it anyway because it's still way less bad than the TV example.
currently there's a huge risk Marathon might get shut down like high guard or concord because of player numbers. If they shut it down, nobody could play it anymore.
If there's a system in place for us to be able to host our own servers, or... I don't know? OWN the game we bought and play it because we OWN it because we PAID for it. Then yeah, that's good and it's a good movement and I fully support it.
I genuinely don't understand the other side of this argument because it just feels like no for the sake of no.
what's the risk? "Oh no we might have to provide the product we sold!" Lmao. That's the right kind of risk to force on sellers in a market. Sellers risk getting penalized for not providing what they have paid for. Great. Fanastic. Sounds healthy for any market and may even increase average customer confidence enough for a surge in sales, one that can't be created by one company alone.
The concept of DNF (“did not finish”) is pretty familiar to people who read regularly, but three pages seems far too early to make that call. The general rule of thumb I’ve encountered is closer to 100 - 150 pages.
Some of the most memorable works of literature I’ve read are books I didn’t particularly enjoy for the first hundred pages or more. I stuck with them mostly because I deliberately give books time to develop before deciding whether they’re for me.
My favorite example is A Tale of Two Cities. I didn’t enjoy it all that much until Book Three, Chapter 12. From there, it was smooth sailing. It’s now one of my favorite stories I’ve ever read, and I still think about it often, especially that entire final book.
That doesn’t mean every book takes that long for me. There are plenty I enjoy from the very beginning, particularly stories retold from a character’s perspective, adventure stories like Watership Down, and pretty much any Sherlock Holmes novel.
I understand the idea of putting a book down after a few pages if you don’t connect with it, and ultimately everyone should read however they want. But I do think that, by doing so, you risk missing out on some genuinely great books simply because they needed more time to become what made them worth reading.
Side note: My actual criteria for dropping a book are a little different. I tend to stop when reading it gives me a kind of vertigo or that strange feeling where your throat tightens and you start to feel sick.