Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about current US Politics. If you need to do this, try [email protected] or [email protected]
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Software engineers, supposed "experts", can't even agree among each other how to structure and build software, let alone agree with project managers, users and other laypeople.
Source: Am software engineer.
Structure and build? Look at the guy using Waterfall instead of Agile development.
Source: Am also software engineer.
I'd call it healthy debate but I've never met a software engineer who had a healthy anything
In my experience there are two types of software engineers. Those who are narcissistic and believe their own bullshit and those who suffer from crippling imposter syndrome. Few can agree on what is the best way to do things but most will agree to do things the wrong way for money.
Crazy thing is that doing it the wrong way is the best way to have job security. Fire me? Yea, well, you'll never find anyone else that knows this spaghetti as well as I do.
I was brought in to a place where the guy had pulled out all the comments and replaced all the variable names with random strings. Saved himself on his personal USB stick the real code.
That’s because whatever system you’ve got now feels old and tired, but that new system that just came out looks so new and useful. I mean, it can’t hurt to change the entire thing half way through development again, right?