201
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 02 Feb 2024
201 points (91.4% liked)
[Outdated, please look at pinned post] Casual Conversation
6466 readers
1 users here now
Share a story, ask a question, or start a conversation about (almost) anything you desire. Maybe you'll make some friends in the process.
RULES
- Be respectful: no harassment, hate speech, bigotry, and/or trolling
- Encourage conversation in your post
- Avoid controversial topics such as politics or societal debates
- Keep it clean and SFW: No illegal content or anything gross and inappropriate
- No solicitation such as ads, promotional content, spam, surveys etc.
- Respect privacy: Don’t ask for or share any personal information
Related discussion-focused communities
- !actual_discussion@lemmy.ca
- !askmenover30@lemm.ee
- !dads@feddit.uk
- !letstalkaboutgames@feddit.uk
- !movies@lemm.ee
founded 1 year ago
MODERATORS
I'm meeting up with a friend and their SO for a little hiking and brunch at a local breakfast joint. Picking up the vision pro today for work so that's exciting!
I think it's easy to be negative if a person doesn't consider the human reading their anonymous posts, people feel empowered to take out their problems from life in general on random faceless internet strangers.
Sounds cool! Hope you'll enjoy it!
Yeah, definitely. Hopefully in communities like this we can avoid that.
Not sure it's possible to avoid entirely, as the community here grows we get more of all types, it's hard to have a truly only-positive community when moderation is voluntary and the masses have full reign to submit literally anything.
Do you think a technology solution would help? Sentiment analysis on posts and gently redirect people to other communities instead of outright blocking them?
Maybe the only real solution is personal resilience and recognizing that we don't need to feel negative feelings just because we received a negative communication
You can't fix a people problem with process.
For example I've worked in DevSecOps for 10+ years, whenever consulting my first step is to implement a CI that picks up Pull Requests, builds them and runs a code analysis tools (e.g. pep8, spotbugs, eslint, etc..) and have the CI comment the Pull Request. The idea is to get an understanding of the projects technical debt and stop things getting worse and ensure the solution 'just works'.
Teams with huge amounts of technical debt will find a way to disable it when your not looking. They will develop all kinds of reasons and in reality the technical debt was created because of cultural issues in the team.
So I've learnt its important if you spot a team doing that, the solution isn't locking it down the solution so they can't disable it or more process. But forcing out the technical leader and sitting with the team and working out why each one is fighting the tool and not seeing them as an asset and teaching them to be better.
Earlier in my career the biggest lesson I learned was infosec was first and foremost a culture problem. Similar to your experience, working with people individually, meeting them where they are, listening, understanding, guiding, and modeling a better mindset all helps given enough time.
There are cases where some of those people just aren't willing to work with you. It's still possible to change the culture around them by influencing it more than they do. For every belligerent person, you can find one or more advocates
Yes, same experience here. People will go the path of least resistance except if you actively collaborate with them to make it work.
But in that same vein, recognizing how people operate means you can tweak or build a process to work with them and get results you want.
I'm not in a technical role like most people on this site, but I'm often in between those departments/their products and the consumer as well as the rest of the company. I think the mistake a lot of people in dev roles make is building a system that functions and think is good, and they need to bring the people to the process. But that's not how people work. You can maybe get a person, maybe even a few in line with your designed process. But when you have groups of people it becomes impossible.
Take that DevSecOps person above. Their solution to entire teams not using their process is to oust the leadership and bring the team to heel. I don't think that people take the time to think how they can alter their process to get the people more likely to work with it to get the results they want. As you said, people go the path of least resistance. You have to build your product to the user, not the other way around because the "people" aren't going to change.
My example: We had a process our level 1 team members needed to follow when filling out tickets. Most of the time, no big deal. Our system means their tickets need to be filled out and submitted almost immediately upon completion, they can't just wait around until the end of shift. It's a lot of real-time work. Occasionally we'd get hit by huge numbers because something vital broke and they're our front line in dealing with the communication, then these tickets would not get filled out properly in their mad rush to get them all submitted so they can move on. Every field not filled out correctly breaks our reporting, which is vital for us. Macros were no use because they could only fill out generic info and not any of the information we really needed. Their managers tried meetings and punishment and rewards, but when shit would hit the fan, inevitably the proper protocol would be the first thing to go to keep the operation running.
So I go in, take a look at the process start to finish and talk to the team about what specific things make it harder to complete in a crisis. And then I went and created a "mass issue" ticket form to use for those scenarios instead. When something major breaks and the team is flooded with these calls and they have to go through 4-5 at once every 10 minutes, they tick a box and get a new form with just the vital info and the ability to group as many issues on it as they have. Now they can group like issues together and fill out a single ticket. Their time is saved and we still get the precious data we need. Because we built our system to work with the user and made the path of least resistance a path that works.
But I have an advantage. I now work in a tech-adjacent role but I've spent my life working with people, not technology. So I get to bring that viewpoint to the job where most people around me have never really given it much thought.
DevSecOps is all about process, I simplified my answer.
At a high level in software there will always be a review phase, where code needs to be built and pass tests (as a minimum). With Git being used by every organisation I have been involved in you will find the organisation/team will claim to follow a variation of 'Feature branch Workflow' with review happening at a specific point (Pull Request).
For the last ~10 years every organisation/team I've worked in/with has claimed to use a CI to verify the source code as part of that review phase.
In most dysfunctional teams that review phase will be broken, the fastest win is to bring in the CI. Static analysis tools are also impartial in how they review and useful in teaching people how to review.
I don't say your project must build with no warnings, I say you project must build and I'll have the CI point out where you have added warnings as part of review. When people complain I'll point to their teams Ways of Working or an organisations Software Development Plan (or in one case a System Engineering Management Plan).
The sort of team that then chooses to disable this will do so because the leadership are undermining it (normally a team lead turns it off or tells them to just ignore it). There seem to be a few common reasons as to why team leads will do this but it isn't something you can rationally debate with. The only solution I've found is to sideline the problem, change team culture and identify a leader within the team and hand it over to them.
Your talking about teams which are failing due to the environment, those normally understand what is wrong and the best approach is to be a good scrum master (e.g. run retro sessions, identify issues and work to resolve the environment problems with them).
Very true, hopefully by the time we get there we'll have more mods tools to allow to identify bots and trolls.
Do you think a technology solution would help? Sentiment analysis on posts and gently redirect people to other communities instead of outright blocking them?
I'm not too sure, I'm always dubious about technology solutions for psychological issues.
Yes, I guess so, also why I made this post. I feel better already.