

“nnnnn-ghinks”
“nnnnn-ghinks”
I believe you. When my ex got a laptop, literally every folder was onedrive. Even system folders were mapped to onedrive it was ridiculous. I had to backup all her stuff and manually fix the fuckery in the registry editor before i could uninstall onedrive.
The screenshotted tweet was from dec 20th. The linkedin post from dec 9th. You can see them in the link to his linkedin post in another comment.
Maybe I dont want a promotion? I just wanna write code and get paid. Please dont give me more responsibilities.
I dont care if the feature I’ve worked on gets canceled. The lost work is management’s problem, not mine; I still get paid the same.
If you read the books, you’ll find that you’re not far off.
The crab will consume all. I need to get out of software development before I can’t hide any longer.
That was 8 years ago, and now he has a crab avatar…
🦀 🦀 🦀
Just run your prod env in debug mode! Problem solved.
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.
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
Thas not the AI though, thats a snippet from an article about how google search is shit now
7 unit tests should be enough I think
It happened. But ok if you say so.