I think this is conflating opensource-corporate and english-non-english.
If you ask american/european/english-speaking developers about coding, it will mostly be about/in the context of corporate environments rather than open source too! The majority do not actively or primarily contribute to open source projects, but instead corporate environments as well.
In an alternative timeline where the lingua franca isn't english, I can still see open source culture exist; I don't think the desire to publish and cooperate in public is an inherently "western" culture. It will also run into the same conflict of interest between Open-Source and Corporate: one prefers transparency and full-disclosure, the other prefers control in the interest of minimizing risk.
You're right. Ultimately, the absolute number of developers matters a lot. But when it comes to coding style and paradigms, it's overwhelmingly dominated by the English-speaking world.
For example, object-oriented programming or conditional statements generally follow a What -> Action -> Target order. But my native grammar follows a What -> Target -> Action order. So I have to translate SOV logic into SVO code syntax.
The reality is that English speakers are numerous, Japanese and Korean speakers are relatively few, and while Chinese speakers are quite numerous, there's still some cognitive load due to differences in thought patterns. It's almost like a difference in the sheer volume of accessible knowledge.
Due to the cumulative cost of translation, this feels like a bigger hurdle than people realize.
So sometimes language gives a sense of identity tied to 'ethnicity' and 'nation,' but when it comes to the competition for knowledge, I feel that the number of native speakers matters more. There are points where I agree with you, and points where I don't. It's complicated
Having messed with RPG Maker formats recently, I find this fascinating because it's so much more elegant and nicer looking.
Though it seems like it's more suited to fully text based scripts. The format I was messing with was full of markers to e.g. change the facial expression of the speaker's portrait, play sound effects, etc. (mid dialogue!)
Makes me think about how script/dialogues are written and formatted internally in other mediums. Umamusume in particular stands out in my mind; it has a lot of movement and actions as the dialogue lines are spoken. Sounds silly but they really do make it feel more dynamic and alive.
Loreline does have tags to address this. When you plug the language to an actual graphics/game engine, you can use them to change how you display things:
barista: <concerned> That's a lot of coffee...
<- use "concerned" tag in the engine to display a concerned face
It is certainly my biggest dislike factor with my stay in Germany, and I'm still struggling to come to terms with it: do I dislike it enough to compel me to move away? is this something I can accept? How much can I influence and improve things that I directly interact with?
It seeps in everywhere too, with almost all aspects.
Day-to-day with restaurants, cafe, shops. Almost all interaction feels like it's actively checked if it's in their process or job description. Shop staffs are typically disengaged and can't really help you with anything outside the normal process.
Healthcare, both receptionist and doctors. You can see the rushed service because they are only compensated for limited amount of time by the state insurance. This took me a while to figure out; the process really defines what treatment you get, with what equipments, as well as the duration, and they have to do their best with the constraints put by the process.
An example: with Wurzelkanalbehandlung, the process says (at least back then) only 1 hour of Laborkosten can be compensated by the state insurance. This means if the dentist took more than 1 hour to work on you, that would be done at their personal loss, and thus the incentive to rush the procedure.
Going private helps (they tend to be more relaxed after the mention of of Privatzahler, and gives you access to newer equipments not yet acknowledged by the state insurance processes), but you still have to research, find, and pick the right practice.
Bureaucracy, administrative. You often have to deal with clerks that just go "I just work here", the rules says this and there's nothing I can do, throws hand in the air. Goodbye, next person please!
In day-to-day work, I can also see it. New hires tend to be more into the work, and questions things, but the system does push everyone to just follow the process and not do anything more. I've seen my colleagues slowly shift into this mode, delivering what is outlined, nothing more, not questioning the intent behind the work (or at least, doing it much less than before, because the system does not incentivise that).
I would summarize Americans (and perhaps most English speaking countries) as perceiving this mindset to be callous, ineffective, and a dereliction of autonomy.
But I'm interested in how Germans perceive Americans in reverse? If shop staff went out of their way to help them find a product, shoot the breeze, or recommend a lunch spot, would Germans tend to see this as being overzealous? Would it cause embarrassment, or be a pleasant surprise? Just curious.
I tend to view shop staff having a random talk with someone while I’m waiting to purchase or ask something as a dereliction of duty. If you want to catch up with a friend you can do it on your own time.
Every country is different and you need to learn slightly different ways of dealing with them in each. On a bad day it can be pretty exhausting.
It turns out, people everywhere want the same things, in the end. They just go about them differently.
In Germany, it often helps frame it as both of you trying to work with the rules together; as a framework to build within and on, rather than a cage to hold you in.
Doesn't always work. Nothing works all the time, (especially if the other person is having a bad day themselves and just wants it to be over). But if it helps even once eh?
The difference in healthcare between private and public insurance is, as far as i know, because if a doctor sends you for some test or something that your insurance feels was unnecessary then the doctor has to pay for it with the public flavour. At least, that’s what I heard but could be wrong.
I don't know how much of that 6 hours build is tangled up in github workflows, but if it's a single contiguous block, you probably could make it near zero by making the self-hosted runner do only the preparation and only the final upload process (workflow_dispatch when the build is complete).
Most of it is just time waiting either while the source assets are downloaded (I clean slate it, that's the point of CI after all), the build itself runs, or the artifact is uploading to it's storage home. I'm sure it could be re-architected to use less actions minutes but if I'm going to redo it I will probably just move away from actions altogether because it's only loosely linked to Github anyway (runs on a schedule) and that way I am insulated from any future changes they come up with. The hardest part will likely be figuring out the Slack bot posting, I do use the marketplace action for that, but that's probably low lift. With LLM assisted coding I'm leaning more and more to little in house apps for stuff like this, it keeps you from dealing with lock in and other extractive gotchas.
per minute billing is hard to wrap around the head
On my larger organization, we have on average 20 to 30 *active* runners during business hours. Assuming 5 on the off-hours, my napkin math says it comes down to about 10 fully-utilized-runners per month, so about 864$/mo. For the size of my organization that is honestly totally acceptable.
This is assuming 0.002$ per minute of job being actively executed. If it turns out to be 0.002$ per minute of *runner being registered* on the control plane, it would increase quite a bit. We are still using the old HorizontalRunnerAutoscaler with actions-runner-controller, with quite a pool of prewarmed runners idling to pick up a job. It would be a strong reason to use the new RunnerScaleSet (to take advantage of the reactive webhook-based scaling) and keep a very lean pool of prewarmed runners.
We have the same question, our runners are registers 24x7 but we probably only use a few hours a week.
I get the logic of it, they have to have some sort of task running on their side when the runner is working. If it's only build time, then we don't care.
If you ask american/european/english-speaking developers about coding, it will mostly be about/in the context of corporate environments rather than open source too! The majority do not actively or primarily contribute to open source projects, but instead corporate environments as well.
In an alternative timeline where the lingua franca isn't english, I can still see open source culture exist; I don't think the desire to publish and cooperate in public is an inherently "western" culture. It will also run into the same conflict of interest between Open-Source and Corporate: one prefers transparency and full-disclosure, the other prefers control in the interest of minimizing risk.