Hahahahahahahahahahaha
(Pause for breath)
Hahahahahahahahahahaha
Was that tone really necessary? I would have liked your comment more without this part.
English source code is a universal language.
I've never seen a need for localization beyond domain terminology. And I think it would be a huge detrimental.
To implement it would be unnecessary significant complexity. Effort better spent elsewhere. And for programmers it'd be confusing. Think code snippets, mixing content, and the need for reserved word expansion or exclusive parsing scopes that would be even more complex and confusing.
error: dict not found. Were you looking for dick?
Sounds like you had the wrong indent after they shifted you around.
This is not a supply chain attack, it is sudden extreme enshitification. according to the article, the attacker also bought the GitHub repo
I don't see how buying the GitHub repo as well makes it not a supply chain attack but enshitification.
They bought into the supply chain. It's a supply chain attack.
The Nobara Project, to put it simply, is a modified version of Fedora Linux with user-friendly fixes added to it. Fedora is a very good workstation OS, however, anything involving any kind of 3rd party or proprietary packages is usually absent from a fresh install. A typical point and click user can often struggle with how to get a lot of things working beyond the basic browser and office documents that come with the OS without having to take extra time to search documentation. Some of the important things that are missing from Fedora, especially with regards to gaming include WINE dependencies, obs-studio, 3rd party codec packages such as those for gstreamer, 3rd party drivers such as NVIDIA drivers, and even small package fixes here and there.
I wouldn’t do that, too much tunnel vision and biases.
Absolutely not. Self-reviews are very productive. I can confirm this from my own work and my colleagues, who also find it so.
You're of course free to vary the degree and depth of self-review, but tunnel vision and bias is definitely not overbearing and diminishing in those situations for us.
Someone else will of course see more, what you may not see due to tunnel vision. But that's besides the point.
I think it's convoluted way to describe it. Very technically-practical. I agree it's probably because of historical context.
The argument I read out of it is that using goto breaks you being able to read and follow the code logic/run-logic. Which I agree with.
Functions are similar jumps, but with the inclusion of a call stack, you can traverse and follow them.
I think we could add a goto stack / include goto jumps in the call stack though? It's not named though, so the stack is an index you only understand when you look at the code lines and match goto targets.
I disagree with unit tests replacing readability. Being able to read and follow code is central to maintainability, to readability and debug-ability. Those are still central to development and maintenance even if you make use of unit tests.
The title could have been "Why knowledge of programming alone is not enough", without a question mark. I would have preferred that.
If only this post title had received descriptive text too
Kissaki
joined 1 year ago
The dash emoji. Always looks like a fart.