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
-
They were providing URLs apparently... 👀
Some even had an extra provider to include the paths... That also had a method for getting a path using an enum (should have a factory instead for stuff like that).
And then yeah... Most were just concatenating from a base URL brought in from somewhere else...
It's been a long day 😒
Everyone always says the previous developer was crap, sometimes you're right
bad code that works 👍
source: reddit.com/r/ProgrammerHumor/
Maintaining software built by interns who have all quit by now and made zero documentation
Adding a new feature to a mobile app that has a bunch of classes for getting URLs! Want some examples?
FallbackUrlProvider
CompositeUrlProvider
CompositeRouteUrlProvider
CompositeBaseUrlProvider
RootUrlProvider
I was half expecting to find FallbackRootBaseCompositeUrlProvider!
Not only that, but there were a load of interfaces that sometimes didn't match the name of the class!!!
For example,
class RootUrlProvider : ICompositeUrlProvider
Ugh! But I managed to get the new feature in... Somehow... After trying something... Throwing it away... Trying something else... Throwing it away...
😭😭😭
rant
bad design
bad code
classes
dotnet