Kraiden

2 were self employed, running their own businesses, one was fucking fishing, and one “cuts fabric” part time.

Show me a corporate desk slave that a) lives that long, b) works that long and c) doesn’t resent their entire existence, and I might buy into this obvious fucking farcical corporate propaganda piece.

Fuck you, eat the rich.

(Not you, Op, the author)

have you seen what people can do with makeup? The prince didn’t stand a chance!

Huh. My phone always tries to correct MAGA to MEGA… at least now it’ll make sense… Now I just need someone to make one for MEGAN

Make Europe Great Again, Ned!

Yes and no. I agree that camel vs snake or that stupid mNameThing that was popular for a while, doesn’t reeeeeaaally matter, although I would argue that convention over the language still has value. As an example, naming a Java variable with a capital letter would be confusing and annoying to any new devs joining the project, even if it’s a valid identifier. Also it’s handy to be able to look at something in ALL_CAPS and know that it’s probably a static final, without having to check it’s definition. I guess it’s about finding that line between useful conventions and pedantry.

Dear god please no. This way madness lies. Your idea of “whatever you think works best” is not going to line up with whatever the next person that comes along thinks, and your codebase is about to get all kinds of fucked up.

Thinking code complete is going to save you is naive. Even in languages like C and Java, where it works best, you still need to be able to read and understand the code in context. There’s no hope in a language like Ruby with all it’s meta programming stuff