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.
Hot metal + arm = Smiley Face
You're absolutely right. For what it's worth, it's just the first part that's important.
When you pick up a new concept from a "resource" such as a tutorial, take a minute to explore the concept and understand the semantics of what you're doing. In the name of illustrating a concept tutorials can often be misleading in subtle ways.
An explanation of my "useless use of cat" example:
The command line has a concept called "piping". This lets one command send output to a second command. It's very handy. There is usually also a "cat" command, which will read a file and send the contents where you tell it. This is often your screen, or through a "pipe" to a second command. There is also a "grep" command that lets you search data for certain words.
Many "linux newbie" tutorials combine these tools to show how "piping" lets you send data from one command to another. "cat" some text file, then "pipe" the output to "grep" to search for your words. It usually looks something like cat ./my_address_book.txt | grep Giles to find lines in "./my_address_book.txt" that contain the word "Giles". The thing is that "grep" can take a file name as an argument. You can just do grep Giles ./my_address_book.txt, and cat is for concatenating files into one. If you want to simply read a file there are more appropriate tools such as "less". This by the way is the "useless use of cat"
When you're a newbie though, it may be the first time you're seeing either "grep" or "cat". The tutorial is just trying to show you "pipes". Along the way you're picking up these "bad habits". I've met professional sysadmins who didn't know grep took a filename as an argument. It was always "cat blah | grep my_search". I will see people type "cat /some/file | less" instead of "less /some/file". It shows a lack of understanding of what these tools actually do, and IMO it just comes down to regurgitating tutorial actions without bothering to understand the semantics of what you're being shown.
Don't follow tutorials, understand them. I'm so tired of seeing useless uses of cat because some asshole writing a tutorial 20 years ago decided to illustrate how pipes work with a good ol cat file | grep string as if grep didn't take a file name as an argument.
The more time I spend being mad about this the more I notice people using horrible practices in tutorials because they're too lazy to setup a legit use case.
A new user sees this and thinks this is how grep works.
Loops are another common one. People going around not knowing you can pass a glob to a shell for loop. Because the tutorial they read was lazily written and they didn't bother to understand the bits of what they were being shown, only how to reproduce/mangle the command until they manage to get close enough to what they want out of it.
Well logged in tonight and had the exact opposite experience for the first time since release day.
I think I may have just been unlucky with my time / zone choices.
My question is: What is it that I'm not understanding?
I'm really hesitant to be that twat shouting "Dead Game". We're still very fresh into a new release, I know that's not true. I can look up server population estimates. It's obviously not an accurate statment.
I am having a helluva time finding activity on the new maps. Commander/Mentor tags disappear seconds after I notice them. Events are over/failed by the time I arrive at the markers. Meta is consistently not getting completed. I hardly even cross paths with other players on these maps. They legit feel lonely and empty to me.
Yet when the daily is "Complete a renown heart" I can hop over to Kourna/Jahai and find activity no problem.
I'm on Gate of Madness fwiw. Is it my time zone/playtime? Are my expectations off? Am I just not getting how the new maps work?
I'm not looking to mindlessly follow a zerg for 100% of my playtime, but it's been really hard for me to do any of the content that isn't readily soloable. Despite what I know to be true (lots of folks are playing this expansion), what I'm able to observe is that I'm often the only player I see around these zones when I'm playing.
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.