> ad hominem, type of argument or attack that appeals to prejudice or feelings or irrelevantly impugns another person’s character instead of addressing the facts or claims made by the latter.
> Ad hominem arguments are often taught to be a type of fallacy, an erroneous form of argumentation, although this is not necessarily the case. A number of scholars have noted that questioning a person’s character is a fallacy only insofar as the person’s character is not logically relevant to the debate.
You are right! The link does discuss cases where it's not a fallacy - in those cases, it is instead a valid argument. Again, not what you said.
It wholly does not. It in no way qualifies the statement that people who use tools with "more friction" (the unsound assumption under attack) because they view it as a puzzle game as a subset of the total users of that tool, and devotes zero time to discussing any alternative interpretetations of why someone would do so.
> I think the reason these types of discussions never die is because people in general tend towards closed mindedness. It's hard to put yourself in other people's shoes, and even harder to entertain the possibility that you're wrong.
I think the real reason is that people are used to GUIs who see the "harder tools" cannot entertain the possibility that they are wrong, and see the need to constantly make these hit posts to validate themselves. I have _never_ seen a vitriolic post made by a vim/emacs/tmux/etc. user telling users to switch over - I have seen countless by the "other side". I myself switched to terminal native workflows, not because of one of these posts but despite them, seeing how people who actually used these tools came off way more positive and seemed to enjoy their work way more than I saw from people who used e.g. VS Code and endlessly complained about anything not fitting into their worldview. It's exhausting and provokes no real discussion - nobody is actually being swayed by them, and it just adds fuel to the fire, letting people with opinions swing them around
prepending argumentum is literally just expanding the informal name for the fallacy to the full name of "an argument to the person", easily verifiable with one search query. unless you are saying that you were 1. originally just making your own contraction from argumentum ad hominem, 2. normally use latin in online forum comments, 3. often use ad hominem in your own speech to mean a different thing from the common parlance, i think this is an Obvious Fabrication (!!!)
I did this too for my BSc! Prof. Yee King is a great teacher, and although I was mostly doing it for the qualification and knew most of the course materials going into the degree, his explanations of web app architecture still really helped solidify my understanding. It's a great course in general, especially if you like data science
I would say at this point it's better than Google Photos!! The team is absolutely amazing, and I agree that it's astounding to see IMO the best (general purpose) photo app out there being open source
I think writing the instructions for such an agent would be almost as much work as maintaining the wiki and learning your preferences yourself (and both may be coupled intrinsically unless you already manage a large enough notes system). The crucial problem is that the agents lack 1. taste and 2. the ability to know what is good for them. I've bounced off trying these like three times over the last couple of years, twice after Feb 2026, simply because it requires way too much toil that would be better (IMO) put into maintaining your own knowledge base, where at least that toil would result in learning
It's not insanely hard, I've done it before with a dummy plug and it's possible with the current implementations (essentially what you said: just a separate Wayland session). The reason it is not better supported, I would hazard, is because not many people really need their session locked when they're away - they just need to remote in.
I do feel like rewriting a front end that depends on the same backend is much less perilous than the alternative - in the end its basically just a presentation layer change
Came here to say this - you can construct a point to win this argument that needless rewrites are only for the engineer's satisfaction and serve no business need, but the article clearly argues against itself IMO. Rewriting to make it more ergonomic for developers to work with is ultimately going to be better for the business
maintaining an LLM wiki has been a lot more effort than I thought, at least if we are trying to maintain a high quality in structure and writing comprehension (for easier lookups both for the agent and human). Are people just shotgunning their agent wikis or how
Do you mean the local session would be locked while you work unlocked from remote? That should be doable with a separate session using a dummy HDMI plug, but your original comment read to me as being able to remote in and lock the session, which is 100% possible with Sunshine
Software engineer with a background in infrastructure, backend systems, and developer tooling. I enjoy building systems that are easy to operate, easy to change, and automate away repetitive work. Strongest areas are Nix/Linux, CI/CD, infrastructure, and Rust/Python.
Most recently I was a Founding Engineer at Alpha Story. I built features across the stack, led an authentication migration from Supabase Auth to an in-house system with no downtime, automated infrastructure with OpenTofu and GitHub Actions, cut CI times by more than half, and stepped in to lead engineering after the CTO left.
Before that I worked in production operations supporting more than 100 AWS-hosted government websites, where I wrote internal tools to automate operational workflows.
I contribute to nixpkgs, Home Manager, Hyprland, NVF, pullomatic, and other open-source projects. Personal projects are mostly around Nix, Linux, Rust, and developer tooling.
I'm looking for backend, platform, infrastructure, or developer tooling roles.
<https://rrv.sh>