*NIX enthusiast, Metal Head, MUDder, ex-WoW head, and Anon radio fan.

  • 0 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle

  • I do greatly appreciate my management and general company tech culture, they’re great.

    I agree with your stance here, because it’s part of my point. I tend to see more people bitching about Agile itself and not management or their particular implementation.

    The jobs where I was only given enough info to plan 2 - 4 weeks out were so stressful because I frequently felt like I was guessing at which work was important or even actually relevant. Hated it.

    Turns out it’s a skill issue ;p (on the management level to be clear). Folks, don’t let your lazy managers ruin you on a system that can be perfectly fine if done right.



  • 2-3 sprints?! Y’all really flying by the seat of your pants out here huh?

    My teammates and I have no trouble planning multiple quarters in advance. If something crops up like some company wide security initiative, or an impactful bug needing fixed, etc then the related work is planned and then gets inserted ahead of some of the previously planned things and that’s fine because we’re “agile”.

    I delivered a thing at the end of Q3 when we planned to deliver at the start of Q3? Nobody is surprised because when the interruptions came leadership had to choose which things get pushed back.

    I love it. I get clear expectations set in regards to both the “when” and the “what”, and every delay/reprioritization that isn’t just someone slacking was chosen by management.




  • That’s my bad, I asked an incomplete question.

    What does the approach of spawning a grep process and having ls send ALL of it’s output to grep have over just passing a glob to ls?

    Like:

    $ ls /usr/share/*.lm
    
    /usr/share/out-go.lm  /usr/share/ril.lm     /usr/share/rlhc-crack.lm   /usr/share/rlhc-d.lm   /usr/share/rlhc-java.lm  /usr/share/rlhc-julia.lm  /usr/share/rlhc-ocaml.lm  /usr/share/rlhc-rust.lm
    /usr/share/ragel.lm   /usr/share/rlhc-c.lm  /usr/share/rlhc-csharp.lm  /usr/share/rlhc-go.lm  /usr/share/rlhc-js.lm    /usr/share/rlhc-main.lm   /usr/share/rlhc-ruby.lm
    


  • What’s the benefit of spawning a subshell and executing “ls” here instead of just passing a glob to your loop?

    $ for lol in /usr/share/*.lm;do printf "I found a file named '%s'\n" "$lol";done
    
    I found a file named '/usr/share/out-go.lm'
    I found a file named '/usr/share/ragel.lm'
    I found a file named '/usr/share/ril.lm'
    I found a file named '/usr/share/rlhc-c.lm'
    I found a file named '/usr/share/rlhc-crack.lm'
    I found a file named '/usr/share/rlhc-csharp.lm'
    I found a file named '/usr/share/rlhc-d.lm'
    I found a file named '/usr/share/rlhc-go.lm'
    I found a file named '/usr/share/rlhc-java.lm'
    I found a file named '/usr/share/rlhc-js.lm'
    I found a file named '/usr/share/rlhc-julia.lm'
    I found a file named '/usr/share/rlhc-main.lm'
    I found a file named '/usr/share/rlhc-ocaml.lm'
    I found a file named '/usr/share/rlhc-ruby.lm'
    I found a file named '/usr/share/rlhc-rust.lm'