| ▲ | ThunderBee 4 hours ago | |||||||
You could say the same thing about any always online software suite and it would be equally fair as we move into more agentic development workflows. EX. Sure, you could go back to the old ways of using a drafting table for your engineering work if CAD went down but it would be exponentially slower… Personally with my workflow I spend 30-60 minutes per Claude feature spec doc when I’m pair planning. If Claude goes down I would just prepare spec docs on my own until it came back online and then rapidly review them before calling the coding workflow. | ||||||||
| ▲ | monegator 2 hours ago | parent | next [-] | |||||||
>You could say the same thing about any always online software suite Precisely. Every online-only solution is a huge risk i personally do not want to take, i've always done my best to use offline-only tools. That may restrict me from the latest and greatest, but i prefer not to be left at mercy of any corpo | ||||||||
| ▲ | voidUpdate 34 minutes ago | parent | prev | next [-] | |||||||
How does "CAD" go down? Sure, there are online CAD systems (onshape), but there are offline ones too (fusion, freecad) | ||||||||
| ▲ | isodev 2 hours ago | parent | prev [-] | |||||||
> You could say the same thing about any always online software suite But this is the reason "serious shops" do not use always online software and tools in critical parts of the SDLC. There is a difference between influencers/people on socials promoting things vs. reality where the expectation is that things don't just stop working because there is an internet outage or some 3rd party disruption | ||||||||
| ||||||||