Changelog

there are a lot of AWS services available. And I do mean: a LOT. Currently, there are 163 (!) different services that are available from the Amazon Dashboard, each with their own way of working, difficulties, catches and best practises.

What follows is one-line descriptions of all 163 AWS services. MSK? Kafka as a service. Amazon Connect? AWS call center platform. And so on.

On the heels of NVIDIA’s latest announcements, Daniel and Chris explore how the new NVIDIA Ampere architecture evolves the high-performance computing (HPC) landscape for artificial intelligence. After investigating the new specifications of the NVIDIA A100 Tensor Core GPU, Chris and Daniel turn their attention to the data center with the NVIDIA DGX A100, and then finish their journey at “the edge” with the NVIDIA EGX A100 and the NVIDIA Jetson Xavier NX.

Dmitri Popov:

digiKam is the cornerstone of my photographic workflow. This powerful and versatile photo management application has all the tools and features necessary for transferring, organizing, processing, and managing photos, RAW files, and videos. But even though digiKam can handle practically any photographic task you throw at it, there is still room for optimizing and improving parts of the Linux-based photographic workflow.

Go Binaries is an on-demand binary server, allowing non-Go users to quickly install tools written in Go without installing go itself, and removing the burden of cross-compiling and uploading dozens of binaries for every command-line you write.

Matt Mullenweg:

The two main theses of my professional career have been that distributed is the future of work, and that open source is the future of technology and innovation.

On the distributed front, the future of work has been arriving quickly. This week, a wave of companies representing over $800B in market capitalization announced they’re embracing distributed work beyond what’s required by the pandemic…

Change happens slowly, then all at once.

There are few people on Earth that have been thinking about this longer (and more deeply) than Matt.

We’re bringing Brain Science backstage — Mireille puts on her interviewer hat for a deep dive into Adam’s backstory. When and how did he get involved with podcasting? How did he get in to software development? When did he get his first shot at leadership? How did he learn about sales? Why is he so curious?

Nick and Jerod welcome Dojo’s Matt Gadd to the show to catch us up on what’s changed with the framework since episode #25, what’s coming in version 7, and to defend Nick’s comment that if you like React you just might like Dojo better.

It’ll mirror user interactions across 30+ devices and give you a single element inspector so you can make and inspect changes in one fell swoop. (Built with Electron.)

Looks interesting. Would you use this?

Searches a curated subset of the web: official docs and community-driven sources. No JS, cookies, tracking, external requests or data collecting.

There’s lots of feedback from Rakhim (the creator) and commentary on Lobsters too.

This thread from Tobias Lütke (CEO of Shopify) on Twitter…talks about digital by default, a unified work experience, WFH setup, empathy, company culture, change, and silver linings.

As of today, Shopify is a digital by default company. We will keep our offices closed until 2021 so that we can rework them for this new reality. And after that, most will permanently work remotely. Office centricity is over.

Until recently, work happened in the office. We’ve always had some people remote, but they used the internet as a bridge to the office. This will reverse now. The future of the office is to act as an on-ramp to the same digital workplace that you can access from your #WFH setup.

He goes on to say…

We haven’t figured this whole thing out. There is a lot of change ahead, but that is what we’re good at. “Thrive on change” is written on our (now digital) walls for a reason.

Itamar Turner-Trauring:

Even if you job is secure now, who knows what the future holds? Especially these days, it helps to be prepared. Learn some quick techniques to help make your future job search easier: knowing more people, upgrading your skills, getting public evidence of your skills, plus fallback planning for peace of mind.

Johnny and Jon are joined by Denise to talk about her role at GitHub and what the community and safety team does to help open source project creators and contributors, GoCon Canada and the role of organizing a conference, and more.

The best satire hits close to $HOME:

As we’ve mentioned in previous blog posts, the $FAMOUS_COMPANY backend has historically been developed in $UNREMARKABLE_LANGUAGE and architected on top of $PRACTICAL_OPEN_SOURCE_FRAMEWORK. To suit our unique needs, we designed and open-sourced $AN_ENGINEER_TOOK_A_MYTHOLOGY_CLASS, a highly-available, just-in-time compiler for $UNREMARKABLE_LANGUAGE.

Pairs nicely with this tweet of ours from a few months back.

High expectations for performance in both life and work are common, but what do you do when you get stuck and you’re not able to achieve the results you desire? In this episode, Mireille and Adam talk through the different aspects of perfectionism and ways in which is can be adaptive and helpful and other ways in which it poses additional challenges. What happens when we avoid the possibility of failure as opposed to simply having high standards for our performance? How can we begin to focus on healthy striving as opposed to reaching for perfection?

Dan Norris shared nine reasons why business ideas fail. This coupled with this recent advice from Tim Ferriss on being a specialist or a generalist is golden 💰

The startup community likes to glorify failure but I don’t. Failing sucks. Failing slow sucks infinitely more. That’s why it’s OK sometimes to give up, to free you up to move onto an idea that could bring you something that the startup community doesn’t talk about near as much: actual fulfillment and success.

Here is a list of things to look out for when things might be set for failure. These are based on my failures and the failures I’ve seen around my circles (mostly self-funded online business folk).

Every 10 years there is a changing of the guard in JavaScript. I think we have just started a period of accelerated change that could in future be regarded as the Third Age of JavaScript.

This year marks five years of Rust. On the Rust blog they reflect back on all the major changes since 1.0.

Rust has changed a lot these past five years, so we wanted to reflect back on all of our contributors’ work since the stabilization of the language.

When Rust turned 1.0 you could count the number of companies that were using it in production on one hand. Today, it is being used by hundreds of tech companies with some of the largest tech companies such as Apple, Amazon, Dropbox, Facebook, Google, and Microsoft choosing to use Rust for its performance, reliability, and productivity in their projects.

A smooth hand-off of your open source project is no easy feat. To help others succeed in this arena, Paul Götze build Adoptoposs.org:

I found that, on GitHub alone, there were more than 36,000 issues asking “Is this project abandoned?”, I thought about how to tackle this problem. More than 15,000 of these were open issues. So, lots of projects need help with their maintenance.

You can get it on the App Store, but it is the author’s first foray into SwiftUI so you may be best served using it to learn as well.

Minimal CSS “frameworks” are on the rise. There are so many of them now that it’s hard to compare apples to apples. This’ll help.

This is a quick drop-in CSS switcher to allow for previewing some of the many minimal CSS-only frameworks that are available. See the demo or drop the switcher into your own page to see how different frameworks would look together with your content.

This project only includes minimal frameworks, in other words, boilerplate / classless frameworks that require no adjustment of the corresponding HTML and can be simply dropped into the project to provide a starting point for further design. No additional javascript, compiling, pre-processors, or fiddling with classes should be required for these to look good and be responsive.