A work frustration:
System 1 is slated for deprecation, therefore improvements for System 1 are not being prioritized.
Systems 2 through X rely on information stored and served by System 1. Systems 2 through X provide services for essential normal operations and issues with them have the potential to cause problems with increasing blast radii over time.
At this time, there is not even a proposal, prototype, or mitigation plan in place to create System A to provide the System 1 support systems 2 through X require.
System 1 is slated for deprecation.
A coworkers quote: "Internal software has two states: Experimental and Deprecated"
Michelle was right. I will not recovery my sanity until I am running my own company.
re: A work frustration:
@orrery I just don't get why it's the norm, though. We, as passionate, knowledgeable people, hell, just as people, aren't being given the time we need to do our work the way it should be done. Just so that people who don't even care can get richer, faster.
*several AU distant, a measurable arc of an unexploitable asteroid belt vaporizes under sustained fire from directed energy weapons*
re: A work frustration:
@kelseyhusky I think that this would be the way of it even if we didn't have that pressure on us, simply because as people we get bored, wander off, and don't always manage hand-offs well enough, so the pressures of bit-rot (new hardware means new features means more complex code means increased risk of emergent bugs means some work just to stay still) will eventually claim any system not actively being maintained.
That said, you're right; it's way worse than it could be.
re: A work frustration:
@orrery ⚙️ 🤖 💎 🌠 🌹 when?
re: A work frustration:
@kelseyhusky As soon as possible, pupper. As soon as we can.
A work frustration:
@kelseyhusky An elder wizard I once knew said that all systems are either failures or legacy horrors to be.
They are either replaced because it's easier to replace them than maintain them, or they're tolerated because they're easier to maintain than to replace.
Sounds like someone here decided to see what happened if you both scrapped and kept the old codebase.