This is certainly a fun exercise in economics. By taking a shortened work-week, should the companies then pay us 80% of our current comp? Or maybe a little less since they will have to pay for the added tokens we are now using as part of our job that we used to do manually (i.e. time)? Or perhaps we are able to justify that now they can save overhead by reducing facilities costs by 20% as well. Oh but maybe their business lease has a continuous occupancy clause and now the reduction in foot traffic causes them to get penalized so they need to reduce our salaries even more. Slippery slope my friend.
No. They should give you 40x your current pay. The AI made you 10x more productive, and you worked four days, so you generated 40x the economic output. As such, you should get 40x in pay. At this point, you're doing the company a favor by taking a day off as otherwise they wouldn't be able to afford you.
You wrote a lot of words, but none of them describe a slippery slope, or explain how a supposed 10x increase in productivity precludes a 20% reduction in hours worked.
From your statement and the parent comment, just learned that "cargo cult" is a thing, but cargo-culting as a compound is something AI has made up? [1].
As I was educating myself, I found Richard Feynman's Commencement Speech at Caltech in '74 [2] that might have coined this for our industry? If you would rather listen than read [3]. Posting this for others curious on the term.
Thanks for this! I confess I've heard of cargo culting for a long time but never thought too much of it. Seemed like an idiom like any other. The talk is fascinating, and describes attitudes I see all the time in the industry and at work, and they bother me. Now I know they are also cargo culting. That will hopefully help me steer people away from those practices.
By default Windows 11 will not run an untrusted .exe/PE file - it's governed by Microsoft Defender SmartScreen that will present a pop-up scaring people away and it actually isn't intuitive to click-through to run the program unless you've done it before.
But after enough people run it, that disappears. They implement crowdsourced trust, because it isn't a rent extraction exercise but actual concern about malware.
It's fun to think about tile dilation per the exif captured Create Date: "2026:04:03 00:27:39.26". I know it's negligible over the trip, but when they took it, was their time really "2026:04:03 00:27:39.25"?
Their master diagram example in #3 contains a #2 mistake with an unconnected resource (the stripe account). Maybe a double validation of why the master diagrams can be hard to maintain.
"Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL."
Interesting they are listing archived projects and not OSS-Fuzz. What's the reason for this?
