314 karma · joined January 19, 2024
As an IC though, me sending a slack message is perhaps less impactful than a PL responding to a report :)
This is the premise of the comic Power Nap.
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.
I distinctly remember their GH page being flooded with issues written in Chinese.
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 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.
The subject of the article, and fellow social media participants, are hedging a bet that manual trade jobs will be safe forever, at the cost of a salary cut and inflicting physical damage to the body. All to do a trade that perhaps doesn't even interest them that much. Insecurity, maybe even arrogance, is driving these people outside of the white collar workforce and I think they will get burned for their decision in the long run. Because there really is no guarantee that these physical jobs will be safe.
The other subtext is that white collars should take a salary cut to work in a different field. And who absorbs the difference in salary that is no longer being paid out? No one that is the subject of this article.
Actually up until a few months ago I swore I just couldn't use these hosted models (I regularly use local inference but like most my local hardware yields only so much quality). Tech companies, nay many companies, will lie and cheat to squeeze out whatever they can. That includes reneging promises.
With data privacy specifically I always take the default stance that they are collecting from me. In order for me to use their product it has to be /exceedingly/ good to be worth the trade off.
Turns out that Claude Code is just that damn good. I started using it for my own personal project. But the impetus was the culmination of months questioning what kind of data I'd be okay with giving up to a hosted model.
What I'm trying to say is that this announcement doesn't bother me that much because I already went on my own philosophical odyssey to prepare for this breach of trust to occur.
I really can't put frameworks in the same bucket as AI. At least frameworks describe an abstract model for a developer to rationalize and think through. AI allows (but doesn't mandate) a developer to write code that they don't understand.
Perhaps I've worked on business logic so long instead of esoteric efforts; what real world use case would benefit from not leveraging a framework where applicable?
In fact, I see your publicly posted resume; are there really developers out there rawdogging Javascript? What problem space do you hire for that mandates the ignorance of >15 years of JS libraries?
And does your business pays above market rate for these skilled developers? Without understanding the problem space I just assume your business tries to hire talented people at exploitative wages. Regardless it appears to be a staggering waste of talent unless the higher quality significantly reduces the cost center of downtime, bugs etc (I find this hard to believe)
`uv` is great but `pipenv` is a perfectly well-tested Python dependency manager (albeit slow). Down in the instructions it explicitly asks you to use `pipenv` to manage* dependencies. I also do not think your assertion of "what is a Pipfile in any context" is fair, as I don't think I've ever seen a project list a dependency manager and then explicitly call out artifacts that the dependency manager may require to function.
I don't see how you could say this with a straight face. We know at this point that factory jobs inflict physical damage to the body, a priceless artifact that no wage could replenish. I find it difficult to address your last paragraph as it's just not based in reality. Anecdotally, many people I know who take an hourly wage at factories never shift elsewhere. There is no waiting, and often they will start their families younger than their salarymen equivalent, 30 years ago or now. Perhaps they failed by your standards?
I don't see what value this provides that rsync, tar and `aws s3 cp` (or AWS SDK equivalent) provides.
I do not have unlimited funds to plug in some token and burn a bunch of money when writing code.
I am gpu poor. I'm lucky that 8gb vram can run the smallest models. But the output is so poor that I lose out to anyone using a hosted service.
If anything this article shows that building great programs is less democratized than it once was.
Edit: to add on, the only evidence that this runs anywhere but Apple Silicon is the maintainer's Twitter where they show it running on two Macbook Pros as well as other devices. I'm not sure how many of those devices are not ARM.
I'm not throwing shade at the concept the author is presenting, but I'd appreciate if they could slow down functional commits (he is writing them right now as I type) and truthfully modify the documentation to state which targets are actually able to run this.