I had my "wow" moment recently and saw an AI agent do something do over a weekend something that I spent years developing a relatively niche skill might have needed a month to complete.
I think the message the team lead takes away right now is "oh, this can be done a lot faster, let's do more!" This is exciting for a bit, but I think it comes at the cost of learning -- and being able to communicate --architectural lessons that would stage off systemic issues later.
I bet a huge amount of that is on your head, or if it is factual, a function of a toxic work culture where people are primarily incentivized to "outperform one another" rather than arrive at collaborative solutions.
The wealthy/owner class once again consume all of us -- here through AI -- because we cannot agree to work together.
It's a little different because cloud and blogs didn't actively get in the way of your home compute. To wit, the various cost spikes for hardware.
People -- WANT -- this technology on their home devices and (apparently?) the providers of this tech don't seem to be running a profit so they probably don't want the maintenance tail on their side either.
I think it's a bit different. Inevitable that this becomes a household-run thing? Not likely.
As a semi-savvy programmer, but with little experience in web-dev, I'm actually a bit ignorant of what a site can measure -- client side -- versus collect server side.
Presumably it's a simple matter to send something back to a server, but I've really never thought about the mechanisms involved.
Is that the hang-up? Like are people so unimaginative to see that none of this was here five years ago and now this machine is -- if still only in part -- assembling itself?
And the details involved in closing some of the rest of that loop do not seem THAT complicated.
I think think this must be why so many advanced level texts are couches in "introduction to..." language. Maybe it's a concession to not being able to cover every topic!
Because my own introduction was through combinatorial game theory, I always get excited to see some hackenbush diagrams and rarely do when the subject is mentioned.
Perk is... quite a thing. I think if you like programming because you like believing you have secret knowledge... go for it. Perk will scratch that itch. But I do not believe it beings you closer to the pantheon of God's. Ai n't gonna stop anyone from dancing with the Satyrs though, if that's your jam.
I have to agree -- I generally avoided Twitter/X over the past decade. I started poking around in there once in a while the last few months and everything time I'm left exasperated. 'I can't believe people believe any of this!!"
It's not a matter of a "deal" to be made or agreed to, it's a matter of paying a fair share of the cost to organize a society. When Capital gets to reap dual benefits of revenue from business prospects and lobbying government directly to set the tax rules, then it can't ALSO offload outlaying to the public good that it DEPENDS on to make a profit.
Avoiding tax through various loopholes that Capital gets a seat at the table to help craft, while benefitting from externalizing the costs to taxing labor is just corruption.
Well... is it really? Just because someone can pump out some kind of product that someone will buy doesn't mean it's actually worth any externalized cost whatsoever.
It's one thing of we're talking food production and housing. Completely different if we're talking McDonald's happy meal toys.
Like, does the same argument apply to noise pollution? Are we alright installing a factory next to the symphony hall so long as the factory "owns" their land?
I think as our technology and understanding of the world grows we ought to change with it.
It would seem likely they were consumed by the proximate concerns of evading notice and making it to the plane and had no idea or thought about the dangers of being at such high altitudes.
There are enormous pressures on a new parent -- stress about getting back to a normal work routine and lack of sleep compound into a unique kind of stress and things start to slip.
For me: I decided I could just slow down a bit. Standing out isn't worth the stress. I don't want to slack, but I don't feel compelled to cram productivity into every moment.
We were 38 with our first. I strongly agree that is too late to have them, especially given the likelihood of birth defects. Thankfully, we avoided issues there.
A few years in and I feel "back on my feet", but it was harder for being older.
At face value, I think I agree -- especially the format of the website being in a sort of hand-designed style.
"Assembly Theory" is a sort of applying (kolmogorov-esque) complexity theory to physics and other natural sciences. I don't know much else beyond that it's a "real thing".
So with that extra background, I give it a pass. I think it's an interesting idea at least.
Sort of both. I believe there are massive polarized forces that invest heavily in understanding and gaming the system. Sort of like a big multi-player game of tug of war .
The system must be understandable or people wouldn't incorporate and collaborate on extracting an edge. Slack in the system represents a lower price point, which will be corrected by a corresponding purchase order.
An individual has an effect, but it's miniscule compared to the massive forces in play. Unless you have a TRULY novel analysis of a situation, you are going to have a very low probability, success rate and out competing the market.
My understanding is the notion is about getting an application to "work" without any underlying theory of operation or evaluation of the imported context.
I think the message the team lead takes away right now is "oh, this can be done a lot faster, let's do more!" This is exciting for a bit, but I think it comes at the cost of learning -- and being able to communicate --architectural lessons that would stage off systemic issues later.