Was left stranded in Berlin last night trying to get home to a neighboring city, which should have taken 45 minutes (more like 1h20 nowadays due to time tables and whole regional train lines being down for maintenance til EOY).
The lack of communication was probably the worst of all. Announcements saying to take alternative means of transport. The DB Navigator app insists that everything is still running and it was impossible to get clear info as to whether RE trains were also affected.
Eventually we took a Miles car home and because of this and past unreliability I'm, sadly, thinking about getting a car instead.
This was also my first thought when reading the title: because Claude is a tool you use and co-workers are either competitors or people preferably dependent.. an anti-pattern and not good culture but sadly the norm.
That's not to say that the help-vampires the parent mentions don't exist. I think we culturally are afraid of pushing back against them: telling them to RTFM and then come back.
During the first World War, Belgium divided in its Dutch (Flemish) and French (Walloonian) speaking constituents, had many such Walloonian officers rule over often Flemish soldiers. It wasn't unheard of that an officer got shot by his own people.
I'd dread managing technical people in a field I have no experience or knowledge; in my experience, especially in tech, such managers are often held hostage by engineers who stubbornly don't want to do things, tell fibs about feasibility, ... The other side of that is that such managers often make progress making said engineers promises that often turn out to be carrots on sticks or outright lies.
If you can't go with in the trenches, what good are you and how do you expect to build a trusting relationship?
> Imagine that the only PC you could buy one day has everything tightly integrated with no user serviceable or replaceable parts without a high-end soldering lab.
This is akin to a psychopath telling you they're "sorry" (or "sorry you feel that way" :v) when they feel that's what they should be telling you. As with anything LLM, there may or may not be any real truth backing whatever is communicated back to the user.
Likewise, I tested this with a project we're using at work (https://deepwiki.com/openstack/kayobe-config) and at first it seems rather impressive until you realize the diagrams don't actually give any useful understanding of the system. Then, asking it questions, it gave useful seeming answers but which I knew were wholly incorrect. Worse than useless: disorienting and time-wasting.
> Do companies use GitHub sponsorships to judge the health of dependencies? Will they create budgets to support their dependencies systematically?
In my past I've worked with multiple places that absolutely loved open-source. Because to them it was "free". Something they could use in their products and then charge customers for. Often these opportunistic parasites would never contribute anything back; going out of their way to work around missing features or bugs rather than trying to fix or contribute towards the codebase.
I doubt that these companies now, despite depending on such OS, would pay paying money/contribute; no matter how administratively trivial it became.
The lack of communication was probably the worst of all. Announcements saying to take alternative means of transport. The DB Navigator app insists that everything is still running and it was impossible to get clear info as to whether RE trains were also affected.
Eventually we took a Miles car home and because of this and past unreliability I'm, sadly, thinking about getting a car instead.