Coffee coffee = new Coffee { };
if ( coffee.Empty )
{
coffee.Refill ( );
}
else
{
coffee.Drink ( );
}
// I'm a software developer \\

When "Programmers" don't understand how something as simple as git works.

>Do they keep whole repository in a zip file for each commit? Having made 100 commits is there 100 zips with all the files? or is each commit additive to the first commit. so that 1 zip with all the files you just get files added or removed based on what commit you are downloading?

Stuff like this makes me cry.....
-commit 1GB file
-commit another 1GB file
Repo is now 3GB? Seems legit right?

DevRant works in china! 👌🏼
Honestly though it's been quite fascinating watching the great firewall of china actively filter most things I try to do.

noob misconception #527: during my first hackathon i didn't know what version control was (i thought github was this magical elite hacker tool), so id copy my code into a google doc every few minutes along with a timestamp 😫

Our programming teacher always wanted us to do this (in C#):

somedatatype somevarname;
somevarname = somevalue;

You were NEVER allowed to:

somedatatype somevarname = somevalue;

"Can't I just do it in one line?"
"No."
"Why?"
"<insert dumb statement here that gives no reason whatsoever>"

He made an account just to open this issue on my repo. I am still confused, 2 months later.

One step through the door my wife whips around, a look so disgusted she barely seems human. "What's that smell?" she cries. "It's you! You smell like...like bad code!"

Indeed, I am covered with the scent of the forbidden love child of a man who read half a chapter on if-then statements and then pushed out into the world, earthworm-like, a mangled misshapened gelatinous mass that my employer gave the title of line-of-business application purely out of pity.

For more days than I'd like to count I have been porting a ColdFusion 5 application to .NET. Initially written in 2000 and last touched in 2006, it has a data architecture comparable to Dresden after the second world war. It features a table solely comprised of seven columns of IDs so that joins can be made between other tables lacking a common key. Columns that should be contained within a single table spread out among multiple tables. Single columns containing data that should be multiple columns (with handy flags to separate the subsets). A view with 14 joins that playfully displays unintended results. And so much more spread out over almost 200 stored procedures, views, triggers, and tables on the SQL server, and dozens of additional ADO-like SQL statements within the ColdFusion itself. Fortunately, the application overcomes these issues by having absolutely no data validation while allowing nulls pretty much everywhere.

When I am done this will be a very nice ASP.NET MVC app with at least 150 less stored procs, views, and tables. Auto-generated duplicate entries will be a thing of the past. Pop-up windows that inexplicably refresh the underlying screen to display a different part of the program than the one the user wants will be eliminated. And a UI based on the colors of a Rubik's Cube with usability that Mr. Rubik would find challenging will disappear with only the trauma of using it left behind.

Sadly, this is not my worse legacy code experience. Just the most recent. Just the most recent stench added to a lifetime of bathing in code rot.

When you are the one who does all the work in a group project.