It sort of was debugging because I'd written a ton of stuff for them in 1-2-3 (on site). This was their accounting system for a small business and I was "debugging" something rather simple: they weren't getting all the columns printed on their dot matrix.
I agree with the parent poster and a ton of people do. Anyone who actually knows the story of the breaking of Enigma and Turing in general would know that that film is terrible.
I know a great deal about both, Turing being my scientific idol. I thought The Imitation Game was great, though not nearly enough postwar events and his trauma. I realize the title The Imitation Game was meant to be a double meaning, about both Bletchley's cryptographic attempts and Turing's attempts to feign heterosexuality, but the movie ultimately was about breaking encryption, not a study of homosexual life in a bigoted nation. I wouldn't personally call it a biopic. It's a sensationalized version of actual events because the real thing would've been boring. No one wants to watch me, by analogy, sit at a whiteboard beside a computer staring at symbols for eight straight hours.
I'm sorry you didn't get the biography you wanted.
I used to do this but stopped a very long time ago. I use KeePassXC instead. It’s much more secure and much better at handling websites with special password requirements.
There's custom wallpaper in the office which features elements of the other offices, but this is a fun idea. We do have a double pendulum and lava lamp elsewhere in the office, just not on the wave wall.
If your users need to resort to HN comments (or Twitter or Reddit or etc) to get a support issue fixed, something is definitely wrong with the pipeline. How many of your users out there have issues, but do not happen to see a random comment thread where someone from your team is participating.
Mistakes inevitably happen at scale. Sometimes they’re not caught by traditional channels. What I try and encourage is our leaders to take responsibility and fix them wherever they see them. Which is what John did above.
If the support side of things isn't scaling the same way the technology is, then maybe the whole business isn't "scaling". You can't just make one side work and then throw your hands up in the air and say, well, it's just too many user to have proper support. I mean, that's how it works but it's not how it should work.
"Whereever they see them" implies to me that it's not a systematic solution that is ever able to scale unless they scale their "leadership" the same way.
I don't think "wherever they see them" is the entire solution to scaling. I'd imagine that they have a whole system in place - an imperfect one because all systems are - that includes more than one part of it. That is "leadership fixes issues wherever they see them" is an component the system, not the system as a whole.
Even if you saw all the "cf fucked up" tweets/posts/etc, you still couldn't make that assertion without knowledge of all the times they didn't fuck up. People are far more likely to make noise about issues than things just working. This assertion is like assuming the starbucks corporation is incapable of producing a coffee people will buy because you saw a couple tweets about a messed up order.
