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.
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.
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.
Can you estimate how much faster your processing is now vs. before on MySQL? I find it interesting that your cluster is only 6 nodes - relatively small compared to what I've seen and from what I've read about. It'd be interesting to know the benefits of small-scale usage of big data tech.
Can I just say that I love your attitude? A borderline unhealthy sense of self deprecation and just 'doing it' because you can - qualities I wish more tech people had.
He's one of my favorite people to follow on Twitter [1] because of this; he regularly tweets about stuff he's learning, especially new languages. It's quite inspiring and uplifting to see a such a figure in the industry still make time to learn on his own and candidly share his thoughts.
Your being a big white guy visibly unaffected by soy is strictly anecdotal evidence - perhaps you aren't affected by it.
The plain reality here is that we don't yet know the full effects of a diet high in soy has on the body, so I'd err on the side of letting studies come out with something more conclusive. In any case, shouldn't we be consuming within moderation anyways?
Growing up before I knew anything about computers I always asked my parents if I could play on the home PC, which really equated to MSPaint time.
Others might have started off with tinkering with BASIC and whatnot but I think I'm fortunate enough that it turned out to be my gateway drug into computers anyways.
It's not even marketing in my mind but a public obligation. If there is anyone who would be able to provide this service, it's Twilio. Agreed, hats off.
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-...