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. This includes using AI responses and summaries.
Credits
Our breathtaking icon was bestowed upon us by @Cevilia!
The greatest banner of all time: by @TheOneWithTheHair!
view the rest of the comments
Software engineer.
Morning meeting that's supposed to just be "what you did yesterday, what you'll do today, and if you need help". People fuck that up and go off on tangents. What should be a ten minute meeting takes 30.
Product owners at some point told you what the features to work on this month will be. For example, we need to add the ability for some reasons to bulk delete appointments.
Chat with product and other engineers about what that entails. Product probably won't give complete, clear, requirements so you need to pull it out of them. (Hard delete or soft delete? Do you need an audit log? Are you sure with no take-backs you don't need an undo? Do you want to notify anyone when it's deleted? One email per request or per event? Do you have designs for that email? No? Of course not. And what do you want the UI to look like? If I "just put a button somewhere" we both know you won't like it. Give me details or that blank check in writing.)
At some point sit down and make code changes to do the thing. Change the backend server code to accept your new request. Write automated tests. Change the frontend to make the request. Write more tests. Manually bang on it. Probably realize some requirements were missed (you guys know there's a permissions system, right? I hooked this up to the existing can-delete permission. What do you mean CS doesn't use permissions? You made them all superusers??)
Manually bang on it a little. Deploy it to dev or some non-production environment. Have product and other stakeholders look at it and sign off. Probably get feedback and either implement it, or convince them to do it "later" (or: never, because they'll forget and it's not actually important).
Get code approval from other engineers. Make changes as needed.
Merge and deploy. Verify in production.
Meanwhile, do code reviews for other people's work. Context switch. Feels bad. Other guy is working on a progress report tool that's in a whole other part of the code, so every time you look at it it's a shifting of brain gears.
Also look at dependabot for libraries that need updating. Read release notes. Make changes if needed. Test. Pray.
Also periodic meetings to go over work in the backlog. A meeting to discuss how the team is doing that usually doesn't produce results, but can be a vent session.
I imagine from the product owner it's something like:
Get a mess of contradictory ideas from leadership. Try to figure out what they actually want and in what order. Manage their emotions because they have all the power and don't like being told no or otherwise feeling bad.
Talk to customers and other users. Try to figure out what they want. They say things like "make it go faster" or "can you make the map bigger?". There's no map on the website.
Talk to engineering. They ask so many questions. Why can't they just do the thing? They're always going on about stuff that doesn't seem important (like security and permissions and maintainability). This needs to go out Friday because the CEO wants it out.
Write tickets (a short document describing work to be done). People don't read them. Or maybe don't finish writing them, and leave a vague "as a user I want to be notified about changes to my project", without specifying any details. (Notified how, Ryan??)
I don't know what else they do.
Startups are a mess. Anyone who says they want to run the government like a startup should be banished from the land.
How did my boss come to embody every other department/group that you work with!? Literally one guy, fighting with himself about the ideas he wants and failing to communicate it while complaining that the solution should be simple and easy while making meetings drag on...
As a former software engineer turned product owner turned manager, thank you for including other perspectives. When complaining on the internet, engineers typically think other people should be doing all the specification work and they just implement it, without realizing that in the pre-agile days, the bureaucracy was soul-crushing. We need engineers to discuss all these technical details like permissions and whatnot, they're the best people for the task! But at parties, engineers talk about this as if management is stupid for not working it out for them. No, software engineers shouldn't try to reduce themselves to code monkeys. You're problem solvers, you're engineers.