8

It sometimes really sucks to see how many developers, mostly even much better than me, are too lazy to implement a function to its full UX finish.

Like how can you not implement pagination if you know there's going to be fuck ton of content, how can you not allow deleting entries, how can there be no proper search of content, but instead some google custom search, how can you not implement infinite loading everywhere, but only in parts of your application, how can you not caching a rendered version or improve the page, that loads EVERY SINGLE ENTRY in your database with 11k entries, by just adding a filter and loading only chunks of it.

I know sometimes you need to cut corners, but there's rarely any excuse with modern toolsets to just write 3 lines more and have it ready for such basic things.

I sometimes just wake up during the night or before falling asleep and think "oh, what if in the future he might want to manage that, it's just another view and another function handling a resource, laravel makes that very easy anyway", write in on my list and do it in a blink the next day, if there's nothing else like a major bug.

I have such high standard of delivery for myself, that it feels so weird, how somebody can just deliver such a shitty codebase (e.g. filled with "quick/temporary implementations"), not think of the future of the application or the complete user and or admin experience.

Especially it almost hurts seeing somebody so much more versatile in so many areas than me do it, like you perfectly fine know how to cache it in redis, you probably know a fuck ton of other ways I don't even know of yet to do it, yet you decide to make it such a fucking piece of shit and call it finished.

Comments
  • 2
    Not too lazy in many cases, too busy. Why spend an extra half day making everything perfect for your single user instead of developing more features to bring in more users?

    Are you paying the developer wages?

    If they are just being lazy, then yeah, I agree.
  • 1
    @vlatkozelka @drumgimp I know when theres not enough time or budget, then you balance between vital and non vital features (we all have been there), but the examples were aiming towards the more "normal" conditions, where you do have enough time and budget to implement something, that you don't even need to handle yourself, because the framework just hands it to you already and it will e.g. improve the loadtime of the panel, which is loading 90% more than needed without it
Add Comment