Well, yeah, while that is true, my impression is that mathematicians (as a community, even though there were outliers) didn't care - not even the slightest - about the impact of LLMs and generative AI, other type of AI and machine learning until it started impacting them. So I have no sympathy for their community at all. They brought all this AI dystopia on us, so they should have voiced their concerns much louder and much much earlier. They should also have shamed their peers who helped these companies much louder and they should have lobbied their institutions and their governments much earlier and much stronger. They should also have protested the direction these companies took at the exact moment when they started using AI for profit.
You would be surprised to see how much the japanese IT industry is behind the times (a decade at least IMO). There is only a very limited startup culture here (both in size and talentpool and business ideas), there is no real risk taking venture capital market here (maybe Masayoshi Son is the exception here, but again he tends to invest in the US mostly) and most software companies use very very very outdated management practices. On top of that most software development had been/has been outsourced to India, Vietnam, China, etc, so management see no value in software talent... SW engineers' social recognition here are mostly on the level of accountants. Under such circumstances japan will never have a chance to contribute to AI meaningfully (other than niche academic research)
Buying a phone is a non-dispensable part of life today. There are some government services in many countries which are digital only (and phone only in particular), and restaurants, hotels, etc in the service industry which all require you having a phone, otherwise you can't use their services. And this trend is growing. So if you are the type who wants to live in a cave, or hang yourself on a tree rather than accepting that modern societies require a modern phone, thats's your choice. But others rather accept this. We are beyond the point where this trend can be reversed. On the other hand AI is not that integral part of people's lives yet, and it's better to protest now as long as it has an impact
These are the comments of the people who will cry a f@cking river when all the f@cking bubbles burst. You really think that it's "$300 total to serve the same amount of tokens as a 5090 can produce in 1 year running constantly"??? Maybe you forgot to read the news how much fucking money these companies are burning and losing each year. So these kind of comments as "to run local models is not worth it EVER" make me chuckle. Thanks for that!
How wrong the author is about that! IMO As soon as the bubble bursts, which is already evident and imminent, these agents will raise their subscription fees to ridiculous amounts. And when that happens, entire organizations will abandon them and return to good ol' human engineering
Thanks for the link. I see that you get credits and access to embargod releases. So I understand that's not financial stake, but seems enough of an incentive to say positive things about those services, doesn't it? Not that it matters to me, and I might be wrong, but to an outsider it might seem so
I love to write code too. But what usually happens is that I go through running the gauntlet of proving how brilliant code I can write in a job interview, and then later conversely being paid for listening to really dumb conversations of our stakeholders and sitting in project planning, etc meetings just so that finally everybody can harass me to implement something that a million programmer implemented before me a million times, at which point the only metric that matters to either my fellow developers or my managers or the stakeholders is the speed of churning the code out, quality or design be damned. So for this reason in most cases in my work I use LLMs.
How any of that comes down to an investment portfolio manager as writing "world class code" by LLMs is a mistery to me.
Yeah, shallow dismissal of people's effort to try to make a change must be because they are a ‘one trick pony’. Is that all you brought to the conversation?
What I am missing from both the blogpost and the comments is that the most valuable contribution a manager can provide is information and not some elusive, esotheric, corporate-speak mumbo-jumbo. And when I write information I mean information in advance (you can call this call for comments if you wish), not after the fact when decisions have been already made. 99% of managers rather focus on some self-patting feel good mindfulness guru teachings instead, and I wonder why...?
Yeah, this makes sense. What I am missing from both the blogpost and the comments is that the most valuable contribution a manager can provide is information and not some elusive, esotheric, corporate-speak mumbo-jumbo. And when I write information I mean information in advance (you can call this call for comments if you wish), not after the fact when decisions have been already made. 99% of managers rather focus on some self-patting feel good mindfulness guru teachings instead, and I wonder why...?
You can't bring people in the same office from three different timezones. Most probably your setup was the problem, not the productivity of the people working remotely. Remote people working in the same timezone are usually very effective in their job.
While the article does not mention it, chances are that the sarcophagus was found during doing the soilwork for modern construction. In which case the construction company is obliged to report that to the ministry in charge and then the excavation can be done with proper care. If there was not a law for that we wouldn't talk about grave robbing but grave destroying instead.
I like that the author propagates software developer liability. That makes sense. Unless we introduce such system, the incentives are not there to avoid failure
It's good that the author makes the distinction between developers and managers. This distinction is rarely made and most media outlets talk about the wrongdoings of developers, who are almost never the decision makers of failing projects. It's quite the opposite, they are the ones who if brave enough criticize bad management practices and the lack of proper management of the software project.