why do you have,...

HHHHaaha~
You should know what concepts are and how to code firstly.

Was looking for an excuse to use this meme:

What do you call a careful wolf? Aware wolf.

This guy is pure evil 😈

How many project managers does it take to change a lightbulb? None, they'll just schedule a meeting to discuss the lighting strategy.

Nobody, nobody, nobody should accept an office-only position unless they actually want to work in an office. People who actually believe that everyone should go back into the office should be excommunicated from this field. This freedom we have needs to be protected for the best interest of the future.

If only.

Thoughts?
https://github.com/RupertBenWiser/...

Right...

"How do you do X?"

"RTFM"

* npm install RTFM *

when someone tells me unit tests are useful and I should start writing them

it sucks!
Fuck asynchronous code because

Increment operator (++)
Decrement operator (--)
Excrement operator (💩💩)

had to laugh way too hard about this in the office today, feels like it was invented for our team

https://reddit.com/r/...

😅😅😂😂

Coding often times, is just moving from one error message to another.

i understand some developers like to write wrapper functions to handle tedious things, I even understand how to write dynamic SQL queries, but for the love of fucking god and sanity, NEVER FUCKING DO THIS!!!!

Yes its PHP, but its not even bad PHP, its a fucking abomination from hell of PHP.

I just spent… a significant amount of time touching my face feeling the bone tissue within. Now I have the perfect depiction of my skull, and when I open my mouth, I can see the picture of my skull doing so. To me, a skull has its own, separate face. Quite disturbing, not gonna lie.

Remember: right now, inside you, there is a skeleton.

"LGTM 👍"

Best decision: becoming self-employed.

Worst decision: not doing it 5 years earlier.

expect([
row[‘blah’][0][1],
row[‘blah’][1][1],
row[’blah’][2][1],
row[‘blah’][3][1],
row[‘blah’][4][1],
]).to contain_exactly(
a.name(user), # “John doe”
c.name(user), # “John doe”
e.name(user), # “John doe”
b.name(user), # “John doe”
d.name(user), # “John doe”
)

(Note: The comments are mine.)

See the problem? No, not the ugly code (which is actually worse than what i posted here).

It’s using the same ridiculous getter (if you can call it that) that pulls a name out of the passed user object, and then expecting each row to have that name, in order. Not that order matters when they’re all the same.

Upon inspection, all objects created by the spec have the exact same name, so the above test passes (as long as there are 5 rows). It passes, but totally not because it should: those aren’t the objects that are actually in the table. All of the specs — all 22 of them — only check for that shared name on various rows, and no other data. And it’s not like this is the only issue, either.

Fuck me these are bad.

And this guy is a senior dev earning significantly more than me. Jesus what the fuck Christ.

Yes yes yes
Let's spend countless hours writing painful spaghetti that generates a financial report, extend that spaghetti for specs, then not bother to check the amounts or status. or where it says the money went. Nope, checking non-unique names is totally good enough. We're so good at this. Ten points to the legendaries.

Let's also make the object factories not create the objects correctly, and make sure that report includes entries for orders that don't include any actual payments. Oh, their status? "Ready to send" of course! Let's send that totally valid $0.00 to nobody!

Oh, but Root. Root, root, root. You can't ADD payments to this. no no no. if you do, it'll break specs everywhere else that uses that factory! Shame on you for suggesting it.

Pssh, now you want to make a payment just for this report? Why would you do that? Our best devs have been working on this for years! What could you possibly know that they don't? No, they're perfect. Don't touch them. Just make them better, okay? No take, only throw!

Dropping out of college because it was useless, and getting a job in the industry while continuing to teach myself.

That way I was paid to learn instead of the reverse — and I learned newer and actually useful things. I also saved time to boot.

I might not have a masters degree, but that doesn’t matter, either. Experience is always better than a comparable amount of education.

Honestly, none of the good devs I have worked with held masters degrees. To a one, they were all self-taught.

Excerpts from "Bastard devops from hell" checklist:

- Insistently pronounce git with a soft "G" and refuse to understand people not using that pronunciation, the same goes for jithub, jitlab, jit lfs, jitkraken etc.

- Reject all pull requests not in haiku format, suggest the author needs to be more culturally open minded when offending.

- increment version numbers ONLY based on percentage code changed: Less than 1% patch increment, less than 5% minor increment, more than that major version increment.

- Cycle ALL access keys, personal tokens, connection strings etc. every month "for security reasons"

- invent and only allow usage of your own CI/CD language, for maximum reuse of course. Resist any changes to it after first draft release

I came to know and use C++ for 10 years now and I've just seen this syntax:

for(int i{0}; i<5; i++) { }

WTF is this shit??

So i have been thinking..
SQL is a lang that runs on a specific software on the server, and helps creating data stores(databases and tables) that can be queried & manipulated.

is there a way to run sql like queries on the client side with no interaction from backend at all?

Say i have 5 inter related data models. in a backend world, they will form nice little tables of a db with all their joins and composite keys. from the server, i shall be querying them like "SELECT name from x where y=z & ..."

but what if i could store them like tables in browser memory and run the same query filters via a query language... is this possible?

i know this poses a certain security risk, but we already use cookies, local storage and a lot of json based shitty client side storages. surely it might be possible to have a lesser optimised sql tables on the frontend with extremely good querying capabilities?

or am i talking something far fetched here?

write comment above block of code

or pull block of code out into method and work the comment into method name

programmers now vs then

sprint retros with PM are a fucking farce, it cannot possibly get any more grotesque.

they are held like this:
- in the meeting, PM asks each team member directly what they found good and bad
- only half of the team gives real negative feedback directed towards the PM or the process, because they are intimidated or just not that confrontative
- when they state a bad point, he explains them that their opinion is just wrong or they just need to learn more about the scrum process, in any case he didn't do anything wrong and he is always right
- when people stand up against this behavior, he bullshits his way out, e.g. using platitudes like "it's a learning process for the whole team", switching the topic, or solely repeating what he had just said, acting like everybody agreed on this topic, and then continue talking
- he writes down everything invisible for the team
- after the meeting he mostly remembers sending a mail to the team which "summarizes" the retro. it contains funny points like "good: living the agile approach" (something he must have obviously hallucinated during the meeting)
- for each bad point from team members, he adds a long explanation why this is wrong and he is doing everything right and it's the team's fault
- after that happens the second part of the retro, where colleagues from the team start arguing with him via mail that they don't feel understood or strongly disagree with his summary. of course he can parry all their criticism again, with his perfectly valid arguments, causing even longer debates
- repeated criticism of colleagues about poor retro quality and that we might want to use a retro tool, are also parried by him using arguments such as "obviously you still have to learn a lot about the scrum process, the agile manifesto states 'individuals and interactions over processes and tools', so using a tool won't improve our sprint retros" and "having anonymous feedback violates the principles of scrum"
- when people continue arguing with him, he writes them privately that they are not allowed to criticize or confront him.

i must say, there is one thing that i really like about PM's retro approach:
you get an excellent papertrail about our poor retro quality and how PM tries to enforce his idiocratic PM dictatorship on the team with his manipulative bullshit.

independently from each other, me and my colleague decided to send this papertrail to our boss, and he is veeeery interested.

so shit is hitting the fan, and the fan accelerates. stay tuned シ