377 karma · joined December 14, 2010
The way I excelled from beginner to a higher level engineer was self learning, curiosity, building things so I could understand them. Example: when learning dependency injection, I found a tutorial on how to build your own DI container. So i built one and saw how it worked internally. That was SUPER useful.
I recommend Podcasts, YouTube Videos, Courses, Conferences, Participating in Open Source (even writing docs that are missing is helpful). Ultimately its about using what you learn and always being curious, learning patterns, and what is useful vs what is not.
I workout with Police officers, Lawyers, Doctors, Dentists, Stay at home moms, Accountants, Students, other tech folks, etc, you name it they're all there.
There's something about "shared misery" that brings people together and builds a comrade. That turns into a community where you start to hang out with them out of the gym/etc.
This happens at any group fitness place where the same people show up at the same time to do the same thing. It's natural, organic and freeing.
I've moved across the country 3 times now and this is how I integrated into each area I moved into.
Good to see you're still around. :fist-bump:
Start there. That book changed my career. Just look at the chapter names here: https://amzn.to/2wnPHfi
Chapter 6: I dont have much time and I have to make a change
Chapter 7: It takes forever to make a change
Chapter 13: I need to make a change but don't know what tests to write
Chapter 16: I dont understand the code well enough to change it
Chapter 17: My application has no structure
Chapter 22: I need to change a monster method and I can't write tests for it
Chapter 23: How do I know that I'm not breaking anything?
All the stuff is gold. It applies to every language, every work environment and every client I've ever been at.
This is the #1 book I have my teams read.
edit: Formatting and addl chapters
So much this. Soooo much.
That said, there are other options. Look at WeWorkRemotely.com and RemoteOk.io for remote jobs. Get a good job, work remotely and have a good quality of life.
I almost went down the SF/SV route many times. Each time I ran the pros/cons and SF/SV has the worse return on life value for a family, IMO than almost anywhere. I've worked remotely for nearly 9 years and love this life. No commuting. Just my .02.
Unfortunately, due to this problem, I've been using the FB mobile website for a very long time. Every 3-6 months I'll re-install the FB Android app in hopes that things are better, only to be let down once again.
Something tells me that all this bit flipping that FB is doing is not making things better, but worse. Sure, it may be better for the FB app, but worse for the device general. This is just my speculation at this point though ...
Not to mention GitHub has had more than its fair share of outages.
The solution was to rename the package name using a tool called jarjar (https://code.google.com/p/jarjar/) and then things would work just fine. Was kind of a pain to maintain this library in sync with the updates of GSON, but eventually we were able to abandon support for these devices once the company felt the impact was low based upon the stats in the Android Platform Versions - http://developer.android.com/about/dashboards/index.html
Android, always keeping us on our toes. :)
Remember that next time you get a diagnosis. "Doctors practice medicine."