Changelog.com - 🏠 Work from home SUPERCUT

Themeable and has a game-inspired menu system 🔥

Jaana Dogan started with a draft and this tweet and ended up laying down some serious knowledge on databases.

A large majority of computer systems have some state and are likely to depend on a storage system. My knowledge on databases accumulated over time, but along the way our design mistakes caused data loss and outages. In data-heavy systems, databases are at the core of system design goals and tradeoffs. Even though it is impossible to ignore how databases work, the problems that application developers foresee and experience will often be just the tip of the iceberg.

Phelia transforms React components into Slack messages by use of a custom React reconciler. Components (with their internal state and props) are serialized into a custom storage. When a user interacts with a posted message Phelia retrieves the component, re-hydrates it’s state and props, and performs any actions which may result in a new state.

It’s crazy interesting to me how many of these “Use React for X” projects keep popping up. People are making CLIs with React, games with React, desktop apps with React. What else?

I’ve read 2 of 6 books on this list, so I concur on those (The Design of Everyday Things and Outliers).

Students occasionally ask me for book recommendations. Since I’m always recommending the same ones, I decided to write up this list. You’ll notice that several of them are not directly about software engineering or even computer science. The students have already had plenty of exposure to the classic CS material (and will continue to in their careers), so I try to consider books that are relevant but might not be obvious.

But hey, frequent Go Time guest panelist Thorsten Ball made the list below the list with his book Writing an Interpreter in Go.

Ilija Eftimov:

For folks that do not have experience with lower level languages, understanding bytes and how to work with them can be challenging.

That’s why I wrote this article, taking a simple idea such as a Slack chat, turning the interactions (join/leave channel, send message to channel or user, etc) into a TCP protocol. Then I show the reader how they can implement the protocol in Go, by building a concurrent TCP server and learn more about bytes and working with bytes in the process.

I love it when people take things we do understand (like basic Slack interactions) and use them to teach us something we don’t understand (how to build a TCP protocol).

Written in C++ and powered by Qt 5. #notelectron

To help you succeed as a remote programmer, here at CV Compiler, we analyzed about 1,000 remote vacancies, (~330 job listings for each group), to define the tech skills employers are demanding from remote developers right now.

Frontenders oughtta know JavaScript (duh). Backenders oughtta be able to make their way around AWS.

For those searching for ways to shave a few kilobytes off of their bundles, that’s less than 1/5th of the size. This is made possible by using the browser’s native [Fetch API][fetch], which is supported in all modern browsers and polyfilled by most tools including Next.js, Create React App and Preact CLI.

Of course, you could always use Axios directly if/when you can justify the dependency.

It’s certainly interesting to ponder how to store data for as long as you possibly can, which Drew highlights very well. But I really enjoyed the questions at the end on “actually storing data forever”…

Let’s say you’ve managed to keep your data around. But will you still know how to interpret that data in the future? Is it in a file format which requires specialized software to use? Will that software still be relevant in the future? Is that software open-source, so you can update it yourself? Will it still compile and run correctly on newer operating systems and hardware? Will the storage medium still be compatible with new computers?

The New Stack with a nice rundown of what’s new/noteworthy in Node 14. The once-an-npm-package node-report is now mainlined, an experimental AsyncLocalStorage API has been added, and more.

Some of the particulars in this article don’t feel relevant during the coronavirus-lockdown phase of history, but the overarching message is solid:

Companies waste millions on building the environment they think makes developers happy, without understanding what actually makes developers tick.

What does make developers tick? What motivates us? The answers aren’t always the same, but they often aren’t all that different either. Eduards argues that autonomy, mastery, and purpose are at the heart of it.

This seems like a great option to spice up your site’s backgrounds. Only 1KB when minified/gzipped.

Find security vulnerabilities in open source npm packages while you code. Receive feedback in-line with your code, such as how many vulnerabilities a package contains that you are importing.

Inspired by Import Cost

Good news! For 2019 there were 10,975 responses to the survey — that’s almost twice as many as last year. Here are few major findings from the results, but of course, you should dig in because they make it really easy to scan and grok the details.

• The demographics of our respondents are similar to Stack Overflow’s survey respondents, which increases our confidence that these results are representative of the larger Go developer audience.
• A majority of respondents use Go every day, and this number has been trending up each year.
• Respondents are using Go to solve similar problems, particularly building API/RPC services and CLIs, regardless of the size of organization they work at.
• Most teams try to update to the latest Go release quickly; when third-party providers are late to support the current Go release, this creates an adoption blocker for developers.
• Almost everyone in the Go ecosystem is now using modules, but some confusion around package management remains.
• VS Code and GoLand have continued to see increased use; they’re now preferred by 3 out of 4 respondents.