Common criticisms here would be that these endeavors stifle creativity and show the adoption of modern solutions. That said, I find conducting “code archeology” to figure out the idiomatic way of doing something in an old project very rewarding. Because computer programs exist in people’s mind’s, doing that with the support of original developers or subject matter experts is some of the most effective knowledge transfer I’ve ever witnessed.

My take on a summary: like C/C++, Rust can be relevant in a variety of use-cases and one could conceivably build a long-term career on it, while adjusting to market/technology interests.

Seems like a reasonable prediction?

That totally threw me off. “Literally unplayable,” as they say.

I adore Rider for work, but have found myself preferring VS Code for personal contributions, myself because it’s lighter.

I’m curious about your opinion though: why would you only use them in a corporate environment, assuming the scope of projects is equivalent?

That makes sense. I’m also involved in localization efforts. In niche cases, it’s paid off to work with the clients directly on that. You get you a good balance between correctness and day-to-day usefulness.

Since ladder is mostly diagram-based it almost doesn’t need to be localized and isn’t jarring when you use non-English variable and function names with English keywords.

Apart from being strictly left-to-right.

If he worked in Germany, did he use English or German mnemonics?

If he worked in Germany, did he use English or German mnemonics?

Industrial controls equipment made by German companies can be programmed in English or German. You can also switch languages (German/English) at any time and the IDE switches over all the keywords.

Semicolon!

Shared with my favorite blind iOS dev. Should be a good laugh!

Hey, let hiring managers enjoy their riddles!

I also can’t get the printer to work.

OK, tiling window managers are neat and so are TUIs, but web pages are also supposed to work with keyboard only. On Windows, F6 will jump between different panels in an application - give that a try.

The key you’re talking about is the menu key, by the way.

Using a modern OS and the modern web with the keyboard only is essentially a solved problem, not only motivated by efficiency, but also to allow access to people with motor disabilities.

Coming at this from an accessibility… is there any reason the tab, arrow, scape, escape and enter keys would not suffice?

Is it about efficiency? Are Linux GUI apps not expected to be keyboard-only accessible by default?

Sounds like you may be interested in a certain manifesto.

Don’t mind me, I’m just picking the very best grains of sand to make my own silicon, like a real programmer (xkcd).

I think .NET and EF should handle navigation property nullabiloty better out of the box, especially when you explicitly set the foreign key to long?.

That said, while I understand these relationships in my own projects, adding clear annotations is very helpful for colleagues who may have to provide support in the future. That could even be me!

So there’s no perfect solution in this stack, but anything that makes a developer’s intent clearer helps. Privilege of least surprise, right?

Well, you still have to ! because it may, based on the annotation, be null.

Very handy, regardless. Microsoft’s docs on these attributes are very interesting, particularly the postconditionals.

An open source-ish corporate product is valuable in so much as it’s a vehicle for a paid service, right?