What the FUCK im fixing integrations on some dumbass's API. Biz wants this in prod on monday. It's fucking saturday. Anyway

Me: why did you give us a 200 even if its an error
Them: thats normal
Me: If it's an error it shouldnt be 200
Them: its a 200 because the api params are correct but differ in value so its not an http error but an api error

lmao

Help. We're starting to feel the effects of unnecessary micromanagement.

We're a small startup. The kind with less than 10 devs spread across different domains. We've been fine with a Kanban approach as the velocity/flow of deliverables don't necessarily warrant a Scrum approach yet.

Our boss has been wanting to adopt Scrum-style sprints, even shoved and assumed that were doing these sprints and demanding Scrum-style reports (and meetings!!!) when they are, in reality,
1) unnecessary
2) a waste of time

Absolutely none of the team members want this. But our boss insists on having it. We like our boss, but lately things are getting out of control

What can we do to mitigate and prevent this?

Quick update on our partner's API that doesn't work (see previous rant).

They gave the wrong URL! Wow!! Well we have the new URL but
the production credentials don't work!!!

Weeks after our partner has been nagging us to release to production because we've been putting it off because their API sucks and wouldn't properly work.... we finally did....

except their production API doesnt even work LMAO

I'm currently showing my new junior the ropes in the workplace. We'll be using Gitpod for pair programming.

Me: "okay so I think Gitpod will use my configuration if we use the workspace I made... are you familiar with vim keybindings?"
Junior: "😢"

I've been putting off my gamedev project for a while... while the golden age of free open source game development has long ended, I believe that a renaissance is long overdue!

Any backend devs here working with TypeScript? What are the best framework choices right now? I've been looking at Nest.js, but there seems to be a steep learning curve that might hamper onboarding of my (literally fresh graduate) new hires. There's also Ts.ED, which seems like the fat has been trimmed from it.
I know people will recommend something like, just using express / koa / hapi but I don't think we have the time to work with something super lightweight 😬😬😬. And besides, opinionated frameworks will speed things up for now (we have a lot of crap we want to do this incoming 2022)

Is it possible to get through a work week without hearing about a surprise requirement when the deployment is supposed to be one week from now?

Bonus points: One week from now, deployment is delayed due to more whatever shit they forgot to take care of in the biz side

Holy crap, I can't take it anymore.
I know that user acceptance testing is supposed to be done by the end user but it's as if they entirely skipped UNIT TESTING and QUALITY ENGINEERING.
Does their API work? Yes. It does.
Are their endpoints working? Sort of... why are query parameters required again?
Is it good overall? No, there are CORNER CASES ALL OVER THE PLACE (are they even still corner cases at this point?). It feels like it was made by amateurs!
Why am I doing quality testing on their services??? holy crap, they should pay ME for doing this

ah yes, i'm a VERY kinky Java dev

my favorite NSFW act is naming my java variables shorter than their data types

Trying to use a certain library for my ORM needs. It seems that the devs 'forgot' to add decent documentation.

Also trying out another library to integrate with it. Again, no decent documentation.

It pisses me off how A LOT of Node.js libraries have the worst documentation ever, and if they do have some seemingly okay ones, they conveniently leave out the more complex functionalities. What do they want to achieve here? For people to head to their Github pages to sniff at the code?

Holy fucking shit. I hate you people. I even hate having to use these in the first place.

Everyone's a pro ninja 10x whatever until you ask them to create multi-core optimized code

During code review:

Guy (also the same guy who pushes code without making unit tests): "Hey, this thing you added is unnecessary. Remove it."
Me: "Have you read the rest of the changes? It isn't unnecessary."
Guy: "Not yet"

Me: 'alriiight let's run this code here'

Logs: 'lol the function you did is deprecated. how about you don't do that, and do the right thing instead'

What was the right thing?
I don't know. It's not on their documentation in their site.

Thanks, js devs :) you guys are the absolute best

So i'm working with people from another team to bring about a feature. I was wondering, "how come they're churning out so much shit in so little time!?"

Apparently, they make code, merge request to the release branch, and then do unit tests later.

How do people, in good conscience, think that they can skip unit testing for extremely vital components???

Why do node.js devs think it's okay to deprecate older functionalities while replacing them with barely-working ones riddled with bugs?

Is this a node.js community thing?

>$ mvn clean test
>$ [INFO] Building project-name
>$ ....
>$ ....
>$ ....
>Results:
>Tests in error:
> Test.test:75

aauaauugh

While talking about how Windows dropped support for a line of AMD GPUs (not really sure which), I suggested they use Linux.

Friend: "You know, whenever I hear Linux, it's always from oraro"

:(

Anyone else a fan of Android: Netrunner? I believe it's one of the only (tabletop) games that depict hackers accurately

"thinkpads are awful"
🙃

🙃Why push unit tests to master that don't even run successfully 🙃

I was in charge of updating the dependencies on a microservice we have. Everything was at least 3 years old. Nice. How bad was it gonna be?

Jesus Christ, I have never felt so wrong.

A certain dependency I will hide under the name w******js allowed custom functions for a feature that accepted three arguments: paramA, paramB, paramC. The old installed version, 1.x.x, did what was intended, but for some dumb reason, 2.x.x calls the function with paramA as paramB and paramB as paramA!

It took me a god damn while to find out why shit wasn't working as expected. Who thought this was a good idea?