Just disassembled 2 €5 desk fans because they were shit.. and so is their design apparently.

What I found inside was actually surprisingly simple.. a toddler could build it. It's just a DC motor, a 3PDT switch, DC barrel connector, some wires and screws to hold stuff in place. Oh and the plastic thingie with the fan blades, as well as the USB cable of course.

5 fucking euros. The combined cost of the components would be less than 3, certified motherfuckturers. Time to build it, injection moulding, transportation, sure.. but still.

And if you think that being salty about €5 is cheap shittalk, expand that to every fucking piece of electronics that doesn't cost a small fortune.. at all price ranges. Could be radios, alarm clocks, heck even phones. Shit's way too expensive for what it's worth. Perhaps because so many people in the industry are just here for a quick buck.. motherfuckers 😒

Anyway, back to the design.. the hole in the fan blade thingie is supposed to get the motor's shaft shafted in, to turn the blades. I'd use glue there.. but not these designers. They just shove it in and hope that friction takes care of everything. And one of the fan blade modules' hole was so wide that inserting the motor is like throwing a sausage down the hallway. No contact at all! Make it tight already like the Chinese designer's glory-...
Nah let's not get into Chinese tightness just yet.

Oh and also a resistor for slow mode. Consumes just as much power except the fan turns slower. Because fuck efficiency, right?

Goddammit, next time I'm just gonna build my own again.. at least that wouldn't be a certified piece of shit 😑

A little example of how recriutment in IT works.

Mechanic gets a live mechanic skill test to get a job, as he really wants this job because of lack of money he asks recriuter couple of questions.
Mechanic: do I need to bring my own tools ?
HR: no everything will be provided in place
Mechanic: what would I do during this test ?
HR: everything will be explained just before the test I’m not an engineer so engineer will explain everything to you

The test day, mechainc goes to the test place and the recriuter says:
Recruiter: Your first task is really simple, please tighten those screws, you have 10 minutes
Mechanic: But I don't see the screw driver

Recriuter: I can't say to you how to do it, you figure something out
Mechanic somehow manages to tighten those screws using his belt

Recriuter: Ok so now tell me what force is needed to unscrew them and tell me if you did good if I’d say you need to tighten 1 million screws
Mechanic: I just want to do my job

Recruiter: Hey we are looking for people with broad experience for this position, of course you wont be asked to do that task but we want to know if you’re capable to do the job if we ask you.
Mechanic: answers the question that he will use tools and what devices he will use to measure the force

Recriuter: Can you write this as a mathematical equation ?
Mechanic: don’t know that
Recruiter: Well we can’t hire you we are looking for someone with more knowledge about the topic

Mechanic: But you keep asking me about the fucking screws
Recruiter: Watch your mouth sir because for me you are junior mechanics, you don’t know how to use proper tools and you barely manage to do the first task in time I would use: started elaborating about tools to tighten many screws at a time in a distributed fashion

Mechanic: but to run those tools I would need more than 10 minutes and besides that those are not here
Recruiter: yes they are, we open those doors to get them before our work you suppose to know that and we use those all the time, it was in job description, besides that it is recommended by company xyz to keep those tools behind blue doors, there is nothing here besides blue doors and room with tools and you didn’t know what blue doors are for, you need to learn the basics first

Mechanic resigns. 90% luck 10% skill
Every fucking time.

I'm in a situation at work where management and even the team I'm on, does not want to create a test suite, because:
1. It takes time to get decent code coverage. Time that could be spend doing new features
2. My team doesn't like to test.

We're now in a situation where we break something every single fucking time we relase and the manager just ignore that it's now a common occurrence. It it literally just a matter of time before the entire fucking backend will shit itself over poorly maintenanced code (who has time to do refactoring anyway) and poorly tested flow.

It annoys me greatly that a developer with many years of experience fails to see and understand that just doing test by hand, screws us over so badly.

As a junior dev, i would like to know, how are your team dealing with testing?
Because we're clearly not...

How many Windows users does it take to change a light bulb? - 100. one screws and 99 clicks the error messages away

I know the video editing software LightWorks has its aficionados. I can see how it's powerful. I've been using it since at least version 12. But my gosh how it screws people over. In the latest version, when you import files into a project and then want to delete _just the reference_ to the files in the project, LightWorks says "Nope, imma delete the FILE, too!" So you can never just start over with an import. When you import a bunch of still photos in one shot, no matter how many, it imports them all as an unwatchably fast 1 second video sequence instead of as an individual file. Like...what? And they've dumbed down the interface so much that there's no toolbar. You have to right-click poke at everything to try to find where stuff is. And right clicking is NON-EXISTENT on a Mac. I had to use a pen tablet to achieve it. I'm too cheap to buy Adobe Premiere for the few times I have to edit video in a year, so I guess it's just ShotCut on Windows for the rest of my life.