No Stupid Questions
No such thing. Ask away!
!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules (interactive)
Rule 1- All posts must be legitimate questions. All post titles must include a question.
All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.
Rule 2- Your question subject cannot be illegal or NSFW material.
Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding META posts and joke questions.
Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.
On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.
If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.
Rule 7- You can't intentionally annoy, mock, or harass other members.
If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.
Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- Majority of bots aren't allowed to participate here.
Credits
Our breathtaking icon was bestowed upon us by @Cevilia!
The greatest banner of all time: by @TheOneWithTheHair!
view the rest of the comments
Oh boy that would be a nightmare.
Don't get me wrong, I can easily imagine a working environment where everyone is a professional and everyone is making well reasoned responsible decisions with their hardware. Such workplaces exist.
But in reality there are any number of reasons why individual workers shouldn't have unlimited access to their machines or others in the pipeline. I've worked mostly in corporate (financial) software environments, but many of these things apply to all workplaces though many places will be far more relaxed (or disorganised)
A few off the top of my head:
Data loss - irrespective of who anyone is, they shouldn't be able to plug removable media into a machine and download the production database without being noticed. Likewise, for everyone's safety, no-one should be able to plug a usb stick they found into a machine connected to the network. Exceptions can be sought, and granted, as part of an audited process. Anecdote: I worked one place where we were due to continue working over the weekend and a business analyst took client data home with them on an unencrypted usb stick.
Verified software - people shouldn't be able to download and execute whatever they feel like as this offers a huge attack surface. Many companies maintain a list of verified software and install this centrally rather than allowing people (even developers) to download it and install it themselves. Again exceptions can be granted. Anecdote: one place I worked, an member of the infrastructure team had installed bitcoin miners on company servers.
Stability - developers generally do not have access to the production environment, running deployments is the responsibility of a dedicated team, this is because the temptation to meddle when in a pressured situation is too great. Anecdote - at one bank I worked at I made a mistake in a package of changes I'd prepared. The person running deployment came and told me and - because of a particularly time sensitive issue - we went and figured out the issue at the point of production deployment and fixed it manually. This worked but was exceptionally irresponsible. At a different place I worked, early in my career, I made a similar hacky fix and took down the public website of a major UK utility provider for several days
Quality - the software development process has many checks and balances between areas of expertise designed to bring out the best even if it's more frustrating getting there. Want to change the indexes on the DB? Got to convince the DB admin that it's the right thing to do, can't just do it myself. Want to close that ticket that's way overdue? Can't unless QA / testing approved else I'm just marking my own work. Want to make changes in the integrated dev environment because that's far easier that developing against the out of date mocks in my own sandbox? Nope. Want to expose a new endpoint for my services to talk to unilaterally? Nope, need architectural sign off, network security signoff, and the infrastructure team. Anecdote: All of these have been areas where I, a reasonably skilled developer, would have compromised in various points in my career when my back was against the wall and I was under pressure to deliver.
Some corporate environments can be suffocating, other software places can be so lax as to be alarming. In my experience there's a sensible balance in the middle and the best places to work have been where management is sensitive and reactive to the needs of developers to get the job done in as reasonably a safe way as possible.