You have nothing new in your closet , unless you count good will as new . <| sep |> Yeah that ' s entirely , 100 % your fault . You shorted on rent to play a video game . <| sep |> pretty standard . the brits have won the body count prize , belgium wins the award for outstanding cruelty . the rest of the colonial powers are pretty much on the same level of general asshattery . special mention to italy and portugal for stellar competence <| sep |> Seems like the problem is communication . They see it as unnecessary effort because they don ' t fully understand the value of what you ' re proposing . You may try coming up with some quantified estimations of the effects your proposed changes would create . For example Would your changes lead to faster loading times ? If so , how much faster ? How would this improve the estimated bounce rate ? Or Would BEM make it easier to maintain the code in the future ? How much easier over time ? Would you save hours of future work ? Hundreds of hours ? How much money would this save your employer in the long run ? I ' m kind of reaching for examples here but you get the idea . Put it in terms they are more likely to care about . They probably don ' t care about your feelings or frustrations . They probably care more about their bottom line . They ' ll probably come to realize that the extra stress of reorganizing the codebase is worth it if it can save them some money later on . Hope this helps !