How to write a high-engagement tweet An Article by Rach Smith rachsmith.com Pick a stance that that could be mistaken as contrarian, but in reality most people actually agree with. Posit your argument as if there are "people" who have been spreading the opposing view. You don't have to be specific about who it is. In fact, they don't actually have to exist. Make the subject matter something that people get emotional about: gender inequality in tech, TypeScript vs. JavaScript, hiring processes, etc. Watch the engagement from people agreeing with you/bonding over your common enemy roll in. Things that increase popularity that I generally don't doCoevolution and the bad take machine mediaargument
Touch the keys An Article by Rach Smith rachsmith.com In his course Being Productive: Simple Steps to Calm Focus, Kourosh Dini emphasises the importance of taking a moment to “be with” the work every day (or however frequently you need to tackle a project). “Being with” your work is to be fully present and intentional about that activity and doing nothing else. This idea was inspired by Dini’s piano teacher, who encouraged him to sit at his piano and touch the keys every day. Even on the days that he felt he had no time or inclination to practice. Sometimes touching the keys would lead to a good practice session, even when he didn’t feel like it would before he actually gave it a go. Just like Dini, I find that once I give the task my full attention and be present, the actual doing of it turns out to be much easier and more enjoyable than my mind had been expecting. As usual, the resistance to getting started is far more uncomfortable than actually doing the thing. To pick up my pen productivityworkcreativitypractice
I completely ignored the front end development scene for 6 months. It was fine An Article by Rach Smith rachsmith.com What I’ve learnt through experience is that the number of languages I’ve learned or the specific frameworks I’ve gained experience with matters very little. What actually matters is my ability to up-skill quickly and effectively. If you focus on: learning how you best learn, and practicing effectively communicating the things you've learned you can't go wrong. learningprogrammingskillexperiencepractice
I haven't experienced imposter syndrome, and maybe you haven't either An Article by Rach Smith rachsmith.com I have never felt like an “imposter”. I have always deserved to be here, I’ve worked hard. I don’t suffer from a “syndrome”. Identifying the gaps in my knowledge and being aware of what I don’t know is part of my vocation. In recent years it’s become trendy to discuss how we all apparently suffer from this imposter syndrome - an inability to internalize one's accomplishments and a persistent fear of being exposed as a “fraud”. I take two issues with this: it minimizes the impact that this experience has on people that really do suffer from it. we’re labelling what should be considered positive personality traits - humility, an acceptance that we can’t be right all the time, a desire to know more, as a “syndrome” that we need to “deal with”, “get over” or “get past”. workknowledge
Feature parity An Article martinfowler.com Whilst Feature Parity often sounds like a reasonable proposition, we have learnt the hard way that people greatly underestimate the effort required, and thus misjudge the choice between this and the other alternatives. For example even just defining the 'as is' scope can be a huge effort, especially for legacy systems that have become core to the business. Most legacy systems have 'bloated' over time, with many features unused by users (50% according to a 2014 Standish Group report) as new features have been added without the old ones being removed. Workarounds for past bugs and limitations have become 'must have' requirements for current business processes, with the way users work defined as much by the limitations of legacy as anything else. Rebuilding these features is not only waste it also represents a missed opportunity to build what is actually needed today. These systems were often defined 10 or 20 years ago within the constraints of previous generations of technology, it very rarely makes sense to replicate them 'as is'. softwarefeaturesrepair