21

A Visual Studio solution that had 62 (SIXTY TWO) projects for a webpage that was like 8 user forms total was like going to a shop to buy 3 items and receiving 15 tickets for that.
PMs saying no to refactoring due to not having enough time for a months. The first task took me 2 days just by fixing cyclic dependencies among the libraries. Went home and merged all the projects to just 3, building instantly in just two hours. Fuck idiot PMs that do not know how to code, buys shit and don't listen to devs. Fuck all idiots.

Comments
  • 7
    `World.population.where(idiot: true).destroy_all`

    Rapture!
  • 2
    Dude... Same problem on my last job. Not so many pages but alot of projects. Code was shit, no time to refactor = a lot of bugs on production.

    Wasting time/money was a thing there :/

    Edit: welcome to devrant :)
  • 0
    @three333 overengineering and fucking idiot at the keyboard. The user session was fragmented in 4 places. There were the "data" projects the data DTO projects the WCF services the WCF contracts the useless WCF behaviors the MVC project the...
    And things like:
    int a = 2;
    int b = (int) Convert.ToInt32((Convert.ToInt32(a).ToString());

    That dumbass has a CS degree. I 'd wipe my ass with that title
  • 2
    OOP languages blended with mediocre paycheck devs can really bloat the project source, I’m talking about seriously mofo level of interfaces/factories/orms/unittests, that’s even before functionality scope creep over engineering..
Add Comment