Form out of band relationships with coworkers you trust to get a base going then send an email to everyone from your department from an anonymous email address to solicit feedback and organize a vote.

Unions are legal in all occupations. There may be restrictions on some form of collective action (i.e. the government can force strikers back to work) but organizing is never illegal.

As someone who writes high throughput PHP code I can confirm that it’s much more about technique than language capabilities (though in an embedded setting things with dynamic GCs are simply unusable unless static memory management can be enabled with a compiler switch).

For most projects you’d be much more rewarded for focusing on tools/framework/libraries available for the different languages (since that’s where most initial effort will go) and then build up any missing functionality as needed ontop of that base.

Most languages can do pretty much anything these days. The technical advantages are much smaller than the impact the right approach will have… it’s one reason that I hold “maintainability” as the most important attribute of a project.

GitExtensions

I use an excellent GUI that opens a terminal to run the commands you execute in it so that you can review the precise command in case you need to modify it.

That’s fair enough.

C is an extremely expressive language. There’s a reason it won’t die and, while we all love to shit on it for the memes, you can write perfectly safe software in it.

They may be obvious to the reader but they may be impossible to see if tabs and spaces are mixed together.

Closing tokens are always clearer.

Sorry, what’s confusing the fact that "Hi my name is {$this->name}" works and "Hi my name is {self::name}" is unintelligible gibberish! /s

Yes it would - look at optional braces for short if expressions in C family languages and why it’s so discouraged in large projects. Terminating characters are absolutely worth the cost of an extra LoC

For those highly complex situations is Lua still viewed as the ideal solution? Lua is sort of legendary for game configuration and seems to strike a good expressiveness/accessibility balance for modders and the casually technical.

So Poe’s Law and all that… I really hope you’re being sarcastic because having non-technical people hand edit JSON is a nightmare. It’s also quite annoying to read without a lot of extra whitespace which most editors that’d help less technical folks omit… and comments to help highlight what different things mean are hacky, hard to read, and actually read as data.

Because people over use it. YAML is pretty good for short config files that need to be human readable but it falls apart with complex multi line strings and escaping.

I think there are much better clearly delimited for machine reading purposes formats out there that you should prefer if you’re writing a really heavy config file and, tbh, I think for everything else .ini is probably “good enough”.

I have been hoping someone would eventually write a solid utility to use old tablets as touch screen displays for other machines but I think the apple ecosystem has prevented any good solutions from being banged out.

The real estate requirements are real and if you don’t have the space it simply won’t work - but they are absolutely fine for text legibility. An important thing to remember is that, because you’re viewing the reflection of the image instead of having a backlit screen, (outside of matte e-ink options) I’ve found it a lot less fatiguing on my vision than a traditional monitor. So, while I still prefer dark mode out of habit, even bright sections of the image for extended periods of time doesn’t make my eyes sore in the same way. Lastly, as someone who wanders and dances while they work - it’s much easier to keep focus on the screen as I migrate.

I’m sure it’s not for everyone but it’s an extremely comfortable way for me to code.

Honestly… just get a fucking projector.

Can you clarify if you want to track changes across all the files or just the ones that will always be available? And will you be automatically committing the state of the files at some regular interval or would you only be manually checking in changes?

If this is something likely to change I’d space it out - but mid-line diffs are usually pretty readable in most clients.

As always, expression should cater to readability and shouldn’t be limited by syntax rules.

I think that makes it harder to work in a language… you certainly can set up an editor autoreplacement but once a decade or so someone’s going to need to hotfix something in a strange environment and trying to force things into nano using alt codes is a real pain.

That said the intentionally hard to type symbols with ascii replacements actually make me less sad than things like this syntax that requires a pipe character… I don’t know if you’re a polyglot (or ever typed on a keyboard in quebec) but most of these languages’ symbol choices are convenient on an en-US keyboard with little consideration for international keyboard layouts and there are a lot of hard to type symbols on the spanish keyboard that are very common in programming languages.

It’s unnecessary, though - the keywords alone are sufficient. I dislike “clutter” syntax.