Register a SA Forums Account here!
JOINING THE SA FORUMS WILL REMOVE THIS BIG AD, THE ANNOYING UNDERLINED ADS, AND STUPID INTERSTITIAL ADS!!!

You can: log in, read the tech support FAQ, or request your lost password. This dumb message (and those ads) will appear on every screen until you register! Get rid of this crap by registering your own SA Forums Account and joining roughly 150,000 Goons, for the one-time price of $9.95! We charge money because it costs us money per month for bills, and since we don't believe in showing ads to our users, we try to make the money back through forum registrations.
 
  • Post
  • Reply
Sywert of Thieves
Nov 7, 2005

The pirate code is really more of a guideline, than actual rules.

sfwarlock posted:

No, the best part is when you say "I can't make it Tuesday at 9:30, I have a weekly team meeting 9-10 on Tuesday." and they reschedule it for 9:30 next Tuesday.

Not that that has ever happened to me...

My wife had literally this happen today. I heard her exclaim in frustration during lunch, turns out someone declined her meeting proposal and suggested another date/time. Wife could see this person was busy then, but accepted the proposal anyway.

Lo and behold, a day later (today) the other person declines this new proposal because it also conflicted. So yeah, no poo poo lady :argh:

Adbot
ADBOT LOVES YOU

The Iron Rose
May 12, 2012

:minnie: Cat Army :minnie:

xsf421 posted:

My first major project starting at the new company last summer was "hey, so we have this ancient ELK stack deployed via chef, opsworks, and cloudformation that hasn't been touched since 2018, could you do something about it?" My suggestion of "burn it all down and just ship everything to a logging PaaS" was unfortunately not taken seriously.

deploy a new eck cluster and do a remote reindex

It’ll still suck but it’ll be easier to manage that way

xsf421
Feb 17, 2011

The Iron Rose posted:

deploy a new eck cluster and do a remote reindex

It’ll still suck but it’ll be easier to manage that way

I migrated it to an aws open search managed instance and put logstash in eks. Handed the keys off to a dev team and now I’m trying to forget I ever touched it.

The Iron Rose
May 12, 2012

:minnie: Cat Army :minnie:

xsf421 posted:

I migrated it to an aws open search managed instance and put logstash in eks. Handed the keys off to a dev team and now I’m trying to forget I ever touched it.

Even better. Good luck with opensearch.

We use fluentbit -> cribl -> elastic and do all our log parsing at the cribl side… and it’s actually amazing?? I’m shook.

Also opentelemetry of course but that’s mostly traces not logs.

Silly Newbie
Jul 25, 2007
How do I?

The Iron Rose posted:

deploy a new eck cluster and do a remote reindex

It’ll still suck but it’ll be easier to manage that way

You can't convince me that these are real things and you aren't doing a bit.
Also I initially read that as "do a remote reindeer" and I'm not sure if that's better or worse.

Wibla
Feb 16, 2011

Oof, we have an elk setup for logging in an OT environment and we have to migrate it soon. F.

God of Mischief
Oct 22, 2010

Silly Newbie posted:

You can't convince me that these are real things and you aren't doing a bit.
Also I initially read that as "do a remote reindeer" and I'm not sure if that's better or worse.

You only do a remote reindeer when your elk cluster sheds and you need to collect velvet.

xsf421
Feb 17, 2011

Silly Newbie posted:

You can't convince me that these are real things and you aren't doing a bit.
Also I initially read that as "do a remote reindeer" and I'm not sure if that's better or worse.

My life would’ve been so much better for the past month if it was a bit. Turns out upgrading from logstash/filebeat 2.4 to 8.6 isn’t the easiest thing?

DACK FAYDEN
Feb 25, 2013

Bear Witness
Mandatory cybersecurity training at the new job has informed me that the correct response to "an email comes in from a senior executive asking you to click here to reset your password" is "call that executive to confirm the email is real".

Wonder how fast you'd get fired if you wasted a c-suite's time with that bullshit?

CommieGIR
Aug 22, 2006

The blue glow is a feature, not a bug


Pillbug

DACK FAYDEN posted:

Mandatory cybersecurity training at the new job has informed me that the correct response to "an email comes in from a senior executive asking you to click here to reset your password" is "call that executive to confirm the email is real".

Wonder how fast you'd get fired if you wasted a c-suite's time with that bullshit?

Very fast. Not to mention: Even taking that seriously I'd raise my eyebrows.

We've had to remind our support team this year that its not their job to reset passwords, we have a self-service application for that.

ponzicar
Mar 17, 2008
What a coincidence. In the one I just took, a manager suddenly asking for pictures of itunes gift cards apparently deserves only mild caution.

xzzy
Mar 5, 2009

