The Miller Principle (2007)
puredanger.github.io
The Miller Principle (2007)
1–10 of 63 posts
Re: The Miller Principle (2007)
#2I have found much value in reading the python and sqlite documentation. The Arch wiki is another reliable source.
Good documentation is hard.
Re: The Miller Principle (2007)
#3I have found much value in reading the python and sqlite documentation. The Arch wiki is another reliable source. Good documentation is hard.
I would love to answer your comment but I didn't read it :P
Re: The Miller Principle (2007)
#4The agents will read them
Re: The Miller Principle (2007)
#5I read this entire post and all the comments this disproving the Miller principle
Re: The Miller Principle (2007)
#6The LLMs read everything.
Re: The Miller Principle (2007)
#7The Laravel documentation is GREAT when you're getting started. Every chapter starts by answering the very question you might ask yourself if you're going through it top to bottom.
I'm a one-man-band so if I write code comments, I write them for future me because up to this point he has been very grateful. Creating API documentation is also easy if you can generate it based on the comments in your code.
Maybe rename it the Filler principle. Nobody reads mindless comments that are 'filler'.
Re: The Miller Principle (2007)
#8Despite using an ai while programming I still have open Java doc and other api documents and find them very useful as the ai often gives code based on old apis instead of what I'm actually using. So I do read those documents.
But also, I have a somewhat mentally ill (as in he takes medication for it) coworker that sends rambling extra-long emails, often all one paragraph. If I can't figure out what he's asking by reading the first couple and last couple of sentences I ask him to summarize it with bullet pouts and it actually works. Lol.
Re: The Miller Principle (2007)
#9..and emails
Re: The Miller Principle (2007)
#10The LLMs read everything .
Only because they are architecturally unable to not read something.