Unlike many tutorials today, this one will focus on minimizing the technical requirements to follow along. We will get up and running with TypeScript without opening a terminal, installing dependencies, or even initializing an NPM project. In the advanced portion we will need to do a bit of that, but for most users, all you will need is Visual Studio Code as your editor. Link Get Started With TypeScript the Easy Way ...
Everyone loves types, Everyone loves autocompletion, Everyone loves getting warnings before they arise. But nobody likes wasting time compiling stuff. Hopefully this will help convince you or your company that you don’t actually need the TypeScript flavor syntax. So i have embedded the same editor used in VS-code to show you that you can have type safety with vanilla JavaScript and have the best of both worlds and play around with it. ...
This keynote presents my (and many other’s) thinking about #NoEstimates. It argues that estimation is a bad thing, particularly in the Agile world, and presents ways to plan that don’t involve estimation. Link: #NoEstimates
The rule “Everyone sweeps the floor” always resonated with me. This was very much the behaviour and expectations of the person that ran the unit that I worked in some years ago at Apple. At the time, I was unaware that the badge sticker existed. My boss did mention that they appreciated me always “sweeping the floor” … both in the codebases I worked in, but also emptying the dishwasher. ...
I thought this was a really interesting examination of the performance penalties of using ({...spread}) in JavaScript. Link: The reduce ({…spread}) anti-pattern
I firmly believe that writing a good git history, or narrative is important and worthwhile. Future Developer will thanks us when they’re using git log -S to find a particular line or fragment, or when they’re using git bisect to figure out when and how a particular defect was introduced. In the past I’ve given a talk about crafting a lovely git narrative. Thankfully, there’s no recording of that talk. ...
I can’t remember where I saw this first, as I configured it awhile ago. Emmanouil Liakos shares a quick tip about how to use git pull --rebase and to configure your git to do this automagically. Link: Don’t git pull, use git pull –rebase instead
2020 has taken the concept of “new normal” and given it a whole new lease of life. It’s a word that’s been thrown around so often but it’s true – it’s permeated every aspect of our lives. Our once loud and proud office culture has been replaced with remote work; the ultimate “new normal” for businesses around the world. We’ve had to juggle family life and childcare with our usual working routines, shifting from video calls to email on a near-constant basis to stay “updated”. ...
Language is one of the most powerful tools we have as humans. It binds us. Instructs us. When used well, it creates a common understanding. And it’s essential for creating an environment where everyone feels welcome and included. Historically, language has left many out. Individuals and groups have been marginalized and discriminated against because of their culture, race and ethnicity, gender, sexual orientation, age, disability, socioeconomic status, appearance and more. ...
The Rules (according to Graham) Don’t use @here unless it is truly relevant to everyone in a channel Don’t use @channel unless there is a fire or a nuclear explosion that everyone needs to be aware of now Use targeted Slack group mentions for getting a hold of stakeholders in a channel (i.e. @support_ in the #support channel) Use Slack as an asynchronous medium, not a synchronous one (assume people will not respond immediately, rather than the opposite) Link: Why you shouldn’t use @here on Slack ...