!rant

So this happened in the zoom meeting today. 2 colleagues were arguing on something.

A : "Do I look like f**king joke to you?"
B : " No, you don't look like a joke , your camera is off. But you sound like one. "
A : "I am so tired of you , f**k you man"
B: " Hey you can't f**k me without my consent, I said I am not interested."

Me : "Uhm guys this is scrum meeting."
B: "No shit captain obvious, we all know that. "

I am so speechless.....

The Captain Obvious commenter:

// account deletion
account.delete()

// check results
if results.any()

.... which eventually leads confusing unmaintained comments

Comments should describe the why and not the what and always be up to date ... or this will be the result.

My new coding buddy

SEO analyst (hired by client) sends his inform to client, designer and developer (me) and all it says is: use friendly urls, proper use of h1, h2..., use alt in img tags...

Come on dude! Those are obvious things to any webdev out there who earns his salary. Do YOUR fucking job, do some fucking research and DO NOT dare to tell me page title and meta description are important (Really? No shit genius!) and tell me THE page title and THE fucking meta description... Or...

Fuck off and go find some other victim to trick with your bullshit marketing slang.

Meeting at 'Derp & Co', the topic was what data model should send the back-end to frontend & app via API calls:

- Coworker: 'we should send the data structured like this for reasons'.
- Me: 'Yeah, this nested object.object.object should do the trick for the front end, but this will be a pain in the ass to convert to POJOs. Why not use something like idk better structure?'

<Mad/intrigued faces>

- CoworkerS: 'Why you need to use POJOs?'
- Me: <More Mad> 'cause I work with java in android... and we have/need/like objects?

<Captain Obvious left the room>

- CoworkerS: 'Oh yeah, well... we can do it the way you say'.

Why you need Objects... what is the next?
- Git? For what? Did not have the usb key from day one?

So I was reviewing coworker's code the other day...
incomingMessageProcessor.processIncomingMessage()
....well thank you there captain obvious

Just sat through a demo of some clicky-draggy data visualisation stuff.

The guy showed us how you can write a custom script that takes a user input and pokes it into a sql command using string concatenation, so a very obvious injection vulnerability.

Ok, so it's only a demo. But you wouldn't do a demo with an example user called Captain Cock, so why do a demo with a screamingly obvious security hole?

Whole thing was basically pivot tables in a short skirt anyway.

I hate when programming books have shit code examples.

Just came across these, in a single example app in a Go book:

- inconsistent casing of names

- ignoring go doc conventions about how comments should look like

- failing to provide comments beyond captain obvious level ones

- some essential functionality delegated to a "utils" file, and they should not be there (the whole file should not exist in such a small project. If you already dump your code into a "utils" here, what will you do in a large project?)

- arbitrary project structure. Why are some things dumped in package main, while others are separated out?

- why is db connection string hardcoded, yet the IP and port for the app to listen on is configurable from a json file?

- why does the data access code contain random functions that format dates for templates? If anything, these should really be in "utils".

- failing to use gofmt

These are just at a first glance. Seriously man, wft!

I wanted to check what topics could be useful from the book, but I guess this one is a stinker. It's just a shame that beginners will work through stuff like this and think this is the way it should be done.

Sometimes I hate StackOverflow's review because I tend to comment and the post turns out to be 5yo top question with inf. amount of comments.

And there I come, the captain obvious, bumping an old thread because the review told you it's 2hours old or something.