These projects quickly reach a point where evolving it further is too costly and risky. To the point that the org owning it will choose to stop development to do a re-implementation which, despite being a very costly and risky endeavor, ends up being a the better choice.
It's easy to say that organizations should do it right the first time, in terms of applying proper engineering practices. But they often didn't have the time, capital, and skillset to do that. Not ideal, but that's often how things work in the real world and it will never change.
Organizations should do it not catastrophically wrongly, especially once a core design / concept is mostly solidified. Putting a little time into reliability and guardrails prevents a huge amount of downside.
I've been at organizations that don't think engineers should write tests because it takes too much time and slows them down...
Clicking through and stumbling upon Croatia, which specifies only "Classified deployment", has left me absolutely cackeling. Seems hilarious that they're willing to say that they use it, but unwilling to state if it's for early testing, civilian-level beaurocracy, or Croatia's equivalent of specialized armed forces.
That they publicly use it at all is great though, as it likely helps shift the Overton window of what's normal, and what fits standard useage of Matrix-Synapse
Question, with so many major orgs using it, are there no plans for manual status? The one thing I miss vis-a-vis teams is the ability to manually set myself away, appear offline, busy etc.
Matrix shows me as active (green dot) when I have the client open but there's no way to override that. At least none that I found. I'm a bit surprised all these big governmental clients didn't ask for such a feature :)
There's a big gap between lots of orgs using it, and lots of orgs paying for development of it. That said, BWI in Germany is currently funding custom status so it should be coming soon :)
It's not a good look to break userspace applications without a deprecation period where both old and new solutions exist, allowing for a transition period.
I would argue they are. Those traditional methods aim at keeping complexity low so that reading code is easier and requires less effort, which accelerates code review.
If boilerplate was such a big issue, we should have worked on improving code generation. In fact, many tools and frameworks exist that did this already:
- rails has fantastic code generation for CRUD use cases
- intelliJ IDEs have been able to do many types of refactors and class generation that included some of the boilerplate
I haven't reached a conclusion on this train of thought yet, though.
I change themes just often enough to completely forget how to do it and also forget whatever other adjustments I had to make to it all work. And like... is my config versioned somehow? This is a long way to say, Thank You for inspiring me to look at all that stuff again!
This is a very costly way of developing software.
reply