I actually rather dislike having my info spread over a gazillion services, all of them having their own paid accounts or advertising. Also, a single unified search for all communication and shared notes would be very helpful.
Also, I'm not familiar with ClickUp nor Dobase, but I imagine you can have them open in multiple tabs, allowing for your preferred way of working?
> A diagram is a dense way to express information.
I'd say it's a lossy way to express information. I find that architecture diagrams often cannot express the exact concepts I mean to communicate, so you're left trying to shoehorn concepts into boxes that are somewhat similar, and try to make up for the difference using a couple of cryptic words.
Prose doesn't look as nice, but allows me to describe exactly what I want to say, on any level of detail required. Of course, like with a diagram, you do need to put in significant time and effort to make it comprehensible.
> I'd say it's a lossy way to express information.
A simplified explanation of the system is by definition lossy. This equally applies to a plain English description.
I’ve been in many design reviews and similar forums where someone has attempted to present a design through written English and finally someone says “we need a diagram here; this is too much to follow” and everyone in the audience nods because they are all lost.
One of the problems with trying to communicate system design with prose is that it makes sense to the person who writes it and has full context, but the audience is often left confused. Diagrams are often easier to follow specifically because they look under specified when they are.
> finally someone says “we need a diagram here; this is too much to follow” and everyone in the audience nods because they are all lost.
Yes, that happens. I can't remember any occasions where the diagram actually cleared things up though.
Coming to think of it, one way that seems to be pretty effective at getting complex designs across is in an interactive presentation with the presenter drawing on a whiteboard, starting simple and adding stuff while explaining what and why. The narrative is very important though. The whiteboard drawings by themselves are absolutely useless.
> I can't remember any occasions where the diagram actually cleared things up though.
I would be very concerned about the quality of the engineers I was working with if they couldn’t produce helpful diagrams.
It’s not coincidental that discussion of system architecture is usually accompanied by diagrams. They should be helpful. And in fact…
> Coming to think of it, one way that seems to be pretty effective at getting complex designs across is in an interactive presentation with the presenter drawing on a whiteboard, starting simple and adding stuff while explaining what and why.
You seem to agree that they are helpful.
> The whiteboard drawings by themselves are absolutely useless.
This seems like sort of a straw man, though. I don’t think anyone advocates for system diagrams in the absence of any context.
Yeah. If ordering a pizza also regularly involves entering BIOS setup to change boot device ordering, change SATA mode from RAID to AHCI and disable secure boot, depending on your distro.
This is funny. I have an HP PC that has an option in the BIOS to "prepare for RAID" or some such. I wondered what that was, so I turned it on. I had Linux on it at the time, and nothing happened. I shrugged and just forgot about it.
Fast forward a few months later, when I gave this PC to my dad. He installed Windows on it, then started thinking the PC was somehow borked: "the installer sees the drive, installs, reboots, then it fails to boot". I was shocked, that PC worked perfectly.
Then I remembered about that setting, told him to untick the box in the BIOS, and he was off to the races.
As you said earlier, therapists are (thoroughly) trained on how to best handle situations. Just 'being human' (and thus empathizing) may not be such a big part of the job as you seem to believe.
Training LLMs we can do.
Though it might be important for the patient to believe that the therapist is empathizing, so that may give AI therapy an inherent disadvantage (depending on the patient's view of AI).
Socialization with other humans has so many benefits for happiness, mental health, and longevity. Conversely, interaction with LLMs often leads to AI psychosis and harms mental health. IMO, this is pretty strong evidence that interaction with LLMs is not similar to socialization with real humans, and a pretty good indicator that LLM “therapy” is significantly less helpful or even harmful than human-driven therapy.
It used to be, but only in cases where your distro doesn't just package whatever software you require. Nowadays I prefer Flatpak or AppImage over crappy custom Windows installers for those cases. They allow for sandboxing and reliable updating/deinstallation.
These days, I equate anything that ships via docker/flatpak first as built by someone that only care about their own computer, especially if the project is opensource. As soon as a library or a tool update, they usually rush to add a hard condition on it for no reason other than to be on the "bleeding edge".
I'm with you on this, but I do want to point out that a big reason that people will update bundled libraries like that is because they don't want to put the effort in to see whether their bundled library versions actually have any critical vulnerabilities that affect the project. It's easier to update everything and be sure that there are no critical vulnerabilities.
In other words, the Microsoft Windows update process as applied to software development.
But we also want devices that are thin and lightweight. Watertight battery compartments are super easy (barely an inconvenience) if you "just" make the device thicker and heavier.
Also, I'm not familiar with ClickUp nor Dobase, but I imagine you can have them open in multiple tabs, allowing for your preferred way of working?
reply