• 0 Posts
  • 7 Comments
Joined 3 years ago
cake
Cake day: June 14th, 2023

help-circle

  • That’s great, and you are correct. Even just a paper trail is helpful even if you resolved the issue internally. What I meant is that there’s this specific type of person who thinks that just because they’re young or x or y that they know more than they do. And that unearned confidence is a killer! I don’t mean that they’re creating tickets to document problems, I mean they are so confident that they don’t need IT that they end up turning little issues into big issues. And the whole time you’re there trying to fix the problem they caused, they’re acting like you guys are on the same page and they’re being helpful when really they’re so incredibly in the way it’s exhausting.
    Like the guy who tries to fix his plumbing issue but makes it worse, then stands over the Plumber the whole time like “Yep, exactly, I knew that was the problem” “Yep, that’s what I was going to do” Except the plumber can fire that customer.




  • [PIPEGEN v0.42] Initializing procedural pipe renderer
    t=0.000s
    Origin pipe spawned at (0,0,0)
    Radius: 1.00
    Color: teal
    Direction vector: (0.00, 1.00, 0.00)
    t=0.217s
    Pipe extended to length 3.4 units
    Current position: (0.0, 3.4, 0.0)
    Color: classic teal
    Specular highlight: implied
    t=0.491s
    Elbow joint inserted
    Rotation: +90° on Z-axis
    New direction vector: (1.00, 0.00, 0.00)
    t=0.944s
    Secondary pipe spawned
    Parent junction at (0.0, 3.4, 0.0)
    Radius: 0.85
    Color: common teal
    t=1.302s
    Primary pipe length: 7.9 units
    Secondary pipe length: 2.1 units
    No collisions detected (optimism high)