Dici ? ' Private room in Bologna ' mi suona pericolosamente come ' casa in condivisione con numero X di altri lavoratori sottopagati ' o anche peggio . <| sep |> What server ? <| sep |> How to lose on Eichenwalde 101 Kongdoo EditionStep 1 Ignore Harryhook highgroundStep 2 Defeat <| sep |> Yeah . The craziest shit in life is rarely caught on camera . There ' s not always people recording 24 <| sep |> I ran into a fence . A very sharp fence . The scar is on my face . <| sep |> Is it common that the codebase for mainstream websites contains a mixture of languages and libraries , then ? Like , if I introduced some vue . js in my next project at work , the next person that has to replace me will need to know both Knockout and vue in order to maintain the old code . Sometimes yes , though people do try and standardize on a set of acceptable frameworks and libraries to minimize the learning curve . Compartmentalization also helps if you implementconvert a bunch of related projects or segments of your code to use the same libraries and frameworks , it ' ll potentially make things easier for the new hire since they only need to care about what the specific subsectionteam they ' re a part of uses . e . g . the data analysts might all use Python , one major portion of a website might use Ruby on Rails , another major but distinct portion of the website might use Node . js , etc . In any case , based on your other comment up above , it might be a good idea to start by writing tests , instead of rewriting things . That way , once things are in a comfortable state and you do have time to start refactoring and rewriting , you ' ll have a decent suite of tests you can run to help you verify your reimplementation is relatively bugfree . I ' d also recommend that you try reading a copy of Working Effectively with Legacy Code the book has a variety of strategies and general advice that I think will be helpful in your specific case .