I think he hit the brick ledge on the wall . Kind of hard to tell with all those toys in the way . <| sep |> Role playing , planning a surprise giftevent , being silly when meeting up and one person spots the other first . All of this requires context and familiarity but it could work . <| sep |> I used to play Combat Mission PBEM for a long time and have the best memories . It ' s 1 v 1 but we played a campaign mode that included more people . I think there ' s a newer version of the game , I used to play Combat Mission Beyond the Overlord back then . <| sep |> Oh lol . My bad . Yeah , in this condition , somebody will definitely be getting a good deal . <| sep |> The specific round was tequila , and it was around 100 shots <| sep |> Ah ok , so people DID actually give you feedback that seems to align with your bullet points . I didn ' t know if you were just guessing at what others thought were problems and were ' mind reading '. Or if you thought the company thought you were a whiner but you genuinely thought that you weren ' t and only wanted advice on how to ' look like ' less of a whiner . Here is my original comment . I don ' t think it 100 % applies to your situation , but maybe it does a bit , because you ' re struggling with what are good vs bad habitsI think the first step is having some compassion for yourself . Second , is separating what you feel makes a good developer from what being a good developer looks like for your current and any other employer . What you feel is a good developer can be very different then what your boss feels a good developer does . What you feel a good developer does can be very different then the choices you must make at your job i . e . a good developer would refactor this , but I don ' t have the time , and in the interest of the company I must consider this feature complete . Third is , remembering that although you may make decisions that you don ' t feel a good developer would make i . e . not refactoring in the above example , that doesn ' t make you a bad developer . Places like this sub are good for figuring out number twofiguring out what makes a good developer to YOU and figuring out how a good developer acts on the job which varies from job to job , person to person , experience to experience . I am sure lots of people will give you improvement points on each bullet . But you don ' t sound like a shitty developer , you sound like someone who is just going through and gaining the experiences that are necessarily to figure out what makes a good developer to them .