note: Not the worst dev I've interviewed but worst I've worked with.
A guy who worked in my company before me "HARDCODED" the entire calendar for next 10 years starting 2016 in dictionaries and arrays in Python for a project.

Someone did it to me. With SQL. Every single week. As a damn table.

Whooo - triangles and squares. Every fuken time, people try to reinvent the wheel.

@mt3o enrages me to death, thinking about it.

You just have to respect this guy. 😂😂

No shit, cannot believe you, and even if I would, wanna think he generated all that with some tool he made to automate the generation.

Holly shit, cannot tell if should be angry or have the ultimate respect for that guy

Whoo man

I feel sorry for the person who had to review the pull request to check every single data to make sure there wasn't one missing or duplicated.

Oh wait.... if its in the code there probably wasn't a review. Or a pull request for that matter. Maybe no version control full stop.

There's a commitstrip for that...

@magicMirror @suprano I had to. The guy mentored me before leaving the company. Told this to me on his last day 😂

@stonyark 😂😂☠️☠️ he set a great example for you to follow. What do you plan on hard coding? 🤔

I have to deal with C++ projects without any external dependencies at the moment. Means: self-written HTTP server (including a socket implementation that crashes the whole thing when the client cuts the connection), URL dispatcher, JSON encoder,...

How does anyone think it's a good idea to reinvent sockets for a simple REST-API?!

At least for Guinness's world record

Too much hardcoded to be true