Antiwork/Work Reform
A community for those who want to end work, are curious about ending work, want to get the most out of a work-free life, want more information on anti-work ideas and want personal help with their own jobs/work-related struggles.
Active stats from all instances
Subscribers: 2.9k
Date Created: June 15, 2023
Date Updated: July 17, 2023
Library copied from reddit:
The Anti-Work Library 📚
Essential Reads
Start here! These are probably the most talked-about essays on the topic.
- The Abolition of Work by Bob Black (1985) | listen
- On the Phenomenon of Bullshit Jobs by David Graeber (2013) | listen
- In Praise of Idleness by Bertrand Russell (1932) | listen
c/Antiwork Rules
Tap or click to expand
1. Server Main Rules
The main rules of the server will be enforced stringently. https://lemmy.fmhy.ml/
2. No spam or reposts + limit off topic comments
Spamming posts will be removed. Reposts will be removed with the exception of a repost becoming the main hub for discussion on that topic.
Off topic comments that do not pertain to the post at hand may be removed if it is deemed they contribute nothing and/or foster hostility at users. This mostly applies to political and religious debate, but can be applied to other things at the mod’s discretion.
3. Post must have Antiwork/ Work Reform explicitly involved
Post must have Antiwork/Work Reform explicitly involved in some capacity. This can be talking about antiwork, work reform, laws, and ext.
4. Educate don’t attack
No mocking, demeaning, flamebaiting, purposeful antagonizing, trolling, hateful language, false accusation or allegation, or backseat moderating is allowed. Don’t resort to ad hominem attacks against another user or insult other people, examples of violations would be going after the person rather than the stance they take.
If we feel the comment is uncalled for we will remove it. Stay civil and there won’t be problems.
5. No Advertising
Under no circumstance are you allowed to promote or advertise any product or service
6. No factually misleading information
Content that makes claims or implications that can be proven false or misleading will be removed.
7. Headlines
If the title of the post isn’t an original title of the article then the first thing in the body of the post should be an original title written in this format “Original title: {title here}”.
8. Staff Discretion
Staff can take disciplinary action on offenses not listed in the rules when a community member's actions or general conduct creates a negative experience for another player and/or the community.
It is impossible to list every example or variation of the rules. It is also impossible to word everything perfectly. Players are expected to understand the intent of the rules and not attempt to "toe the line" or use loopholes to get around the intent of the rule.
view the rest of the comments
That's a lot of changes in four months, is it possible that you made people uncomfortable with the pace of change? Were the other workers able to effectively use the changes you implemented?
I was thinking similar. How much of this was communicated, vs just done without asking. Were there considerations like "does company want their code on GitHub?"
I presented a report after my first two weeks on the changes I recommend. They discussed this with the team, the IT guy, and the CEO. The CEO thanked me for caring enough about the organization to put this into writing. I didn't get everything I suggested but we got the important things. My plan was to get the team used to the tools I suggested before going on to other tools. All of their code wasn't on Github because they had secrets hard coded in there so I only put new projects I created on there. I taught them the importance of environment files to keep passwords from git history. I only wanted to improve the place where I worked.
Not sure what might have happened then. Sounds like you took the right approach.
FWIW as a software engineer for 20 years including some time as Principal, this is kind of like, my thing. Identifying areas of improvement, presenting a use case, and implementing based on that. Some people can get really upset if they're not involved in that process. Like, complain to the CEO upset.
If that's not the case here, then it's not. It is a bit of a red flag simply because that amount of change can be very difficult to impart in such a short time. Props for your contributions for sure.