When I was working on my small side-project library, I needed to represent a missing value. In the past, I’d used the nullable approach in simple settings and Option (aka Maybe) when I wanted more control. In this case neither felt correct so I came up with a different approach I’d like to present.
I firmly believe all creative people hate when others tell them what to do. When instead of problems to solve they are handled solutions to implement or, even worse, isolated tasks to just complete. Yet, the world is full of micromanagers. Over my career, I’ve heard countless complaints about how managers do not give their reports enough context, enough trust, enough freedom. That they decide all on their own. Why is that?
Since the very first moment I learned about TypeScript, I knew there’s always goona be this one thing I’ll hate on: Enums. So un-elegant, so old-school, and so why-do-you-polute-my-runtime. Well, I was wrong. I use Enums now. At least some of them. Let me show you.
Recently I was re-reading one of my favorite engineering articles The Trident Model of Career Development. The sentence that caught my eye this time was a note about the role of a Tech Lead: ‘They should have good but not necessarily the best tech skills in the team they are leading.’ How does this apply to an Engineering Manager?
Yes, they are dying (this is no joke answer). Sure, many open-source databases are being used and maintained every day. And, of course, any open-source software will exist and can be forked by anybody. So on the technical level, they cannot die.
This is a simple tutorial for embedding a YouTube channel into an AMP. With a small modification, this can be used for any website.
This article is a reply to Stefan Judis’s article How the rest operator and default values affect the function length property.
It looks elegant and it does get rid of the warning (which was the ‘real’ issue, right?). What is the danger here? Let me explain, a key is the only thing React uses to identify DOM elements. What…