RT @rjs: “We introduced ‘Shape Up’ by Ryan Singer little over a year ago.”. I’ve been hearing this more and more lately. There’s a lot of….

Closed range peerDependencies should be impossible to publish to the npm registry without a force flag. This is such a massive waste of everyone's time.

RT @boennemann: Is there a freelance application monitoring expert to help me on a project?. Looking at a focussed 4-6 weeks project. Struc….

Is there a freelance application monitoring expert to help me on a project?. Looking at a focussed 4-6 weeks project. Structuring what we have, tooling advise, shipping something that we can confidently continue with. Berlin or remote (CEST±2).

I finally found a fiddly setting on the screen itself that allows me to turn it into a regular 16:9 screen with blacked out sides. This does not feel like a great solution, but at least it's a solution….

Is there a macOS helper or trick to deal with screen sharing on ultra-wide monitors? Zoom supports sharing just a part of the screen, but other than that this has become a real problem for pairing sessions 😬.

RT @ShitUserStory: As an. – iOS user.I want to. – use a rolling date picker that defaults to today and blocks future dates, meaning I h….

I'm starting to see a `node:` prefix for node core module imports pop up (VSCode inserts it, too), but I can't seem to find a write-up what this is about and where it's coming from. Does anyone have a pointer here? Should this be used now? Is there an ESLint rule to enforce etc?.

react-scripts with typescript causes an error on npm@7 install for months now, just because of a closed peerDependency definition ¯\_(ツ)_/¯

The funniest part is that the copy paste handling works perfectly already, no integration needed. You either select your data in the sheet, paste it in, done, or – of course – you connect your Google Account and follow 20 easy steps every single time you want to update the data.

I just connected a Google Sheet to a @Pitch deck for the first time and it turns out to be the most complicated and inflated reimplementation of ⌥ + C, ⌥ + V I have seen maybe ever. It is a one-time unidirectional import. Reimports start from 0. Marketing vs reality 🤷‍♂️🤯

It seems like there is not one day where I'm not stumbling over this:

And while we're at it @twilio & @SendGrid. Let me use my own 2FA app, or stop shoving 2FA via Authy only down my throat. Thank you.

Who came up with this idea of turning login forms into separate email and password steps? It's terrible and it has to stop, ffs (╯°□°）╯︵ ┻━┻.

Is there an npm@7 equivalent in yarn that would allow me to install all peerDependencies automatically? 🤔.

Massive TypeScript footgun. If you check for the existence of an optional enum parameter then the first value is falsey, because it's 0 under the hood. enum E {A, B}.const fn = (i?: E) => {. if (!i) alert('lol').}.fn(E.A).// alerts. That's stuff TS was supposed to prevent 🤔.

RT @SemanticRelease: 🌟 10.000 stars on @GitHub 🌟. @boennemann @gr2m @mtravi @pvdlg_.

RT @SemanticRelease: 📯 ProTip™: Use open ended ranges for "peerDependencies" in your package.json, just like you do for "engines". https://t….

RT @boennemann: @rfgamaral I would recommend to always use open ended ranges. E.g. "graphql": ">=14". Just like you would use `engines.node….

Using peerDependency ranges that exclude future versions makes them useless and annoying. Sadly nobody is listening :(