If it works, it ain't stupid.
The Stupid Programmer Manifesto
91–100 of 239 posts
Re: The Stupid Programmer Manifesto
#92How can you store program state on disk like that? You'd need serialization and deserialization. A DB might be easier.
My first thought was the way early 1990s forum and blog scripts did it, aka the UBB/Movable Type method of storing everything as static text files in a directory somewhere.
That would be really inefficient though. I vaguely recall database driven blog and forum scripts taking over because of how poorly the old solution worked at scale.
Re: The Stupid Programmer Manifesto
#93> so I just store my objects in their entirety as-is on disk.
Every time I decided to use filesystem as db for my program, a couple months down the road that turned out to be a wrong approach.
Re: The Stupid Programmer Manifesto
#94This post is the programmer equivalent of teenage girls posting photos of themselves captioned with "I'm so ugly" to farm praise from their friends. I have come to dislike this growing trend that celebrates mediocrity and failure. Posting proudly that you are stupid, terrible and incompetent seems to result in applause and high praise. Why? Why is that a good thing? I hope this was intended to be a parody.
TBH I just read it as someone who's found a way to make web apps that works well for them and want to focus on solving problems rather than toying with their tech stack or copying solutions from contexts that are entirely unlike the one you're working, e.g. because you're at a much smaller scale.
Re: The Stupid Programmer Manifesto
#95Earlier quoted context omitted.
And they'll also run into major liability issues when they leak customer credit card information, SSN, or something similar because they have a single class that represents the table in the database and they use it in both the frontend and backend.
how does the "structure" of the data have anything to do with leaking information? Seems like data protection occurs way lower in the stack like https and encryption at rest.
I'm guessing they are thinking of a scenario where SELECT * FROM User_Details gets sent directly to the front end.
So even if all you are displaying is the users name or initials you would still be sending things like SSN and credit card number to the front end
Re: The Stupid Programmer Manifesto
#96I can't tell if this is an honest call to keep things simple, or if it's meant to ridicule that idea. Because I strongly, deeply agree with some of these points, and am absolutely horrified by some of the others.
I read this as childish frustration directed at people that are not "as smart" as the author.
Regardless of what he's trying to say, there are much much better ways to present these topics.
Re: The Stupid Programmer Manifesto
#97Honestly, the truly 'smart' programmer isn't someone who does or doesn't use a bunch of techniques or best practices, it's the one who can look at the situation and do what's right for that particular project/job. Most of the things in this post could be the right answer if the project is a weekend side project that's going to get a few hundred views a month, or a website for a small business. Bob's Restaurant doesn'…
How would you host the Bob’s Restaurant website?
You'd hit up GoDaddy for hosting and FTP your webpage files to it. And it'd work just as well as other website.
Re: The Stupid Programmer Manifesto
#98Honestly, the truly 'smart' programmer isn't someone who does or doesn't use a bunch of techniques or best practices, it's the one who can look at the situation and do what's right for that particular project/job. Most of the things in this post could be the right answer if the project is a weekend side project that's going to get a few hundred views a month, or a website for a small business. Bob's Restaurant doesn'…
Yeah, I read this post as a dig at "cargo cult" programmers who read up on google-scale programming and best practice and unthinkingly apply those constructs to their own Bob's-Restaurant-scale task at hand where they are often at best an unneeded time and complexity overhead.
Re: The Stupid Programmer Manifesto
#99Earlier quoted context omitted.
And they'll also run into major liability issues when they leak customer credit card information, SSN, or something similar because they have a single class that represents the table in the database and they use it in both the frontend and backend.
how does the "structure" of the data have anything to do with leaking information? Seems like data protection occurs way lower in the stack like https and encryption at rest.
Because of things like mass assignment or IDOR, or injection attacks, presumably.
Handing data from the user (untrusted input) directly to the backend unchanged is going to in 99.9999999% of cases also mean it's unchecked.
"I'm not smart enough to bother sanitizing my input, or to learn about stuff that's someone else's job like security" would fit right into this "manifesto".
Re: The Stupid Programmer Manifesto
#100One trusts he's not too dumb to protect his webapp from the OWASP top 10