llanowarelves

Or you could say it the other way around: Even leading scientists are susceptible to letting emotions get the best of them and double-down defending their personal investments into things.

"A scientific truth does not triumph by convincing its opponents and making them see the light, but rather because its opponents eventually die and a new generation grows up that is familiar with it." - Max Planck.

Same happened to me on Gumroad. I ended up with 5 or so before I had to contact customer support to merge them all.

Some people rightfully want to see what the engineering effort and roadmap is gonna be before becoming invested in it, since there's always a cost.

Simple aesthetic changes and codes of conduct / political alignment for contributors are not enough for forks to become full things of their own. Even if they can help (branding, community, etc.). Or hurt (Forgejo is harder to pronounce. And CoC have potential downsides, possibly excluding good people, ironically, over banal minutia and hostile environment around being "not hostile" - like you saying he is "hung up" on it...).

Gitea was already a fork of Gogs, so why should contributors use this fork of a fork?

These forks (and direct clones) are like little political secessionary/independence movements, both making lofty statements and splitting would-be contributors. Sometimes it works out very well and they become full independent things of their own (GNU stuff), but it's fair to want to get on to see the actual engineering side of things.

It's so you don't need an exact term, you can search for a synonym or something "similar" in concept.

So more like a search engine than just a Ctrl+F in a file for a string of tokens

Learned a lesson that you only have to "spend" (forgo) $250 to cause that company $14m in losses (that you could have prevented)

Indeed the choice for me as recent as 1-2 years ago was still SVN vs Perforce. Despite only having ever worked with Git

I liked the one Pennsylvania bill introduced where subscription services have to email you that they're about to charge you again.

Throws a wrench into the "was hoping you forgot about it, now ask/argue with customer support on the phone" dark pattern.

Well-written comment. I would love to read an extended version of this with examples, pictures, etc. as a blog post / youtube video.

Thanks. A lot of good stuff here that may go overlooked.

As with any business/product, consumers are also free to say what they think to the business, other users, competitors, and anyone else.

They are great because you can find so many problems at much lower cost earlier. And communication across domain and skill levels.

Maybe their unpopularity among developers stems from trauma of the UML+OOO+Waterfall days and an overcorrection in the opposite direction.

Or many more are doing it and just not talking about it since it's not as exciting as code.

It's clear you've never experienced significant amounts of tech debt that you aren't allowed to fix because it doesnt Excel chart nicely for the boomers higher up who only see things in terms of "something working on the screen" or not.

And no, I'm not going to rebel by secretly fixing it silently and unappreciatedly while peers pile on hacks and get promoted for things on the screen.

Luckily Figma has a great engineering background as its basis with technical founders, so they can avoid becoming that, but not all companies are like that.

I think it ends up being hybrid, like seen in CQRS and especially with DDD. Toss in "Vertical Slice Architecture" as well. What abstractions you want can decided on a per command or query basis and it feels natural.