🔥 It's probably common knowledge that Netlify makes deployment incredibly simple- you can connect a repo, pick a build command and 🚀

or just drop a folder in and you're done!

...but here are some other things you might not know about our deploys that are very special 🧵

So, today, for the first time in 25 (!) years of Apple, I downgraded. From the 2016 MacBook Pro to my 2013, which I had kept in a drawer...

It was pretty simple to do—Apple Time Machine backups let me do it with one click.

That first tweet captures, in two pictures, how badly Apple has “lost the plot” (to quote @wylieprof). On the right is the Apple MagSafe adapter, from 2013. On the left, what I had “upgraded” to.

Thanks, Apple! I really was nostalgic for worrying about yanking my computer off the table.

Oh and I really appreciated not knowing if my computer was charging. What was great was the little whoop sound you used, so that the speaker before me could be informed I was charging my laptop.

1) Looking back on my "career" with @TheNordicWeb over the last 5 years, in retrospect it's easy for me to join up the dots and make sense of the journey:

#cphftw #sthlmtech #helyes 🇩🇰🇫🇮🇮🇸🇳🇴🇸🇪

2)

- Join & start community initiatives to meet people
- Learn from these people about how special the Nordic tech scene is
- Share this with the world through The Nordic Web
- Realise the real value is in the data, particularly in building network
- Use network to raise a fund

3) In fact, it looks all very strategic, but the reality is anything but.

My lack of vision and goals during this 5 year period was _criminal_

Any movement from one step to the next was never pre-planned and was instinctive, or worse, accidental.

4) While I am embarrassed to think of my headless chicken self, there's also part of me that thinks that none of this would have turned out where it did if I had of been deliberate and strategic about this.

5) In fact, I think my genuine love for the Nordics and the ecosystem is the MAIN reason to explain how I raised my fund & managed to move from step to step.

My story is a good example of how passion can be more powerful than strategy in the early stage of an idea/company.

Oh are we talking about Sheryl Sandberg again? Well, your reminder that disabled feminists, LGBQT feminists, and feminists of color criticised her ‘lean in’ deal from day one. Don’t let anyone retcon that out of existence.

Like, a pretty narrow slice of feminists actually endorse and support corporate feminism, they’re just white, nondisabled, straight, cis, and noisy so their voices have a bigger reach.

So if your impression is that ‘feminism’ gave her a ‘free pass’ maybe you should question your overall impression of feminism rather than continuing to centre a handful of people as ‘thought leaders’ or whatever.

Critics within feminism have been doing this work for a long time and have been getting shat on it for about as long and I'm tired of seeing them erased. But what do I know — I am, after all, not a feminist.

But I WILL say, from my not-a-feminist perspective, that people who aren’t feminists who are criticising feminism should maybe understand the movement more deeply beyond a handful of high profile celebrity feminists.

@zkat__ I'm in the position that I actually find npm / yarn the best ecosystem. Whenever I use something else I always end up stubbing my toe into something thats missing / feels wrong.

Ex. Cargo seems to neither have a concept of devDependencies nor peerDependencies.

I also can't understand why it wouldn't have an "add" command to add a new dependency. And I'm no fan of Toml, json is greate (easy to parse and build tooling around), and the better option in my opinion would be json5.

C / C++ seems to just not have language package managers. The linux / bsd crowd seem to have decided that the system package manager also should be the language package manager. Which might have been fine if every Linux distro used the same system package manager.

Instead we end up with a N x M problem. Where we have a bunch of different operating systems and they all support multiple system package managers. So there's no easy way of distributing, referencing and updating C / C++ packages.

It is also my opinion that the compiler / runtime should be a package dependency. I don't like Rust's split between rustup and cargo (they should have been one tool). Similarly it would be better if you added Node as a dependency to package.json, that way we wouldn't need NVM.