sandeepkd

How would that change when support teams themselves are replaced by LLM agents

I think this is the key to some of this debate.

Management/Product/Product Engineer - When you are responsible for getting the work done then you look for any and every option to speed it up.

Owner/Platform/Senior Engineer - When you are responsible for ensuring it works and can be maintained then you have to pay attention to how to build it, aka the trade offs

You are running a machine with tons of vendor provided agents/scripts to do god knows what on a cloud provider which itself runs tons of agents/scripts to manage that infrastructure and then you expect to be secure.

And no, before the labs there was a degree of fear for everyone to hack into some one else system. With the labs changing the narrative, anyone can just blame the agents for the breach, whoever did it would only get fame and no blame

NK seems to be /dev/null for unresolved issues. Wonder if they receive any monetary assistance for taking all the blames

At this point it feels like they have made it a /dev/null for things which are not easy to resolve and one is still on the hook to provide some answers

It pretty much applies to everything, going along the tide is always easier

This is an interesting take, however from what I seen its other way around. Most security conscious operators would only allow IPv4 instead of IPv6. Your ACL rules and tools are still better at handling/managing IPv4 compared to IPv6

My working theory is that being able to understand a detail answer itself requires a certain level of understanding for that topic. In that absence of that it would throw off a big crowd which was hoping to find something simpler, something that aligns with their existing understanding easily.

There is a cost to produce something based on raw materials and then the possible price you can charge from the customer based on demand and supply.

The term Value is pretty vague here. Its more of a perceived value so its hard to put a number against it, there is no direct way to translate it to something more concrete.

May be bit orthogonal, one way I can think of it is to map to physical needs like clothing, housing, food and medicine?

In a company as big as Anthropic, moving at current pace, the person/team writing this article and the team(s) collecting data would be way distant. It should be more than obvious that the data is being collected in not just one place but many (different teams are looking for different gems in that data). What part is used for training, how and when would be spread across the company way too wide for anyone to confirm with certainity.

  On the IP side, About 6 months ago I used Claude to help me draft a patent application for something which I believed was novel, I verified in the USPTO as well. Then out of being busy I dropped that idea. Couple weeks ago I picked up the work again, verified with Claude for the problem statement to see if there is any existing solution. It suggested my own solution back to me which was surprising since I only use in browser and delete the history explicitly. I asked it for references or resources and it could not find any. That helped me to understand the boundaries bit better.

As of today the eco-system favors a VC backed company for visibility and more. Building a company itself is hard, bootstrapping it when there are VCs willing to fund you feels like an unnecessary risk.

For good or bad, thats by design. These is a significant portion of physical infrastructure associated with internet data flow. The only challenge governments face as of now is being able to segment the traffic to their wishes in its entirety.

Companies already control all the traffic flow on their infrastructure using end-point security solutions, the same can be extended at ISP level, and then Country level

Yes and NO. These are intermediate CA's and for them to be recognized by your browser or system, they need to be signed by another CA or root certificate that your system already trusts.

SO, not all CA's are signed by root certificates already on your machine