If I was a business owner I’d rather operate under laws that don’t have highly ambiguous definitions of terms that introduces extra risk that is unnecessary in other places.
Lack of adequate calories and nutrition negatively compound. You lose the ability to focus, you increase your medical risk.
I experienced that in my childhood. It’s terrible. I did very poorly academically when I did not have access to food. It’s astonishing to me how fast my academic performance improved after consistently having access to food.
Saying you would rather put yourself at risk instead of hedge your answer on a minor interview question in order to increase your chances of getting a job offer seems like an issue with prioritization.
I’m not saying your conclusion is incorrect but the anecdote provided is survivorship bias. My childhood was much the same in the 90s.
There was a case recently where parents were charged with felony involuntary manslaughter, and felony child neglect because they let their 10 and 7 year cross the street unsupervised and a car hit them and the 7 year old died. As a parent if that’s the reality I definitely hesitate to allow my son out unsupervised when he’s a bit older. I can’t imagine losing your son in an accident and then have the state come down on you while you’re still grieving.
A US based non-profit news organization isn’t going to spend money to pay lawyers to ensure they meet a regulatory burden that doesn’t affect their core demographic.
I could not agree any less with the author. I don’t want APIs, I want agents to use the same CLI tooling I already use that is locally available. If my agents are using CLI tooling anyways there is no need to add an extra layer via MCP.
I don’t want remote MCP calls, I don’t even want remote models but that’s cost prohibitive.
If I need to call an API, a skill with existing CLI tooling is more than capable.
MacOS has a built in 4x4 window tiling which works for this purpose for me. I don’t find ever wanting more than 4 windows open on an ultrawide. Definitely not as powerful as something like xmonad but useful for the majority of my use cases.
Meta is one of the worst offenders here. They are actively lobbying at least the US Congress for laws that require age verification at the hardware/os level.
I’ve found this to be critical for having any chance of getting agents to generate code that is actually usable.
The more frequently you can verify correctness in some automated way the more likely the overall solution will be correct.
I’ve found that with good enough acceptance criteria (both positive and negative) it’s usually sufficient for agents to complete one off tasks without a human making a lot of changes. Essentially, if you’re willing to give up maintainability and other related properties, this works fairly well.
I’ve yet to find agents good enough to generate code that needs to be maintained long term without a ton of human feedback or manual code changes.
Yeah it’s extremely helpful to clarify your thoughts before starting work with LLM agents.
I find Claude Code style plan mode to be a bit restrictive for me personally, but I’ve found that creating a plan doc and then collaboratively iterating on it with an LLM to be helpful here.
I don’t really find it much different than the scoping I’d need to do before handing off some work to a more junior engineer.