I've also run into this myself in publishing my own blog posts. I had this burning need to add caveats and write very defensibly because the fear in the back of my head of being "well, actually..."d.
In the end, I still pushed them out and they made the rounds with positive feedback, but it definitely took way longer to write than I thought. I know that's probably not a very healthy way of going about it, and a big part of it in my opinion has to do with how it's too easy to issue ego-boosting corrections.
I was laid off along with most of the engineering staff at the startup I was working at in February due to lack of funding. Since I'm based in NYC and my colleagues were very well connected people, the software community immediately reached out (like sharks smelling blood in the water, but in a good way :D) and most of us landed somewhere within a month or two.
It was quite a shock the way we were all let go and it seemed to catch many of us by surprise. I've been through this kind of event twice now in my career and it sucks, but I recognize that we are still in a really great market for software jobs right now, so there's nothing for me to cry about other than getting to work with that particularly awesome team anymore.
Echoing any recommendations for 'Scala for the Impatient' - it is a fantastic beginner/intermediate book that gets you productive pretty quickly, so much so that I'm planning on having an intern who has no Scala experience go through it this summer.
I agree wholeheartedly with you, to me it's a form of humblebragging. It's definitely a nice thing to be in high demand and 'complaining' about recruiters knocking down the door seems so arrogant and unaware.
The low quality spam I can do without, but it's never anything to whine about, filter and move on if it's a problem.
I've been through a few 'crunch modes' before and while there was a general feeling of "wow, we accomplished that" afterwards. Looking back, however, I now realize how profound of a hangover it produced in me and some of my teammates, and the hard truth is that it permanently takes a toll (e.g. sluggishness, lost trust, reduced motivation) that you may never get back wherever you are, at least in my experience. The fallout, it seems, truly underscores the 'nuclear option' moniker.
It is an amazing feeling to ship a product when it should have been a failure. It is unfortunate that I worked alone and didn't have a team to share the experience with. I felt I conquered something insurmountable, yet no one saw my commitment to the company, the creativity and hard work that went into it.
Management never grasped how poorly things were handled on their end. I grew to resent the company and its leaders, and had no choice but to move on.
I think this is the most reasonable take I've read and encompasses the whole "right tool for the job" mindset that I like.
I've found that when starting a new project I get paralyzed with coming up with the perfect data model that will also scale in the future, so I'd rather punt, take the tradeoffs that come with schemaless DBs, and keep a plan to migrate to something like Postgres in the backlog. Holding on to our tools too tightly is IMO how projects get crippled.
Thank you so much for the hard work. I've been using Skeleton for a personal project even though it hadn't been updated in over 2 years. As a (mostly) backend developer, Skeleton has proven to be the best possible starting point for me to learn on; there's nothing tricky about it.
It's more akin to the "job offers" that a woman might get when walking down the wrong sort of street.
The basal level of respect for me as a professional with skills and preferences distinct from those of my peers is typically not present from the recruiter shotgunning spam all over the network.
I've found this to be a problem with reading technical books on my Kindle. I'm constantly flipping back and forth between examples and text and it's really not as good (read: not as fast) as flipping physical pages.
In the end, I still pushed them out and they made the rounds with positive feedback, but it definitely took way longer to write than I thought. I know that's probably not a very healthy way of going about it, and a big part of it in my opinion has to do with how it's too easy to issue ego-boosting corrections.
[1] http://longcao.org/2015/06/15/easing-into-functional-error-h...
[2] http://longcao.org/2015/07/09/functional-error-accumulation-...