![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/2QNz7bkA1V.png)
Probably used ChatGPT….
Probably used ChatGPT….
Therefore this it is the company’s responsibility as a whole.
The governance of the company as a whole is the CEO’s responsibility. Thus a company-wide failure is 100% the CEO’s fault.
If the CEO does not resign over this, the governance of the company will not change significantly, and it will happen again.
“the sudden announcement of Boeing CEO Dave Calhoun’s resignation by the end of 2024 was interpreted as a response to the company’s persistent safety issues.”
I hope Boeing has serious bonus claw-backs in their contracts, because this idiot’s “cost-savings” have actually cost Boeing a fortune, and destroyed their reputation. The entire board should go.
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.
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.
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.
Some context:
http://www.antiscald.com/index.php?route=information/information&information_id=15
At 116F you would require firm, continuous contact for more than 20 minutes to produce a 2nd degree burn, and over 45 minutes to produce a 3rd degree burn.
You should also try and get a letter from the company explaining that it wasn’t for performance reasons.
Excellent advice.
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.
Both measures were according to the mothers’ self-reports.
In other words, this study has no real scientific value.
But there are many more problems with this “study” than just that.
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.
Not everyone be any means, but if you admire narcissistic extroverts then sure, you’re always going to be disappointed.
Social media influencers are money-grubbing low-lives who will promote anything for some cash? Well colour me surprised.
Just FYI, there are some really wild drugs available in the Peruvian jungle.
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.
An article on Ars Technica, complaining about advertising.
What hypocrite posted this?