Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@jestdotty It also only took two colleagues and a workday to get the devenv set up on my machine, on the other project it took over a week and all seniors on my team needed to chime in with some domain knowledge none of the other seniors could've guessed.
-
@lorentz oooh they explained the domain knowledge =]
... I spent 3 days trying to get the IDE to just launch and not show errors. the kicker? then the lead had overwrote the config files that made it work... and overloaded me with work so I spent another 2 days figuring out the IDE again while she kept insulting me and then I had no time to document it even though I really friggin wanted to for obvious reasons =]
and there was absolutely no seniors to give me any advice =] -
@jestdotty The community is great here even though evidently we have a knowledge silo problem, the helpful attitude and air of camaraderie is the main thing keeping me at the company since it's a shit project and the odds of ever learning anything non-obsolete outside the Microsoft stack is vanishing small.
-
@jestdotty that sounds horrible, luckily I'm kind of secure right now so if it ever turned this bad I could leave.
-
@lorentz is this one of those "it would be faster to remake than to maintain projects"?
-
@BordedDev not really because it's also gigantic
-
@lorentz That's unfortunate, odds it's worth to strangler fig it? From my experience, dealing with painful legacy systems is a quick way to permanent headaches if you aren't able to update it 😅
-
@BordedDev That's the first time I hear this term, I'm not sure what it means. Refactoring efforts are of course ongoing but management insists that fast delivery on features is more important now to accommodate our new market before they look elsewhere, so POs are reluctant to prioritize any refactoring work. We'll see how it goes, I don't trust mgmt's word for a second but I don't have a family so I don't need to see more than half a year ahead.
-
@lorentz Yup and then you hit the "hey we want to onboard the client which has 200k of a thing" and they realise they fucked up.
Ship of Theseus is another name, and yeah, management often doesn't understand the effect of an easy to modify system until they have one where they can ask for anything it's able to done while in a meeting with them - love that old system :( -
@AlgoRythm It seems that buffered controller JSON responses are capped at u16max. We're pretty sure streaming responses don't have that restriction, and it's possible that the limit can be raised, but I'm not about to offer yet another route that can save a penny by forcing the browser to render 6k Knockout components, when instead I can pretend that the cheapest solution is pagination or lazy loading and thereby convince them to do the right thing for the wrong reason.
-
@lorentz yeah obviously the right choice is pagination or cursors depending on the use case. But I was just absolutely shocked you reached a limit there. I’ve worked with some endpoints where we have needed to up the limit a bit, but never gotten to the max
what people think when I say I program in COBOL..
Usual legacy development flow (https://turnoff.us/geek/...)
Got moved to higher prio project
- disastrous security
- Built with Knockout.js in 2016
- entire folders of business logic duplicated 3 times to allow for the business requirements of separate regional branches to evolve independently
- Application server in ASP.NET Core MVC but the *real* backend is a WCF service
- there is an outstanding ticket for a list view that fails to load because the API response exceeds the .NET serializer's maximum length. The proposed solution is to stream it down to the client which then collects it into a JS array and renders a DOM node for all 6k rows
- mgmt wants to scale up to the entire European region, not with a single installation but still with a single codebase
- the Germans want interactivity with Relay
- prod database copied around and cleaned to establish new environments, migrations lost to time
- read-only queries have a tendency to deadlock
rant
legacy