Loading…
7
I used to write all my code in one big file until my project in Austin crashed last month
3 comments
Log in to join the discussion
Log In3 Comments
thea_knight4mo ago
My first job in Austin had a single PHP file that hit over ten thousand lines. The whole thing just locked up one afternoon and took the client's store down for hours. Splitting that mess into modules felt like untangling a ball of Christmas lights, but it saved the project. Now I won't even start a script without making a separate folder for the main parts. That crash taught me that clean code isn't just nice, it's what keeps the lights on.
8
nathanrobinson4mo ago
What gets me is how that kind of code crash can actually kill a small business. It's not just a dev headache, it's someone's rent check going up in smoke because their site died.
2
harris.vera2mo ago
My last project had a function called "doEverything" that was literally 800 lines long. I named it that because I ran out of ideas for what else to call it. When that thing broke it took down our entire checkout system on a Saturday at 3pm, so yeah I get the rent check thing. Felt like I was watching someone's livlihood burn while I stared at a wall of spaghetti.
4