210
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 23 Jul 2024
210 points (95.7% liked)
Asklemmy
44152 readers
1420 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
"Do this as a temporary measure. We will code it properly later" ---> code that is hackish and will never be replaced.
"We need you to do this one time because of someBullshit" ---> congratulations, your team had to do this thing outside of your specialty, even though there exists a team dedicated to it, and now we're just going to make you do it over and over again (despite, again, a whole team dedicated to that existing).
I'm always blown away whenever someone says that they like some language or framework because it's "great for prototyping."
Like, what magical fairyland software company do you work at where your prototypes are not immediately put into production as soon as they kind of start to work?
You should tell them this is not 'Nam. There are rules.
These are older lessons and I'm generally pretty effective at pushing back on those now. I'm not a manager, though, so I can be overruled.