Censorship sucks and I canβt believe we let an entire country get away with it and still did business with them the whole time.
It is not clear to me that the country would be less censored now and the people there better off if we had refused to do business with them.
(Just to be clear, I am not saying that we handled China as well as we could have over the last few decades, but hindsight is 20-20.)
Not true at all. They started as a game bundler, and branched out into publishing games..
Also, all of their bundles and sales continue to feature donations to charity.
Is it just me, or this article basically just an ad, and not a particularly well written one?
You are probably thinking about Humble Games, which is a sibling company. Humble Bundle has been a multi pack sale company for its entire existence.
Ah. In that case, I look forward to there being a new keyword in C++26 or later that you add to enforce that the enumeration really only does take one of the enumerated values, rather than just being a strongly typed number, since that seems to be the way that the language likes to do things...
Could someone explain to me what the value is in making it really easy to initialize an enum class with a value that is not one of the enumerated values?
Genuine question: does anyone actually use Vala for anything? I think that the idea of a language whose OOP system is native GObjects is a nifty one, but I have seen no evidence that it has caught on in any significant way.
Sure, but if you are not regularly expressing code that has the potential of summoning elder gods that will swallow your soul into a dimension of ceaseless screaming then are you really living?
I don't always use regular expressions, but when I do, I use it to parse XML,
I find the authorβs writing style immature, sensationalist, and tiresome, but they raise a number of what appear to be solid points, some of which are highlighted above.
I tried reading the article and gave up because life is too short for me to read a tiresome article making points that aren't even particularly that new.
Something that definitely separates me from some of my less experienced coworkers is that, when I sit down and start to implement a plan I came up with in my head, if it turns out that things start exploding in complexity then I reevaluate my plan and see if I can find a simpler approach. By contrast, my less experienced coworkers buckle down and do whatever it takes to follow through on their plan, as if it has now become a test of their programming skills. This makes life not only more difficult for them but also for everyone who has to read their code later because their code is so hard to follow.
I try to push back against this when I can, but I do not have the time and energy to be constantly fighting against this tendency so I have to pick my battles. Part of the problem is that often when the code comes to me in a merge request it is essentially too late because it would have to be essentially completely rewritten with a different design in order to make it simpler. Worse, the "less experienced" coworker is often someone who is both about a decade older than me and has also been on the project longer than me, so even though I technically at this point have seniority over them in the hierarchy I find it really awkward to actually exercise this power. In practice what has happened is that they have been confined to working on a corner of the project where they can still do a lot of good without others having to understand the code that they produce. It helps that, as critical as I am being of this coworker, they are a huge believer in testing, so I am actually very confident that the code they are producing has the correct behavior, even when I cannot follow the details of how it works that well.
I did it again. π«€