Changelog.com - Creating GitLab’s remote playbook

Kev Quirk shares his thoughts on dark mode and links to various research on the science behind it.

I’ve decided to stop using dark mode across all of my devices, because research suggests that going to the dark side ain’t all that. … But after doing some research on dark vs light, I’ve made the decision to stop using dark mode everywhere. Here’s why…

Build your own using these as a reference or simply pull them as-is from Docker Hub and docker run

Lightweight, no vendor/framework lock-in, and easy on the eyes. 🤩

From Kabir Nazir on the AltCampus blog:

One of the things a lot of newbie developers overlook often is the format of their commit messages. Properly formatted commit messages can do so much more than just looking neat…

Use the imperative mood(present tense) when framing messages … Think of each commit in your code as a change that is being applied to your codebase.

I would like to show some examples of this philosophy in action – of how one can use different unix tools together to accomplish something powerful.

This post takes you step-by-step through printing a leaderboard of authors based on number of commits to a git repo, browsing memes on reddit, setting your desktop wallpaper, and getting a random movie from an IMDB list.

I use EXPLAIN ANALYZE infrequently enough that the time I spend squinting at the results and then searching for help interpreting them often outweighs the benefit of the query altogether. Not anymore, baby! This nifty tool increases the readability of EXPLAIN ANALYZE by 1000%. And that’s science!

With VimWiki, you can organize notes and ideas, manage to-do lists, write documentation, maintain a diary, and more. Everything is exportable to HTML.

This is a sweet CSS Grid example of a responsive newspaper themed layout! Also an example of spending too much time on Codepens despite advice with no plans to stop 😂

From the anonymous writers at Stay SaaSy…

Picking your tech stack in an early stage startup is one of the most important decisions you’ll make. Read on to hear about rules of thumb for making these critical decisions.

Rule 1: When It’s Really Early, Just Use What You Know

If you’re still in prototype, less than 4 developers, do-or-die mode, just use what you know. Unless your product has deep technical requirements the only thing you should optimize for is how fast you personally can code. Don’t try something new. Don’t experiment. Write code.

A unique take on explaining Cross-Site Request Forgery (CSRF).

You’re a responsible, hardworking person. You’ve saved up your money over the years at Definitely Secure Bank®. You love Definitely Secure Bank - they’ve always been good to you, plus they make it easy to transfer money via their website. Sweet, right?

You can probably guess where this is headed…

This is a pretty awesome visual timeline of the 25 year history of PHP from JetBrains.

With the combined goal of gaining a deep understanding of DNS, of doing something interesting with Rust, and of scratching some of my own itches, I originally set out to implement my own DNS server. This document is not a truthful chronicle of that journey, but rather an idealized version of it, without all the detours I ended up taking. We’ll gradually implement a full DNS server, starting from first principles.

5 Chapters short.

Daniela Borges Matos de Carvalho:

In this blog post I explain the path I took to fix most accessibility issues on my personal website. It is interesting to understand how everyone can fix most issues with the tools we have in hands. Specially in the COVID-19 situation we’re facing there is no reason to leave people behind.

For years now I’ve been asking AI/ML experts when these powerful-yet-complicated tools will become available to average developers like you and me. It’s happening! Just look at how high-level this text generation code sample is:

import openai
prompt = """snipped for brevity's sake"""
response = openai.Completion.create(model="davinci",
  prompt=prompt, 
  stop="\n",
  temperature=0.9,
  max_tokens=100)

They’re oftening all kinds of language tasks: semantic search, summarization, sentiment analysis, content generation, translation, and more. The API is still in beta and there’s a waitlist, but this is exciting news, nonetheless.

According to the “why does this exist” section of the readme:

Microsoft’s downloads of Visual Studio Code are licensed under this not-FLOSS license and contain telemetry/tracking. According to this comment from a Visual Studio Code maintainer:

When we [Microsoft] build Visual Studio Code, we do exactly this. We clone the vscode repository, we lay down a customized product.json that has Microsoft specific functionality (telemetry, gallery, logo, etc.), and then produce a build that we release under our license.

When you clone and build from the vscode repo, none of these endpoints are configured in the default product.json. Therefore, you generate a “clean” build, without the Microsoft customizations, which is by default licensed under the MIT license.

This repo exists so that you don’t have to download+build from source. The build scripts in this repo clone Microsoft’s vscode repo, run the build commands, and upload the resulting binaries to GitHub releases. These binaries are licensed under the MIT license. Telemetry is disabled.

The Visual Studio Code license referenced is a short read. You should read it if you use VS Code.