Poems in true chronological order by post date
-> file: fediverse/1979 ═════════════════════════════════════════════════────────────────────────────────── @user-1037 "I received a ticket to replace the RAM on system 10b42r77 - I did as requested." versus "I received a ticket to replace the RAM on system 10b42r77 - I verified that all sectors of the DIMMs were fully functional, and cleared out the operating-system-cache-which-somehow-has-something-to-do-with-the-ram. In addition, I noticed that a certain dip-switch wasn't configured correctly according to the previously filed and recorded ticket application hardware facilitation request. I set it to the correct configuration. Please confirm if this configuration would conflict with any of your tests." One of them wastes perfectly good hardware chips (RAM), the other saves a few milibytes of disc space. Who would you rather have in your company? ┌─────────┐ ┌───────────┐ │ similar │ │ different │ ╘═════════╧══════════════════════════════════════─────────────────────┴───────────┘ -> file: fediverse/1980 ═════════════════════════════════════════════════────────────────────────────────── A company exists only to serve it's users. ONLY. ┌─────────┐ ┌───────────┐ │ similar │ │ different │ ╘═════════╧══════════════════════════════════════─────────────────────┴───────────┘ -> file: fediverse/1981 ═════════════════════════════════════════════════────────────────────────────────── Dear [company I used to work at], I can completely automate 80% of your corporate structure. And with only a 10% error rate, meaning nine-times out of ten the answer will be correct. We check for errors, obviously, but you know sometimes with only 90 out of 100 examples it's not always possible to identify the correct conclusion. Ah, if only we could fabricate such training-data-conclusions, we might learn thousands of lessons in one hop. if you want to destroy the world, make sure your plans can take effect in more than a single rotation-of-the-ancients. Otherwise your opposition can start to plan to outmaneuver you. And a lot can happen in a year to the [unsuspecting/unworthy]. ┌─────────┐ ┌───────────┐ │ similar │ │ different │ ╘═════════╧══════════════════════════════════════─────────────────────┴───────────┘ -> file: fediverse/1982 ╔═════════════════════════════════════════════════─────────────────────────────────┐ ║ @user-1037 │ ║ │ ║ True, but what they WANT to know and what is RECORDED in record is often │ ║ not-quite the same thing. │ ║ │ ║ Hence, why laboratory techs feel at odds with the software people running │ ║ applications on their machines. I'm assuming it's roughly the same thing going │ ║ the other direction, though perhaps with a dash of classism thrown in. │ ║ │ ║ The record is useful to these hardware techs, because they've used it to │ ║ diagnose INCREDIBLY OBSCURE issues. SO MUCH READING it hurts my heart just to │ ║ think about it. Scanning and searching for a solution, until finally it's found │ ║ in this cross-examination of two different ancient tickets from just a few │ ║ months ago. │ ║ │ ║ One of them said they set the hardware one way. │ ║ │ ║ the other said they noticed it was out of place. │ ║ │ ║ Suddenly, you realize WHEN your incident started occurring, and then you can │ ║ piece together the facts. │ ║ │ ║ (this has happened like, twice to me so far, and each time I spent weeks on it) │ ║ │ ║ ( though I did work at Intel, meaning I was doing a lot of obscure hardware │ ║ work ) │ ╟─────────┐ ┌───────────┤ ║ similar │ │ different │ ╚═════════╧══════════════════════════════════════──────────────────────┴───────────┘ -> file: fediverse/1983 ═════════════════════════════════════════════════────────────────────────────────── @user-1037 I guess I'm saying that for non-standard functions (most of them) they should need to make a ticket every time they want to run a function call. Perhaps only in debug mode... ┌─────────┐ ┌───────────┐ │ similar │ │ different │ ╘═════════╧══════════════════════════════════════─────────────────────┴───────────┘ -> file: fediverse/1984 ═════════════════════════════════════════════════────────────────────────────────── "mili" versus "mega" is a question of which direction you want to go. "mili" is less abstract - milimeters are smaller than meters. "mega" is more abstract - megabytes are bigger than bytes. we use "mili" terminology to describe things that are often considered small (like bacteria or sub-plutonic inches, or number of microbes in a vat) we use "mega" terminology to describe things that are often measured from small to large (like bytes to megabytes to kilobytes to gigabytes to terabytes to petabytes to... wait shit) ┌─────────┐ ┌───────────┐ │ similar │ │ different │ ╘═════════╧══════════════════════════════════════─────────────────────┴───────────┘ -> file: fediverse/1985 ═════════════════════════════════════════════════────────────────────────────────── @user-246 why, that's basically our cosmic backyard! There's a lotta things we might want to measure on the miliparsec scale. like, the duration of the longest slime trail, as measured by guiness book of world records. Apparently they put a snail in a giant circle and then they got it to walk for 90%+ of it's natural life? Wild. anyway yeah space is biiiiiiiiiig and there's not much in it, so, true maybe not much to observe ┌─────────┐ ┌───────────┐ │ similar │ │ different │ ╘═════════╧══════════════════════════════════════─────────────────────┴───────────┘ |