And you are here why?

Many many   many   years ago - during the DotCom era - I was at a company that unicorn-ed overnight. Mind you, before the craziness, we were a   tiny  company, a handful of people at that. But then - DotCom bubble, websites, and   BOOM! , we were growing like mad. It was pretty awesome, I have to tell ya 🤗 At the time, I was young, full of beans, and pretty certain that the world revolved around me. And the hyper-growth certainly only served to accentuate this - after all, it was obvious that I had something to do with all of our success, right? Somewhere along the way, we brought in a couple of people who were, well, capable of doing what I was doing. And, what’s worse, they had been doing it for a lot longer, and at a much larger scale, than I was. Thing is, I  knew  that I was better, stronger, faster than them, I just needed some way of showing everybody that I was all that and a bag of chips. And I needed to do it  right damn now  becau...

Think about your mentors, and any mentees that you might have had. There are many many reasons why the relationship might be (or have been) effective, but one common denominator is that, in the effective ones,  both sides gained from the relationship . But first, a digression. Think about your relationship with your loved ones — especially friends that you’ve had for a long long time. Y’all are different people than when you met — you’ve grown, changed, and moved on from those salad days. Many experiences large and small have shaped you into the person you are, and even more will shape you into the person you will be. And the same applies to your friends too! It is this personal evolution that has made the relationship last this long — the experiences that each of you have been through creates new vistas to explore, new fields to experience, and new things to learn. To be an effective mentor, you need to find our what  you  can learn from, or about, your mentees....

From the   AWS S3 documentation , about adding randomness to key-names to avoid “hot-partition” / sharding issues. If you anticipate that your workload will consistently exceed 100 requests per second, you should avoid sequential key names. If you must use sequential numbers or date and time patterns in key names, add a random prefix to the key name. The randomness of the prefix more evenly distributes key names across multiple index partitions. An oldie but goodie, this one is. I’ve been bit by it, on average, about once a year or so.   Shopify got nailed recently too , and a quick Google search reveals that there is a fairly constant stream of people running into this. It’s not just an S3 thing, it’s there in   the docs for Google Cloud Storage   too… The issue at hand is, that is the the type of thing that • you experience rarely,   but • when you   do   experience it,   it hurts ,   but • it’s not the kind of thing that you walk a...

Andy Budd has a long post up about the similarity between character classes in Dungeons & Dragons and roles in web-development. To summarize the thing, he draws analogies as Fighters =:= Developers Thieves =:= Front end developers Illusionists =:= Designers Clerics =:= Project Managers Rangers =:= UX Designers I'm really short-changing the article.  Seriously, go read it .  But, in the meantime, there were was one section in particular which caught my eye  Characters in Dungeons & Dragons progress by gaining experience points which relate to the complexity of the quests they undertake and the level of the foes they defeat. If they do something themselves all that learning goes to them. However if they are part of a team the experience is typically distributed amongst everybody. So the more quests you undertake, and the bigger those quests are, the more you’ll progress in your careers. If you play infrequently and only accept easy challenges it can...