Grapher.app is different from Graphing Calculator. It came via an acquisition. All the details are here if you want to read the backstory (assuming the info is correct: https://en.wikipedia.org/wiki/Grapher)
Feels like it might be pertinent to share more details than simply the error code. What country? How are you connecting? Anything out of the ordinary with your setup that might be the cause?
I actually write prompts like that when I'm not under pressure. Claude will sometimes completely ignore your feelings, and sometimes give a little comment, which I just find refreshing in the middle of otherwise often boring sessions. And it does not have an effect on the actual result.
Software isn't solved. 'Coding' is, according to the people of Claude.
Coding (programming) is a tedious and expensive part of software engineering. There's other parts AI isn't doing, such as understanding and refining requirements, and delivery + accountability.
Why is it bittersweet? Carpenters probably didn't cry when their tools improved.
It will be bittersweet when there's no human needed at the wheel but IMHO we are far, far from that. These models/agents are just mimicking human text and need guidance because they often get lost or stuck.
Carpenters would have cried if all their work was reduced to shoving the logs into CNC machines.
Yes there is still human input but it requires comparatively no skill or depth and it gets easier by the month. If I were lobotimized today I'd still be able to function as half-assed architect to AIs anyway.
When was the last time you read fighting distractions/getting "in the zone"/complaint about open space offices thread or comment? They used to be a weekly feature on HN frontpage.
> Yes there is still human input but it requires comparatively no skill or depth and it gets easier by the month. If I were lobotimized today I'd still be able to function as half-assed architect to AIs anyway.
Hard doubt, software engineering is so much more than just literal coding and typing. At least for many of us, the coding/typing part is the easy stuff, everything around that is where the actual engineering happens. If I were lobotomized, maybe I'd get ~10% done today as the day before, if I'm lucky. Even with my full mental capabilities, the agents end up on wild goose-chases unless I'm very specific with what I want, and even sometimes ignoring things if they're too complicated/takes too long, so a bit of thinking is still required to get the right prompts.
And considering how subjective programming is, since it's a creative endeavour after all, I'm not that worried somehow all programmers will be unemployed in just some years.
> When was the last time
Frequency of something doesn't tell you how big of an issue something is, for all we know, HN community (or even the moderators) could have been tired of all the circular conversations where nothing new is being said, and downvote it. Doesn't really tell us much.
Use whatever labels you want, apply charitable reading and I'm sure even you could understand what I mean here. Clearly there are at least two sorts of tasks (or used to anyways) in "software engineering" as a whole, one more mechanical and one more about thinking.
I think carpenters might cry if a company went around shoving every single piece of carpentry they could find into a machine, and then when you press a button on that machine, a chair comes out, and then they go around saying that this machine will replace carpenters forever, and they made this machine with no help from other carpenters, and furniture makers all went "who needs carpenters anymore, lets just use the chair machine"
* https://www.youtube.com/watch?v=pJ4Ol9Tb1D0
* https://en.wikipedia.org/wiki/Terminator_2:_Judgment_Day
This is considering the effects were done in 1990.
https://genius.com/Renaud-laisse-beton-lyrics
I actually write prompts like that when I'm not under pressure. Claude will sometimes completely ignore your feelings, and sometimes give a little comment, which I just find refreshing in the middle of otherwise often boring sessions. And it does not have an effect on the actual result.
Coding (programming) is a tedious and expensive part of software engineering. There's other parts AI isn't doing, such as understanding and refining requirements, and delivery + accountability.
It will be bittersweet when there's no human needed at the wheel but IMHO we are far, far from that. These models/agents are just mimicking human text and need guidance because they often get lost or stuck.
Yes there is still human input but it requires comparatively no skill or depth and it gets easier by the month. If I were lobotimized today I'd still be able to function as half-assed architect to AIs anyway.
When was the last time you read fighting distractions/getting "in the zone"/complaint about open space offices thread or comment? They used to be a weekly feature on HN frontpage.
Hard doubt, software engineering is so much more than just literal coding and typing. At least for many of us, the coding/typing part is the easy stuff, everything around that is where the actual engineering happens. If I were lobotomized, maybe I'd get ~10% done today as the day before, if I'm lucky. Even with my full mental capabilities, the agents end up on wild goose-chases unless I'm very specific with what I want, and even sometimes ignoring things if they're too complicated/takes too long, so a bit of thinking is still required to get the right prompts.
And considering how subjective programming is, since it's a creative endeavour after all, I'm not that worried somehow all programmers will be unemployed in just some years.
> When was the last time
Frequency of something doesn't tell you how big of an issue something is, for all we know, HN community (or even the moderators) could have been tired of all the circular conversations where nothing new is being said, and downvote it. Doesn't really tell us much.