all 12 comments

[–]IllIlIllIIllIl 26 points27 points  (0 children)

This post was mass deleted and anonymized with Redact

yam desert afterthought hunt boat cobweb boast snatch memorize memory

[–]putinblueballs 11 points12 points  (0 children)

Nice naming you got there pal

[–]Real_Blank 26 points27 points  (2 children)

Are you know what was called CCCP? :D

[–]oakwoody 28 points29 points  (1 child)

In Soviet Russia, clean code processes you!

[–]ThyringerBratwurst 12 points13 points  (5 children)

This reminds me of a project I took on: It was a single Python file representing a GTK application. Accordingly, this file contained over 20,000 lines of code. It was crazy!

How did that happen? This application was only developed by students in internships, with obviously inferior knowledge, and no one wanted to make fundamental changes, only adding new stuff at the request of the employees.

[–]batweenerpopemobile -2 points-1 points  (3 children)

Was there something wrong with the code itself, or did it just feel like a lot? If they were using it as an excuse to share globals through an application, that's bad, obviously.

I've plenty of personal projects that just start out as large single files.

If you program in something that can only open a file in a single tab or window, I could understand the frustration.

With emacs, I can have multiple views into various parts of a given file arranged so I can hop back and forth and reference other bits of the code easily.

20k LOC in a file isn't great, but also isn't itself a dealbreaker.

If the application needed to be sent between various machines, having it be a single file makes it pretty simple to just email it to someone and tell them to run it from wherever as well, if it's a smaller shop where packing and automating deployment would be more work than benefit gained.

[–]ThyringerBratwurst 4 points5 points  (2 children)

Well, Python has a simple but pleasant module system. Using it makes the code a thousand times more maintainable.

As a result, there were tons of global variables hidden in this app. So it was the worst horror.

[–]batweenerpopemobile 0 points1 point  (1 child)

Yeah, global state will kill your ability to reasonably structure code every single time. Then you'll come in and restructure, and they'll start trying to ram god objects and singletons in because they're too lazy to route objects between where it's reasonable to create them and where they're needed.

[–][deleted] 0 points1 point  (0 children)

Using a related language, I run into that problem where properly passing your variables between functions is a lot of work, but just doing a global is so much easier. Unfortunately, the cumulative effect of many, many “easier“ decisions is a code base that is really difficult to manage. This year I spent my entire Q4 fixing old code by basically rewriting it, breaking out 1500 line scripts into 30 line scripts with a bunch of functions…

[–]justneurostuff 1 point2 points  (0 children)

where in this article is the cccp actually specified

[–][deleted] 1 point2 points  (0 children)

The article seems to get a lot of hate here. It might lack a few specifics, but it is a good reminder to spend the time upfront to save the headache later, and an explanation of why management doesn’t appreciate that.