Do you pronounce "tortoise" like "bourgeoise" because you don't want to sound inferior?
I jest, but it's like your argument is making my case for me. Replace "snob" with "pedant" to see what I mean.
2,562 karma · joined March 3, 2008
Do you pronounce "tortoise" like "bourgeoise" because you don't want to sound inferior?
I jest, but it's like your argument is making my case for me. Replace "snob" with "pedant" to see what I mean.
"Process-eez" is the same word as "processes" with a pronunciation based on a misunderstanding (presumably) of the etymological "rules".
Words with Greek roots that end in -is or -es generally use the -eez suffix. e.g. analysis -> analyses; thesis -> theses
In the case of Latin, it's -ix or -ex. e.g. index - indices, appendix - appendices.
There are of course exceptions and outliers (suffix -> suffixes; octopus -> octopodes!?), but words like "process" and "bias" do not fall into the categories mentioned, so there's no reason to use the non-standard "processeez" and "biaseez". Unless - IMO - you want to sound like a snob... Think about it - how does one pronounce words like "successes" or "princesses"?
One could argue that language evolves - this is true, but in general language evolves to have simpler rules with fewer exceptions rather than the other way around.
Stop, let's all try to stop the madnesseez.
Here's his YT channel for anyone interested: https://www.youtube.com/@DavesGarage
Well, after a few decades writing software, I've come to the conclusion that yes, yes it is. But just because it can be hard to write a good comment it doesn't mean you need to agonise over it.
Here are a few "simple" examples:
// Once we receive the cancellation ack, we should automatically send the updated flow
if (releasedFlow.Status == ReleasedFlowStatus.IndicativeCancelled)
{
await _mediator.Send(new SendFlowCommand ...
It should be pretty clear from the context that that's what is happening and it doesn't explain why. This is because it would take multiple paragraphs to explain. Could I just post a link to the documentation about this business rule? Yes, but the location of the said documentation changes so often it can render the comment useless. Could I change it to say something like "Please refer to the documentation"? Sure, but then why don't I put that comment behind every piece of business logic? No, the simple purpose of this comment is just that - a comment on what the business rule was at the time of writing, especially with respect to the other possibilities. You can spend ages overthinking this but there's no point. Just read, understand and move on.What about this:
if (foo)
{
DoFoo();
}
else if (bar)
{
DoBar();
}
else
{
// Intentionally empty
}
Dead code with a comment that explains nothing. Is this code better with or without the dead code and comment? I'd argue that the code is better with it. In fact, this is a well-known technique: https://en.wikipedia.org/wiki/Intentionally_blank_pageYes, you can argue that the coder should explain why it's blank. But this depends on the context, and who the intended audience is. Again, no need to overthink it. Read it, modify it if you really think it's necessary (keeping in mind that the alternative is often no comment or empty else statement), and move on with your life.
Most of the time I spend with C++ code revolves around figuring out compile/link errors. Heaven forbid you need to deal with non-portable `make` files that for some reason work on the old box, but not yours... Oh, and I hope you have a ton of spare space because of some reason building a 500k exe takes 4GB.
Keep in mind, this advice only applies to inherited C++ code bases. If you've written your own or are working on an actively maintained project these are non-issues. Sort-of.
When I ask Gemini, it basically tells me "it depends" with a few paragraphs of things I generally don't care about and then suggests I ask for a ballpark estimate (1k - 3k tokens).
That's exactly why I said "many people could", not "everyone will".
These days I only eat after 5pm. My body is so used to it that I don't really get hungry during the day. Even if I go to gym in the morning. Do I notice a difference if I change my eating schedule or diet? Absolutely. If I eat during the day, I tend to want to eat more during the day. If I eat a lot of carbs and junk food, I tend to want to eat more. Also I feel like shit and my skin looks horrible. I think somewhere in all this mess there are mental health concerns as well, but I can't really quantify them in a meaningful way.
I'm sure many other senior programmers have similar thoughts.
I have several different amps, a tube pre-amp, several DACs and a Qudelix 5k DAC. I regularly switch between an HD600, HD650, HD560s, HE4xx and Audeze Maxwells. I can maybe count on one hand when I thought one combination sounded "better" than another, although I'm sure I could bump up this number if I tried. The problem is 90% of the time it just doesn't matter.
There's loads of resources on the net that talk about this, e.g.
https://www.youtube.com/watch?v=K8zAko5G6eg
Most of the time the differences are not that important, unless, as the adage goes, you're using the music to listen to your equipment rather than using the equipment to listen to your music. Which... 90% of users don't do.
Some people will swear XYZ amp makes their audio sound better, but that's more a function of taste, the DAC, and/or distortion handling mechanisms inside the amp, and that's itself is an incredibly topic which again 90% of users can ignore.
"OK don't worry about oval ones. Just consider the round ones."
All this aside, I don't think you understand what is meant by Apartheid. This is coming from a South African who grew up during that era.
I'm reminded of an anecdote (probably false) of when someone was asked in an interview why all manhole covers are round. He replied that not all manhole covers are round. They countered "Well, just consider the round ones".
Is this a serious comment, or satire? I honestly can't tell. I mean... we're talking about a country whose official social media accounts tries to pass off pics of the Lebanese war as the current situation in Gaza; who posts doctored images to try to disguise executions; who posts edited footage of their military commanders pointing at calendars saying they are a roster of terrorist names. I could go on and on, but that last bit is still too surreal.
What (true) version of reality are you talking about here? And besides that, you do realise that one of the things this article is pointing out is how certain groups work together to punish people who post things they don't like - even if it's just an opinion?
Nevermind, your post simply has to be satire...
- 1 assertion per test
- Exceptions instead of return codes
- CQRS
etc
All of these are good guidelines in some contexts. I cannot fathom why anyone would think they apply to every situation...
"I'm giving up on X/Y/Z because I've found a case where it didn't work well for me".
Isn't that how pretty much everything in the world works? There's no reason to be dogmatic about things like this.
AKA Command-query Separation (CQS)
https://en.wikipedia.org/wiki/Command%E2%80%93query_separati...
I use this often, but there is one typical scenario where I break this rule - creation commands. Often someone calling a command that creates an entity needs the ID of whatever was created. Yes, you can use UUIDs and pass this to the creation function (or use more complex methods), but I haven't really come across scenarios where this adds anything meaningful, not to mention that it's not always possible. So I generally break CQS for creation commands, i.e. they change state and return a value.
EDIT: I just noticed the Wikipedia article cites other examples, e.g. The `pop()` method on a Stack.
TrueNAS works fine for my use cases, and I suspect it's the same for most users.
WHERE Column1 <> Column2
The suggested improvement: WHERE Column1 <> Column2
When I pointed out that it just gave me exactly the same code, it apologised and suggested this improvement instead: WHERE Column1 > Column2
I'm trying to understand how this helps me become more productive...OK, I already know where this is going so I'll just skim the rest.
Hmmm... as I suspected, I can't see how this article is any different to:
"AI Does Not Help [xyz]" with cherry-picked examples to prove a point.
In fact, I'm pretty sure I've been reading similar articles several times a month since ChatGPT was released.
Here is my "proposition to be debated":
"Articles about how AI does not help [xyz] do not in fact help anyone"
For example, I asked 3.5 to find a bug in a lengthy piece of Javascript. It said it's hard to give a correct answer because it doesn't know what the HTML or CSS looks like.
GPT4 spotted the bug almost immediately (it didn't manage to fix it though).
https://en.wikipedia.org/wiki/Chinese_room
This is also similar to the Duck Test:
https://en.wikipedia.org/wiki/Duck_test
Depending on the context, there are generally two takes: "It is (or is not) a duck", and "It doesn't (or does) matter whether or not it's a duck". These aren't mutually exclusive.
Would it be noteworthy if it this game (whether or not it existed before) were designed and implemented by someone who has very limited experience with software development in a few hours? Well, the fact that ChatGPT did this means the former is now a very real possibility.
That you can go from conceptual inception of a framework to a fairly complete product in a few hours with very little experience is a big deal.