Refactoring, multiple return exits and my job status

Written by

in

I learned several things today. First of all, I learned that some of old books that I thought are obvious are not so obvious. For instance, take Refactoring, on surface it looks very simple and it would imply that it is not a worthy read. NOT TRUE! This book contains a lot of practical and good information. I think that by re-reading the books every couple of years I can learn at least something new.
I thought having a one return exit in a method is a best practice. Not really. Not most of the time. Of course, if you have a method that is very long, you’re better off having a single exit. But refactor the method! But most other times, having multiple returns is not such a bad thing. In fact, it makes your method easier to see.
Over the last couple of weeks I’m losing a lot of faith in my current place. Things are not as good for me. I am not enjoying it that much. I don’t feel challenged. I would like to stick around for at least another year. But in the year, I would like to get a clear indication that I am going to become a manager. I should also start preparing my resume. I should look at any opening within IAC. It might be a good place to go. There was a good opening in NYC. It’s a possibility. I should keep my options open.