The people that write training materials are sadists that love tossing in trick questions that would never pass actual scrutiny. The harassment/retalation one I took the other week spent pages telling us how we should report all incidents, then in the test section had a situation where a worker had her hours changed shortly after getting pregnant and reporting it would be wrong because maybe her boss just really needed her available 9-5.

Arquinsiel
Jun 1, 2006

"There is no such thing as society. There are individual men and women, and there are families. And no government can do anything except through people, and people must look to themselves first."

God Bless Margaret Thatcher
God Bless England
RIP My Iron Lady
^^^^
That's not a trick question, the company actually wants you to believe that is acceptable.

DACK FAYDEN posted:

Mandatory cybersecurity training at the new job has informed me that the correct response to "an email comes in from a senior executive asking you to click here to reset your password" is "call that executive to confirm the email is real".

Wonder how fast you'd get fired if you wasted a c-suite's time with that bullshit?
I've put together phishing training packages and reviewed other people's ones before they went live, and this reads like it heading up as far as someone who considers themselves a senior executive and then deciding to "take ownership" of something in the worst way.

Primus
May 14, 2007

Greater than the sum of his parts.

xzzy posted:

The people that write training materials are sadists that love tossing in trick questions that would never pass actual scrutiny. The harassment/retalation one I took the other week spent pages telling us how we should report all incidents, then in the test section had a situation where a worker had her hours changed shortly after getting pregnant and reporting it would be wrong because maybe her boss just really needed her available 9-5.

The Turbo Satan version of this is doing this training in a group via Teams call.

RoboBoogie
Sep 18, 2008
client freaked out when we only operate on the waterfall methodology and not in agile.


We were brought on to the project late and the customer's project plan has Sprint 1 ending on April 3. its April 11 and we still have not received any requirements.

Thanks Ants
May 21, 2004

#essereFerrari


Agile means you don't need old fashioned things like requirements and testing

Hughmoris
Apr 21, 2007
Let's go to the abyss!

RoboBoogie posted:

client freaked out when we only operate on the waterfall methodology and not in agile.


We were brought on to the project late and the customer's project plan has Sprint 1 ending on April 3. its April 11 and we still have not received any requirements.

What's more agile than a waterfall? Be Like Water

Wizard of the Deep
Sep 25, 2005

Another productive workday
In Agile™️, you don't get pedestrian things like requirements. You get User Stories, which compile into Epics.

I'm pretty sure you're the Hero in an Epic, so you must Suffer.

Just the rules, sorry.





Someone post the Agile Subway map again.

i am a moron
Nov 12, 2020

"I think if there’s one thing we can all agree on it’s that Penn State and Michigan both suck and are garbage and it’s hilarious Michigan fans are freaking out thinking this is their natty window when they can’t even beat a B12 team in the playoffs lmao"
Agile is rear end but tbh if you’re telling a client you operate with waterfall methodologies in TYOOL 2023 I’m assuming you’re selling mainframes or maybe abacuses

The Fool
Oct 16, 2003


Wizard of the Deep posted:



Someone post the Agile Subway map again.

SAFe and agile aren't the same thing

The Fool
Oct 16, 2003


that being said

vanity slug
Jul 20, 2010

The Fool posted:

that being said



mods??? trigger warning???

SyNack Sassimov
May 4, 2006

Let the robot win.
            --Captain James T. Vader


The Fool posted:

that being said



Heh you missed it buddy. Other poster meant the horrible abomination created by Deloitte. (edit2: might this have been in fact where the current title came from which REPLACED THE TITLE THAT CAME FROM A POST OF MINE I'M NOT MAD please don't put in the paper I got mad)

edit:

SyNack Sassimov fucked around with this message at 17:58 on Apr 11, 2023

The Fool
Oct 16, 2003


oh right, I remember that one now

ConfusedUs
Feb 24, 2004

Bees?
You want fucking bees?
Here you go!
ROLL INITIATIVE!!





I don't feel very SAFe anymore

The Fool
Oct 16, 2003


stealing a joke from the last time it was posted:

I'm "management 3.0" totally disconnected from any work

xzzy
Mar 5, 2009

The part that always slays me is the version number. They're so sincere about the value of that chart that they make updates for it.

Blue Moonlight
Apr 28, 2005
Bitter and Sarcastic

Christopher Webb is a sadist.

Hughmoris
Apr 21, 2007
Let's go to the abyss!

A pox upon their house.

RoboBoogie
Sep 18, 2008

i am a moron posted:

Agile is rear end but tbh if you’re telling a client you operate with waterfall methodologies in TYOOL 2023 I’m assuming you’re selling mainframes or maybe abacuses

Close, that three letter company which is super german

Wizard of the Deep posted:

In Agile™️, you don't get pedestrian things like requirements. You get User Stories, which compile into Epics.

