I also "misuse" timewarrior a bit and use it to time things like "how much time do I spend waiting for salt to run". That has its own timewarrior db and a wrapper function for pointing the command at said db. I use this in both login and non login shell contexts.

All of the repos for my GitHub sourced vim plugins live under one parent directory. I symlink to them from ~/.vim

One example is a simple function that pushes the top level repo directory onto my dir stack and then runs a loop where it pushes each subdir into the stack, runs "ggpull" then pops back to the top level repo directory. ggpull is an alias added by the zsh git plugin. After all repos have been updated it pops back to my original pwd.

I run this as part of my "update all the things" script but sometimes I also want to run it in demand from the cli. So I want this function in all scopes and I want it to have access to "ggpull" in all of those scopes.

It's all about context. If you write a convenience function and put it in zshrc, scripts you run from the cli will not have access to the function as defined in zshrc. Same with aliases added by zsh plugins etc.

If you need "the thing" on the command line, zshrc. If you also need it in scripts you run from the cli, toss it in the profile file.

ETA: I personally keep the functions I want to access from scripts in .zshenv as I recall reading that this file is ALWAYS sourced.

E

5

I want to add: 2-3 sprints ahead is a GREAT begining goal for a team trying to get started with Agile.

Long term though let's set that bar higher :D

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.

Why do people do this? There is neither a clubhouse sandwich or any fries in this image.

This looks like a great lunch but why is it so common to call things what they aren't? "Fries" isn't a shape. Apple sticks? Slices? Roughly julienned apples?

Put pork flavoured soy on whatever you want, but why the need to call it vegan bacon ya know?

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.

Yes

Hot metal + arm = Smiley Face

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 purpose of a pipe and an execution of "grep" here?

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'

File extensions are just a text based convention. Renaming a file to end in .PDF does not make the file a valid PDF.

You're really saying there's no way for a posix shell to take the text to the right of the last "." character and then do simple string comparison on the result?

Also why can't you just use normal globbing to feed arguments to your command? Why do you need to involve flow control?

Configuration management and build automation are definitely worth the time and effort of learning. It doesn't have to be ansible, find which tool suits your needs.

Ah yes, the core definition of communism: a small farm offering a delusion of independence, which is run within a capitalist system.

The AJFA book is full of nothing but lies. Buy another blunt or something instead ;p

Same here. Reference, particularly sheet music and cooking recipes work fine for me digitally.

I can sit at the computer and read social/news media for hours with no problem, but the way ebooks are displayed tires my eyes very quickly for some reason.

While I don't have this issue with the e-ink/e-paper stuff, I've never owned one. I also appreciate that physical books are often much harder to damage and will work without electricity.

This topic is addressed in the first paragraph on the linked page.