381
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 27 Sep 2024
381 points (94.6% liked)
memes
10308 readers
1016 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 1 year ago
MODERATORS
No, actually it's not. It's actually well know how Japanese culture actually affects programming. I, a software engineer who has worked with many other cultures, can confirm that culture affects quality. I'm not saying I'm perfect, but I am saying that culture affects work.
Indian culture is interesting because you never say no to your boss. Even if you don't understand something, or don't have all the information you need, you say yes. Do you understand? Yes. Are you sure, it's okay to ask me clarifying questions. "Yes, I'm sure". Then they give me something that doesn't work because they didn't understand the question.
Japanese is another culture that's slightly different, but if your boss asks you to do something not only do you say yes, you also don't ask for help to do it. You brute force it done, put in long hours, and you get it done. However, in software that's a horrible way to operate because we need to not just get the current problem done, but you need to build something that others will use later, that will be reused, that will be expanded and shared with and by other teams. So what you get is quite literally this - poorly optimized code from many people whose code doesn't really work well together.
So, none of these are stereotypes. In fact, as engineers it would be culturally insensitive if I wasn't aware of this and assumed people worked in the same way as Americans. Your virtue signalling is pretty transparent. Yes, it's humorous, but it's also 100% the truth. They're not bad coders, but their culture does not breed great software projects.
You talk like Nintendo games weren't optimized to hell and back.
Edit: I meant games developed by Nintendo. Pokemon is developed by Game Freak.
They haven't been optimised in over a decade at this point.
Have you seen TotK, Mario Odysee, etc.?
Have you seen them?! Obviously not.
Come again?
They are all technically a mess.
How? How is a game that would have been considered impossible on the hardware "technically a mess"?
Have you seen the pokemon games?
Are those developed by Nintendo?