but user stories are requirements.

Gatac
Apr 22, 2008

Fifty Cent's next biopic.
Gonna be That Guy and say that Agile is a good idea in theory, but everyone needs to actually want to do it and commit to it. Which means everyone needs to change how they work. And oftentimes the people in charge who Good Idea Fairy'd the organisation into Agile are the ones who least want to change the way they work; they just think Agile is a way for them to get whatever new Good Idea they had this week into production ASAP. Google "dark scrum" and marvel at the horrors.

A "user story" does not replace requirements. It's a short, hopefully easy-to-digest way to get at what the stakeholder wants to do and why they want it. It is the beginning of a conversation and a reminder of what the destination is, not the place where you nail down every detail. You wanna get at the nitty-gritty during refinement events, where you'll often see a wide spectrum of possible interpretations of the same set of words at play - and straighten it out into a common understanding, documented in as much detail as necessary. You also need sensible acceptance criteria that describe what the solution the devs come up with needs to do to pass muster. (Not surprisingly, a lot of those end up sounding kinda like unit tests at a conceptual level.)

If anyone thinks they can just pour a vague one-sentence description of a new feature into a dev team and get exactly what they need out of it, they're extremely mistaken on that point and need to be made aware of that. If anyone thinks they can perfectly divine what the stakeholder wants from a user story without talking to that stakeholder and deliver exactly that, they are also extremely mistaken.

Communicate. Refine more. Give stakeholders something tangible in Reviews and take their feedback seriously. Nobody gets it right the first or the second or even the third time. Agile means accepting that. The more you talk up front and the more you make your work transparent, the less work you need to throw out at the end of the day. And that's exactly the kind of laziness a good software engineer should strive for, imo.

Polio Vax Scene
Apr 5, 2009



The Fool posted:

that being said



AGILE RELEASE TRAIN

AGILE RELEASE TRAIN

AGILE RELEASE TRAIN

Arquinsiel
Jun 1, 2006

"There is no such thing as society. There are individual men and women, and there are families. And no government can do anything except through people, and people must look to themselves first."

God Bless Margaret Thatcher
God Bless England
RIP My Iron Lady
I feel like those two diagrams explain why so much of the modern world is terrible in really small ways.

God of Mischief
Oct 22, 2010

Gatac posted:

If anyone thinks they can just pour a vague one-sentence description of a new feature into a dev team and get exactly what they need out of it, they're extremely mistaken on that point and need to be made aware of that. If anyone thinks they can perfectly divine what the stakeholder wants from a user story without talking to that stakeholder and deliver exactly that, they are also extremely mistaken.


I see you've met everyone I've ever worked with. A constant issue brought up during sprint planning is that the stories are incredibly useless with no details and how can we possibly estimate them, but nothing changes.

i am a moron
Nov 12, 2020

"I think if there’s one thing we can all agree on it’s that Penn State and Michigan both suck and are garbage and it’s hilarious Michigan fans are freaking out thinking this is their natty window when they can’t even beat a B12 team in the playoffs lmao"
Ahh I disagree. Consulting is great. It’s taking money from amoral corporations and returning very little of value. Modern day Robin Hood’s

mllaneza
Apr 28, 2007

Veteran, Bermuda Triangle Expeditionary Force, 1993-1952




Gatac posted:

Gonna be That Guy and say that Agile is a good idea in theory, but everyone needs to actually want to do it and commit to it. Which means everyone needs to change how they work.

The Informatics group I work in had been trying to embrace Agile for years. A couple of years ago they figured out why it wasn't really working and went all-in on a clean-sheet reorganization. What they came up with seems like it should work out really well; it went live October 1 and we've been settling but are very explicitly not done yet. That's the first good sign, we know we'll have to make adjustments based on experience. The second one was pulling the four different Informatics groups out of their silos and putting them in one organization.

The new org structure is very flat. We have people in buckets called Chapters, Products go in Domains, and there is also a Catalysts bucket that's smaller but has the big idea people looking for global opportunities for improvement. Each chapter is broken up into Sections by specialty; all of the DBAs go in one section, the back end devs go in another, and so on. Over in the Domains live Product Owners and Managers, and the Project Managers. They spin up Agile teams to do work on their Products, and work with Section leads to provide the people for those teams. A lot of managers under the old system ended up as ICs in the Domains. The Catalysts do things like what my former Director is doing, one of his things is working with every department or site that had defined a standard laptop and coming up with one or two global standards (which would be down from about 20 now).

It's too early to be sure, the Product Owners are having to develop their product lines from scratch for example, but I think this is going to work out. It helps that we have the best of the leadership talent in senior leadership roles and as People Managers.

