Read the code when it matters.
The skill to hone is knowing when it does.
Start with 'never read for a prototype, but read for anything else' . Extend that range as seriousness rises.
Scale wise, the times you should be reading the code will dwarf the times you shouldn't.
@benspringwater It's done that stuff for YEARS. You don't need 3000 engs doing 1.5 tasks A DAY to maintain.
I'm sure their software looks like an iceberg - 10% visible, 90% how the donuts are made - but that scale of commits should map to customer satisfaction going up, not sideways (or down).
@janaka_a@VicVijayakumar Oh for sure! I think the natural order for any internal tool is constant bit rot. They're all little countdown timers that love to reach zero at the most inopportune moments.
@AdamRackis Well, I think what most people think is wild is that y'all are shipping that many commits and from our point of view it doesn't equate to anything thats bettering the product. The UX horrendous.
Feels like Spotify could get the Elon treatment.
What about partial doxxes?
For instance, if I said your head is up your ass, I’m really only doxxing your head.
The whereabouts of said ass are currently unknown, but they were last seen being booed off stage. Is that enough of a delay on the location?
I have a tear in my eye that this Donald J. (J stands for JOBLESS) Trump Jr. jackoff has a tear in hos eye!
THE DAY IS FINALLY HERE FOLKS!
@iamrapaport podcast Inauguration EP is LIVE & Spectacular @hearluminary
📡: https://t.co/Q8XeE6KyIf
BEFORE: “The Rebels are being hysterical. We would never ACTUALLY blow up Alderaan.”
DURING: “Now isn’t the time to play politics and talk about the destruction of Alderaan.”
AFTER: “We need to move on from Alderaan to begin the healing for the good of the galaxy.”