I don't know what kind of work you do on a daily basis. But, the difference between sending a Slack message and sending a message to kick off an agent to chain a bunch of tasks together is a vastly lower activation barrier. I think many people will jump over that lower barrier out of FOMO, to avoid being outcompeted by those who already jumped.
As an IC though, me sending a slack message is perhaps less impactful than a PL responding to a report :)
Maybe I'm just an idiot but...which one is the lower activation energy one?
If I need something done and I ask one of my team members to do it, I trust them to get it done without supervision. They are good at their jobs and I leave them to it.
Well, at some point it's up to us to say 'no.' Weekends have not always been a widely accepted ritual[1]. They only became one because of collective action.
Dedicating any and all of your free time to work only becomes a norm if we let it.
Well, they did specify your _newly_ freed time. So if you work 8 hours now and AI lets you do that work in 4, then you'll just do double the work in 8 hours, not get more free time.
I don't think there's an obvious point to take collective action.
That's why it doesn't seem worth it if you are not running the model locally. To really get powerful use out of this you need to be running inference constantly.
The pro plan exhausts my tokens two hours into limit reset, and that's with occasional requests on sonnet. The 5-8x usage Max plan isn't going to be any better if I want to run constant crons, with the Opus model (the docs recommend using Opus).
Good Macs are thousands but Im waiting to find someone who's showing off my dream use case to jump at it.
Something like HELOCs would certainly be an exception.
The point is to disallow people who make a man's yearly salary every 60 seconds from getting <2% loans against an asset pool that would take hundreds of years for the average American to amass, if ever.
The org should also curate selections. Particularly only games that have been well received in past HN discussions, and if they have, the org might add them to the directory.
To convert that figure to a more relatable number: the surface area of the Earth is just about 197 million square miles. With such an error I'm having a hard time trusting the article content.
Technically, if you're measuring surface area, it' important to remember that the earth is not a sphere. There's a bit of a paradox measuring shorelines: the shorter your ruler, the longer it gets, because you're able to capture more complex features. Pethaps the authors took an extremely precise measurement of the surface of Estonia, counting everything down to the sinus cavities of dogs sleeping in alleys...
Can you explain this more? It seems trivial to extrude a 2d coastline along a third dimension to produce a paradoxical areal calculation corresponding precisely to the perimeter paradox...
If you extrude a coastline into a wall the wall's surface area will blow up the same way the measured perimeter does, but that;s because you've turned a boundary-length problem into the area of a different object. It still doesn't mean the country's ordinary map area becomes paradoxical, the extra boundary detail only affects a vanishingly thin strip near the edge, so the enclosed 2D area stays well behaved.
Aha, so you've misunderstood my joke entirely. We agree about the math, please reread my original comment with the understanding that I'm insinuating that the article has deviated from "ordinary map area" and is instead measuring the fractal surface area contained within Estonia's perimeter.
[now that the joke is explained, feel free to laugh]
Would you say it's truly dead or that it fails to meet the performance bar you've described?
The reality is that most devs do not consider a holistic picture that includes the infrastructure they will be deploying to. In many cases, it's certainly a skill issue; good devs are hard to find. And to flip the coin, it's hard to find good ops people too.
The reason DevOps continues to linger, however vague a discipline it is, is because it allows the business to differentiate between revenue generating roles and cost center roles. You want your dev resources to prioritize feature work, at the beckon of PMs or upper management, and let your "DevOps" resources to be responsible for actually getting the product deployed.
In essence, it's a ploy to further commoditize engineering roles, because finding unicorns that understand the picture top-to-bottom is difficult (finding /top/ talent is difficult!). In this way, DevOps is well and alive, as a Romero zombie.
Your inflammatory accusation aside, is there even any indication that OP worked to push such efforts? Believe it or not, I think most HN users are not directly contributing to writing tools that "enshittify" the internet and are collecting a wage writing other kinds of software.
After paying for fuel, insurance, property taxes and maintenance (exclude the possibility of a car note in this scenario), is it still cheaper than taking the train?
As an IC though, me sending a slack message is perhaps less impactful than a PL responding to a report :)
reply