1,183 karma · joined December 19, 2016
Code that solves problems and makes you money is by definition an asset. Whether or not the code in question does those things remains to be seen, but code is not strictly a liability or else no one would write it.
If China invaded overnight and absconded with Trump, I’d say I disapproved even though I don’t like him.
> I always grew up with the assumption that everything on the internet is most likely fake.
How you interact with the internet is not really relevant to the discussion. The average person does not interact with the internet in the same way that people on this forum do, so that should not be the yardstick by which we judge this.
There’s a difference between writing anonymously and assuming a false identity.
Jesus, we’re fucked aren’t we?
Your chemicals in river analogy only works if there were also a giant company straight out of “The Lorax” siphoning off all of the water in the river.. and further, the chemicals would have to be harmless to humans but would cause the company’s machines to break down so they couldn’t make any more thneeds.
The risk being posed here is that AI may not land as an incremental improvement that still requires the user to maintain some understanding of the underlying skill.
We aren’t quite there yet with the current LLMs. You still need to have a base level of knowledge to use them effectively. But if they were just a little bit better, hallucinated just a little bit less, the value of actually knowing things goes way down.
What would the incentive be to learn the underlying skill or area if the LLM can handle things just fine on its own? Why not just let the LLM figure it out and do it? And at that point, it ceases to be a tool and starts to be something you are completely dependent on. That is a risk.
The total amount of code I had written in my first two years of university was not very much; by the time I had taken some of the advanced courses I had written a lot more code and had thus become a better programmer (still not a good one, but better!). I had written probably 10x more code by the end of year 4 than the end of year 2 thanks to practicum courses, etc.
People do work noticeably shorter days, a handful of people come in for less than 30 minutes (huge waste of resources and time), and yeah, there is a morale problem.
One thing I have noticed is that the more co-located a team is, the more people behave like pre-Covid — in at 9:30, out at 5. Satellite workers who are coming in are the most unhappy (for obvious reasons) and are the most likely to badge in, grab a coffee and check their emails, and then leave and finish the day at home.
1. Track badging 2. Enforce RTO via chain-of-command. SVPs, VPs, and directors have aggregate RTO compliance metrics. SVPs crack the whip on VPs to get their numbers up, VPs crack the whip on their directors, and directors crack the whip on their reports, and so on, all the way down.
The actual implementation of the policy was a mess and there was poor messaging especially at the beginning. I'm pretty sure it still doesn't take PTO or illnesses into account — if there's an issue with that, you're supposed to work it out with your manager — and from what I heard they simply handled the holidays by excluding the work weeks before and after Christmas from the metrics. But, ultimately, the chain of command approach appears to have worked very well in terms of actually getting people to come in.
edit: Just noticed from your profile that you also work at Amazon, so I guess there's nothing new in my comment for you :)