I expect I explained this badly, I sat through hours of presentations and have been living it for six months, so I probably skipped a lot of basic assumptions.

Wizard of the Deep
Sep 25, 2005

Another productive workday

SyNack Sassimov posted:

Heh you missed it buddy. Other poster meant the horrible abomination created by Deloitte. (edit2: might this have been in fact where the current title came from which REPLACED THE TITLE THAT CAME FROM A POST OF MINE I'M NOT MAD please don't put in the paper I got mad)

edit:


Thank you, yes. This Most Cursed Game of Mornington Crescent was what I was dreading thinking of.

Gatac
Apr 22, 2008

Fifty Cent's next biopic.

God of Mischief posted:

I see you've met everyone I've ever worked with. A constant issue brought up during sprint planning is that the stories are incredibly useless with no details and how can we possibly estimate them, but nothing changes.

There are two ways I can see to handle that. Either you do it the nice way and actively invite stakeholders to refinements, hash out all the vagueness in the stories and basically work out the acceptance criteria they should have written beforehand interactively with them. It takes up a lot of time, yeah, but two hours spent up front is nothing compared to throwing away a whole increment's worth of work because you didn't read the stakeholder's mind correctly.

Or you play hardball, come up with a formal Definition of Ready that defines the minimum amount of information you need in a backlog item to estimate it / plan it and tell anyone pushing for backlog items that don't meet your DoR to pound sand and come back when they've got their poo poo together. DoRs aren't a formal part of Scrum (unlike the Definition of Done) and it likely won't make you many friends, but if management is willing to back you on it, you can put the pain back where it belongs.

Either way, I'd advise you to impress upon management that results will not improve until backlog items improve. Maybe add a nice little report with an estimate of how much work you're throwing away / how many backlog items don't get done in the planned sprint / how poorly your story point estimates line up with actual time logged on that item.

ETA: Don't forget to slice, either. If you don't feel comfortable estimating a story, maybe it's just asking too much. Try to get from your stakeholder what they need to solve 80% of their problem, which is often much simpler. We've come to the point several times where we realized that chasing the last few percentages of Process Perfection was just not a good use of the time of several developers and project leads when it could just all dump into a "MANUAL DECISION" type of catch-all step and get individually reviewed by regular domain specialists.

Gatac fucked around with this message at 21:10 on Apr 11, 2023

Gumball Gumption
Jan 7, 2012

Gatac posted:

Gonna be That Guy and say that Agile is a good idea in theory, but everyone needs to actually want to do it and commit to it. Which means everyone needs to change how they work. And oftentimes the people in charge who Good Idea Fairy'd the organisation into Agile are the ones who least want to change the way they work; they just think Agile is a way for them to get whatever new Good Idea they had this week into production ASAP. Google "dark scrum" and marvel at the horrors.

A "user story" does not replace requirements. It's a short, hopefully easy-to-digest way to get at what the stakeholder wants to do and why they want it. It is the beginning of a conversation and a reminder of what the destination is, not the place where you nail down every detail. You wanna get at the nitty-gritty during refinement events, where you'll often see a wide spectrum of possible interpretations of the same set of words at play - and straighten it out into a common understanding, documented in as much detail as necessary. You also need sensible acceptance criteria that describe what the solution the devs come up with needs to do to pass muster. (Not surprisingly, a lot of those end up sounding kinda like unit tests at a conceptual level.)

If anyone thinks they can just pour a vague one-sentence description of a new feature into a dev team and get exactly what they need out of it, they're extremely mistaken on that point and need to be made aware of that. If anyone thinks they can perfectly divine what the stakeholder wants from a user story without talking to that stakeholder and deliver exactly that, they are also extremely mistaken.

Communicate. Refine more. Give stakeholders something tangible in Reviews and take their feedback seriously. Nobody gets it right the first or the second or even the third time. Agile means accepting that. The more you talk up front and the more you make your work transparent, the less work you need to throw out at the end of the day. And that's exactly the kind of laziness a good software engineer should strive for, imo.

Agile is good if your org knows how to implement it right but if you know how to implement it right you will have already stumbled into anyways without being explicitly told what agile is. Agile works for the sort of people who would have been naturally inclined to build something similar and really doesn't work for the folks who wouldn't.

Gumball Gumption fucked around with this message at 22:11 on Apr 11, 2023

Adbot
ADBOT LOVES YOU

CommieGIR
Aug 22, 2006

The blue glow is a feature, not a bug


Pillbug

Polio Vax Scene posted:

AGILE RELEASE TRAIN

AGILE RELEASE TRAIN

AGILE RELEASE TRAIN

CHOO CHOO ALL ABOARD THE WATERFALLAGILE!

  • 1
  • 2
  • 3
  • 4
  • 5
  • Post
  • Reply