There was a case two weeks ago about someone unable to locate their missing parent with a tracking application (I'm assuming the parent has some sort of dementia) because the application could not connect to the servers. Link in spanish https://hipertextual.com/actualidad/los-bloqueos-de-laliga-e...
I am pretty sure Telefónica will tell people they can just switch to their own services.
Telefonica has a business branch that offer some services similar to cloudflares ones like CDN, DDOS Protection, etc...There is a huge conflict of interest here to use copyright law to make cloudflare and other competitors customer's life as crappy and unusable as they can.
No really.... more so when some giant multinational that is bribing (lobbying is just legalized bribes, lets use the real word for it) the politicians start to loose money. Then an exception will be made for them, and they will continue. What they really want is for Cloudflare and others to give in and police it for them.
It's not, unless you think part of the definition of "worth their salt" is never working for a company with bad resource allocation. And I don't see why it would be.
Consumer CPUs don't have enough PCIE lanes to do that. Even if they had physical x16 slots, at most two of them would be x16.
What's cheap to you? You can find Epyc 7002/7003 boards on ebay in the $400 range and those will do it. That's probably the best deal for 4x PCIE 4.0 x16 and DDR4. Probably $500 range with a CPU. That's in the ballpark of a mid to high end consumer setup these days.
That's the path I'm taking.
All with all those PCI-e lanes available.
If I had more income, I would also buy 4x 96g Optane drives of p0 swap disks and a few ssd's for p1 swap disks. To evaluate how well you can get a 1T model running in these absurd ram prices.
Even if you're fine with risers, that might not be enough. If the bridge lanes are PCIe Gen 3, as many consumer boards have, your Gen 5 card might not init. I extensively tested several motherboards to try and get my AM5 CPU talking to a triple Radeon AI Pro 9700 XT setup, and they absolutely refuse to come up on PCIe3. I was using dummy EDID plugs for them, so they think they have a display, ruling out that issue.
What I eventually had to do was buy a used Threadripper box to run those cards, because PCIe Gen 4 definitely works.
It's my understanding that a single senator can't just filibuster anything they want unless the conditions are right. It depends on a few different factors and requires the bill to be brought to the floor for debate, which itself would require cooperation from the majority leader. That's not likely to happen.
If you're solo you have to actually stand up and talk still it seems. (And even then a 60+ person majority can vote to close the debate on you) Nobody has done it solo for more than 24 hours or so. Presumably at that point you're about ready to keel over.
> and they're just as capable as using AI as anyone
Wouldn't the assumption be the opposite, in that AI is magnifying the decision making of the engineer and so you get more payback by having the senior drive the AI?
I've found this to be true so far, junior engineers with AI can be super productive but they can also cause a lot of damage (more outages than ever) and AI amplifies the sometimes poorly designed code they can generate.
I suspect a lot of it best practices will be enforcing best practices via agents.md/claude.md to create a more constrained environment.
I’ve observed radically different workflows amongst senior candidates vs junior candidates when using an ai. A senior candidate will often build an extremely detailed plan for the agent - similar to how you would do a design for/with a junior engineer. Then let the agent go full throttle to implement the plan and review the result.
Juniors seem to split into the category of trust everything the ai says, or review every step of the implementation. It’s extremely hard to guide the ai while you are still learning the basics, opus4.6 is a very powerful model.
My observation has been that there are a lot of personal styles to engaging with the LLMs that work, and "hold the hand" vs "in-depth plan" vs "combination" doesn't really matter. There is some minimum level of engagement required for non-trivial tasks, and whether that engagement comes mid-development, at the early design phase, or after isn't really that big of a deal. Eg; "Just enough planning" is a fine way of approaching the problem if you're going to be in the loop once the implementation starts.
I don't claim to have any special skill at AI, but as a 'senior' dev, my strategy is exactly the opposite. I try to be as lazy, dumb and concise as I can bring myself to be with my initial prompt, and then just add more detail for the bits that the AI didn't guess correctly the first time around.
Quite often the AI guesses accurately and you save the time you'd have spent crafting the perfect prompt. Recently, my PM shared a nigh-on incompressible hand-scribbled diagram on Slack (which, in fairness, was more or less a joke). I uploaded it to Gemini with the prompt "WTF does this diagram mean?". Even without a shred of context, it figured out that it was some kind of product feature matrix and produced a perfect three paragraph summary.
I've never really seen the value in the planning phase as you're free to just throw away whatever the AI produces and try again with a different prompt. That said, I don't pay for my tokens at work. Is planning perhaps useful as a way of reducing total token usage?
It's more about the size of the task I try to do, it's quite possible to get opus4.6 to one shot a "good" 30k loc change with the right planing doc. I'm not confident I could get similar results handholding. I also tend to want to know the major decisions and details in such a change up front rather than discovering them post-hoc.
One-shotting 30k LOC is no use to me because none of my colleagues will review a PR that big. But more to the point, I wouldn't be able to review it either, and I think we're still at a point where you do want to look carefully at the output these tools generate.
Being able to clearly describe a problem and work with the AI to design a solution, prioritise what to put the AI to work on, set up good harnesses so the quality of the output is kept high, figure out what parallelises well and what’s going to set off agents that are stepping on each others toes… all of this needs experience and judgement and delegation and project organisation skills.
AI is supercharging tech leads. Beginners might be able to skill up faster, but they’re not getting the same results.
For a good senior, yes you get massive returns, which is why those good seniors are in incredibly high demand right now.
For average to low-performing intermediates/seniors... there's not much difference in output between them and a good junior at this point. Claude really raised the skill floor for software development.
My thinking is a bit different here: Seniors, even mediocre ones, already learned a lot of hard lessons by doing things pre-LLMs, even pre-SO. Those skills are valuable and I don't know how to train them into juniors.
I find it easier to get a reasonably smart senior to use AI in a good way, than to train a junior in what thinking to do, and what to outsource, learning basics about good design, robustness and risk analysis. The tools aren't the problem per se, it's more about how people use them. Bit of a slippery slope.
That's just my anecdotal experience from not a whole lot of data though. I think the industry will figure it out once things calm down a bit. Right now, I usually make the bet to get one senior rather than two juniors. Quite different to my strategy from a few years ago.
reply