rgoeritz

5 ms·

1. 1.▲
   by rgoeritz 4y ago

   I second the recommendation - I'm a regular listener. Over the years I learned quite a few things on the show that would translate well to my job. One example are the episodes on dos and don’ts of measuring developer productivity, whic
2. 2.▲
   by rgoeritz 6y ago

   I liked the explanation on when to use camel case vs. snake case. Also, the input on design patterns was really useful.
3. 3.▲
   by rgoeritz 7y ago

   I also prefer working for startups or smaller companies nowadays: working closely with the management team helps to understand strategic decisions first-hand. I also found people at smaller companies to be more motivated , and eager to brin
4. 4.▲
   Done Playing Microsoft’s Corporate Game(software-engineering-unlocked.com)

   4 points by rgoeritz 7y ago|2 comments
5. 5.▲
   by rgoeritz 7y ago

   I find this can be applied to conflict situations in general. Not only to code reviews.
6. 6.▲
   by rgoeritz 7y ago

   Good to know. Thanks for sharing.
7. 7.▲
   by rgoeritz 7y ago

   I think you actually don't do any coding challenges, you get to know your colleagues, find out how they collaborate on a daily basis, and experience the company's development process first-hand. Sounds pretty nice, I would say.
8. 8.▲
   How to land a remote position at Microsoft(software-engineering-unlocked.com)

   1 points by rgoeritz 7y ago|0 comments
9. 9.▲
   by rgoeritz 7y ago

   Nice read! Time-boxing my efforts using the Pomodoro technique has also made a big difference to my own productivity. I highly recommend giving it a try if you haven't done so yet.
10. 10.▲
    Code Reviews at Google are lightweight and fast(michaelagreiler.com)

    5 points by rgoeritz 7y ago|1 comments
11. 11.▲
    Don't take on Technical Debt as you'll be busy fighting Technical Inflation(michaelagreiler.com)

    8 points by rgoeritz 7y ago|0 comments