I hope they don’t cremate him, I’d really like to piss on his grave.

The moon phase cycle is 29.5 days. The reported bug cycle is 49 days. Yet somehow, “Not strictly the cycle of the moon but close”.

With that sort of logical analysis ability, no wonder this guy struggles with stupid bugs.

I used to enjoy programming as a hobby in my spare time, but in two years I’ve opened the IDE on my personal machine no more than twice.

This is why I have never taken on programming as a profession. I earn more than I would ever make as a developer (even a very senior developer) leveraging my (average) programming skills to produce a personal suite of software tools and scripts that means I can do my chosen profession better, faster and with less effort than any of my colleagues or competitors. I have also developed small apps on a private/ personal basis that I have then sold to my employer for wider use in the company.

And I still enjoy programming as a hobby as much as I ever have. Don’t underestimate how much being able to program at even an average level can boost a career in another field.

Although rug-pulls like this are dubious to say the least, neither should FOSS contributors be hauled over the coals simply because, to justify continuing to commit more and more time to a project. they need to generate some kind of revenue. If more FOSS advocates donated reasonable amounts of money to the projects they use, this kind of bollocks would be much less frequent, and the long term stability of projects would increase dramatically. Sadly, way to many people donate nothing. And way too many companies, as well.

Of course, it is not always possible to avoid over-committing as sometimes the business calls for it.

Well that sounds like lazy acceptance of a bad situation for your team.

No mention of fighting for better terms for the team. If the business calls for over-committing you team, you or someone else in management have failed. Such a commitment may be indeed be unavoidable in that situation, but your job as a manager is to fight for your team to be additionally compensated for such an over-commitment.

even if it’s a blatant copy paste they can’t do anything.

They can sack you.

If your CV contains absurd claims about having learned all programming languages, I’d be surprised if you even got through to an interview.

seeming to take 100 lines of course to accomplish something I can do in 10 in other languages. But, again, that’s subjective

That's clearly vast exaggeration, and devalues the rest of your post.

12:15, which is great as we break for lunch at 12:30. It prevents the time-wasters blathering on endlessly, as they are focused on lunchtime. A maximum of 15 minutes of wasted time.

You should also try and get a letter from the company explaining that it wasn’t for performance reasons.

Excellent advice.

What did they think Unity’s investors plans were, to endlessly subsidise a constantly loss-making platform just for the fun of it?

Unity have lost huge amounts of money, in fact never made a profit for a single quarter, while establishing more and more market share, and their customers never asked themselves how or why?

If your vendor is constantly making huge losses while establishing more and more market share, your guy in charge of the financial decisions should be asking themselves what the investors long term plans are. That’s not rocket science.

Not pro-corporate in any way, I don’t see how you could possibly read that into what I posted. But if you choose to sup with the devil, best use a long spoon.

Unity have already established market dominance, if not effective monopoly, as the mobile gaming development platform. They are in a position of power, they have invested large sums of money to get there, and there is really very little game developers with a product 1 or 2 years in development can do about it.

While this is going to be difficult for Indy developers, they really only have themselves to blame. Part of the task when you are making a major software platform decision as a company is to research your vendor’s financial strategy - that’s basic due diligence. Unity has been loss making for years, which either means they are not financially viable (and not a safe bet), or they are engaging in a strategy of establishing an effective monopoly position to later squeeze dependant customers until the pips squeak.

This is likely just the start, whether it’s through runtime charges, Unity control of in-game advertising, or huge hikes in seat license fees. Possibly all three.

LLMs produce code that is functionally error prone while looking reasonable (in the same way that it produces answers that are grammatically correct, correctly spelled, but factually incorrect).

As we all know, fixing bugs in someone else’s code is generally more difficult than writing the code correctly in the 1st place , and that’s going to apply to a LLMs code output just as much as a humans, if not more.

Is having a consistent domain language across the board important? Yes, obviously it’s a huge benefit in communication and in maintainability.

Is not following that convention, in and of itself, a huge problem? Probably not, so long as the primary parties understand the differences between separate aspects (such as the database using a different word order), although the documentation needs to explain this.

Is not being able to get an agreement on a consistent domain language that everyone will follow a problem for development? Yes. Huge. Crippling. It reeks of poor, indecisive management at the top project level, and petty interdepartmental squabbling all the way down. It’s a huge red flag as to a company’s ability to deliver. It’s not that difficult a thing to get agreement on or to enforce, as it’s entirely visible. If a project can’t do that, it’s not going to be able to do the things that are actually difficult.

Just because it tasted like bleach doesn’t mean it’s going to clean up like bleach.

But if they don’t know they have to knock “shave and a haircut” first, your job gets a lot easier and you’re dealing with a lot fewer nuisance password promptings.

Very good explanation. And the benefits are even greater: because there is absolutely no response until the entire secret knock is correctly used, the random guy trying to get in doesn’t even know if there’s anyone at that address. (In fact, set up correctly, they won’t even know if there’s really a door there or not)

If you want to go down that path, a password is only security by obscurity.

Port knocking is an extra layer of security, and one that can stop attackers from ever knowing your private server even exists. A random scanner won’t even see any open ports.

Always bear in mind that any random guy advising people not to use port knocking may be doing it with malicious intent. I’m sure there’s someone out there advising that random passwords are a waste of time, and everyone should just use monkey123.