>Quite often a senior leadership issue because backing stuff up results in $$$ spent, which makes shareholders unhappy.
This is true. The latter half of your comment is not. At best they have a duty to shareholders. But your assertion would mean every time a company posted a loss and the price went down the execs would be in legal trouble, which is nonsense.
Shareholder nuisance lawsuits can happen basically any time the stock goes down... or doesn't go up enough, and often companies will settle instead of the expensive fighting...
There are grounds legally if shareholders can prove that the "long-term risk reduction" argument is a lie, they can sue under the Duty of Loyalty. In reality, yes, this amounts nuisance lawsuits, large settlements and disruption at the board level. In practice, this and the executive pay structures almost always incentivizes short-term decisions and these risks become problems “for the next person.”
This is Matt Levine's theory of "everything is securities fraud".
Something bad happens, stock goes down, angry shareholders sue because they should have been told the bad thing would happen and the stock would go down.
And building the correct structure for your problem/program is still a huge part of the job. If you completely delegate structure, you still get a clusterfuck.
I have found working with LLM's is best when I provide as much structure and constraints as possible, and reduce the degrees of freedom that the LLM can exercise, so that it is forced to fit its logic inside the structural boxes I have laid out.
If you just delegate everything to the LLM to get an absolute morass.
The guy in charge of all of this has eaten road kill and rotting carcasses and he appears to be completely fine. I'm sure there will not be any issues.
Also a staff engineer. This is pretty much exactly what I do.
Often it is a result of suggesting an improvement to some PR for a program or system that someone is doing some work on, and discovering that for whatever reason it doesn't quite work. This tends to lead to a deep dive of really analyzing and understanding the problem and how the piece of the system fits into the overall picture. This analysis often leads to a more structured approach to a problem, placing it in the context of wider industry or CS theory, thus enabling us to leverage prior art and other people who have grappled with similar problems.
I've spend a total of about 2 months in the Carribean. One of those being an entire month straight.
It's the convenience really, and the fact that nobody is in a hurry. Island time is real. You cannot be demanding. You can't really be upset at service. Most people are there to chill out, even if they are doing a job. Life is just slower.
This is good, IMO. But if you are a hedonically adapted/burned out western metropolis dweller, this culture shock could be distressing.
One trend that's bigger than tech is that educated professional class has massively consolidated into the liberal column in the wake of Trump, it used to be more like 66/33 lean liberal.
So that's going to impact any professional class community, whether it's tech or not.
I was talking about the broader professional population, there's polling on this and they've (we've) really consolidated left as the right wing has become more and more about culture war.
This is true. The latter half of your comment is not. At best they have a duty to shareholders. But your assertion would mean every time a company posted a loss and the price went down the execs would be in legal trouble, which is nonsense.
reply