The images are not actually the captcha. They’ve used other methods and tools to verify your authenticity, then they force you to help train their image recognition AI under the guise of it being the actual captcha. Its Distributed Forced Labor, and Google has been using captchas to do this for decades. Remeber the picture-of-two-words captcha? One word was always squiggly and the other was not. The squiggly word was the real captcha, the other word was from a scanned book and you were helping to train their OCR algorithms.

I disagree. The teabag is a welcome replacement to having to have yet another unitasker in the kitchen.

No, that complicates things way too much. Simplicity in design is beauty. A real engineer would recognize the tag on the string not only as a point a confusion, but also a superfluous feature. Simply remove it. The end user will have to use a spoon supplied by themselves to remove the teabag, but thats their problem. At least there is actually tea in the cup at that point.

I think he overreacted a bit, not to having his package name forcibly taken from him, but to being asked to give it up in the first place. Kik explained to him that they have to fight this or lose their tradmark because thats how trademark law works. His response was basically “haha fuck you”. He probably could’ve asked for a couple thousand and just changed the name of his project and everything would’ve been fine.

All metrics are terrible when used for anything other than objective analysis

Ive heard of stories where people would have an imposed test coverage percentage requirement… and they would just have a single dummy method that printed “.” to the console thousands of times. They then have a single test for that one method, and whenever their codebase grows to big, they add more lines to it so that the dummy method has enough lines to meet the test coverage requirement.

One time when I was contracting and my company was in the middle of a merger I had to do triple time keeping; client, old company, new company, all on different systems, two of which were ancient hr software from the 90s for some reason still in use 5 years ago. Its at that point I just started blanket logging 6 hours per day on whatever project I could think of at the moment.

In my first programming job, I would actually do code reviews by pausing my own work, pulling their branch and building it locally, then using debug mode to step through every changed or added line of code looking for bugs, unaccounted for edge cases, and code quality issues.

…I dont do that anymore, I now go “looks good to me” even on 10 line reviews.

No fiting. IS always goes at the start of names for booleans you are correct

7 unit tests should be enough I think

Meanwhile webstorm/intelliJ users:

signature look of superiority

empty wallet