I liked agile as it was practiced in the “Extreme Programming” days.

• Rather than attempt to design the perfect system from the get-go, you accept that software architecture is a living, moving target that needs to evolve as your understanding of the problem evolves.

• Rather than stare down a mountain of ill-defined work, you have neat little user stories that can be completed in a few days at most and you just move around some Kanban cards instead of feeding a soul-sucking bureaucratic ticketing, time tracking and monitoring system.

• Rather than sweat and enter crunch mode for deadlines, the project owners see how many user stories (or story points or perfect hours) the team completes per week and can use a velocity graph / burndown chart to estimate when all work will be completed.

.

But it’s just a corporate buzzword now. “We’re agile” often enough means “we have no plan, take no responsibility and expect the team to wing it somehow” or “we cargo cult a few agile ideas that feel good to management, like endless meetings with infinite course changes where everyone gives feel-good responses to the managers.”

Having a goal, a specification, a release plan, a vision and someone who is responsible and approachable (the “project owner”) are all part of the agile manifesto, not something it tries to do away with. I would be sad if agile faces the same fate as the waterfall model back in its time and even sadder if we return to the time-tracking-ticket-system-with-Gantt-chart hell as the default.

Maybe we need a new term or an “agility index” to separate the cases of “incompetent manager uses buzzword to cover up messy planning” from the cases of “project owner with a clearly defined goal creates a low-bureaucracy work environment for his team.” :)

Tankies make liberals uncomfortable because liberals believe they are the furthest left you can go

Without trying to be combative, but that sounds like one of those tidbits which one side believes about the other, circulated only to divide. At least I don’t have the impression that it is a view with any footing amongst liberal-minded people.

Most liberals want to move further left, ideas like free college and public education, public transport, less corporate power and splitting up large corporations, even unconditional basic income, etc. are popular with the majority. Just violent revolution and authoritarianism won’t roll, after all, liberal means “live and let live.”

As a mixed-ideology lefty (maybe I fit within your definition of liberal), I’m not worried about tankies being too far left, not at all, rather, I am tempted to think of them as confused right wingers believing themselves to be “the left.”

Thanks for bringing this up, it’s really needed.

Your example is just one of many I’ve seen. The entire instance seems to be engaged in an opinion shaping campaign where only this gross mix of Western doomerism with Russia/China-glorifying fascism is allowed to thrive.

I don’t know how to best deal with such indoctrination chambers. Their members become completely divorced from reality and there’s no way to pull them back from the brink because anything you could say to that effect gets moderator-deleted. Yet vice versa, they can freely spread their propaganda and engage in “raids” on other instances.

That would (just like Git LFS) store full, separate copies of every single version of the large files I manage. I really, really don’t want to go there, nor do I have even a fraction of the hard drive space for that…

That’s what I meant when I wrote “Git submodules can only point to a whole different repository” - they can’t point to a path inside a repository, only to another repository root. That unfortunately renders them useless for me (I’d have to set up in the order of hundreds of small repositories for the sets of shared data I have).

I’m already using Git for source code related versioning, but some use cases involving large binary files with partial updates aren’t well covered by Git (I’ve gone into some detail in my reply to @vvv@programming.dev).

There’s also the lack of svn:externals in Git. Git submodules can only point to a whole different repository as far as I’m aware.

I’m already using Git, thus my experience with Gitea. I am well versed with svndumpfilter and git-svn to extract and migrate individual Subversion repositories to Git.

I’m not only hosting code, but I have several projects involving large binary files with binary changes. Git’s delta compression algorithm for binary files is so-so. Git LFS is just outsourcing the problem. Even cloning with --depth 1 --single-branch gives me abysmal performance compared to Subversion.

So I’m still looking for a nice WebUI to make my life with the Subversion repositories I have easier.

After finding out that tools that are to “bureaucratic” don’t stick with me (bureaucratic as in, I need to fill out forms to create projects/tasks, update them and follow defined workflows), I ended up with Trilium.

It at first looks like a very free-form note taking app (a tree of documents on the left, click and edit away), but it has a lot of extra functionality that lets you construct journals and tasks lists in the document tree (like its Task Manager which is already set up in the Demo notes of a new Trilium install).

Linux Unix since 1979: upon booting, the kernel shall run a single “init” process with unlimited permissions. Said process should be as small and simple as humanly possible and its only duty will be to spawn other, more restricted processes.

Linux since 2010: let’s write an enormous, complex system(d) that does everything from launching processes to maintaining user login sessions to DNS caching to device mounting to running daemons and monitoring daemons. All we need to do is write flawless code with no security issues.

Linux since 2015: We should patch unrelated packages so they send notifications to our humongous system manager whether they’re still running properly. It’s totally fine to make a bridge from a process that accepts data from outside before even logging in and our absolutely secure system manager.

Excuse the cheap systemd trolling, yes, it is actually splitting into several, less-privileged processes, but I do consider the entire design unsound. Not least because it creates a single, large provider of connection points that becomes ever more difficult to replace or create alternatives to (similarly to web standard if only a single browser implementation existed).

I’m on OpenRC, so I can’t say anything about systemd, but I have several SSHFS mounts (non-auto) listed in my fstab:

sshfs#root@192.168.0.123:/random-folder/ /mnt/random-folder fuse noauto,uid=1000,gid=100,allow_other 0 0

Is that similar to what you’ve tried in your fstab? I’d assume replacing noauto with auto should just work, but then again, I haven’t tried it (and rebooting my system right now would be very inconvenient, sorry).

It also might require you to either use password-based login and specify the password or store the SSH keys in the .ssh directory of the user doing the mount (should be root with auto set).

Yep. The personal responsibility gambit (or should I say fallacy?).

It was such a clever idea, starting with Coca Cola’s “Litterbug” campaign (where they campaigned against bottle deposits under the guise of wanting “personal responsibility” over “regulations.”)

It’s “up to the consumer” to make the right choices. It just so happens that the meat from decently treated animals is five times more expensive and that you have to drive 100 miles to buy it. Or that being environmentally conscious has been made into a tiring exercise in futility where you constantly have to inconvenience yourself.

As an added bonus, individuals trying to convince other individuals to inconvenience themselves in the same way can be painted as obnoxious, holier-than-thou and insufferable. A real double win for unscrupulous big business.