Noxville

[00:25:11.086] npc_dota_hero_legion_commander uses item_armlet
[00:25:20.117] npc_dota_hero_legion_commander uses item_armlet
[00:25:25.449] npc_dota_hero_legion_commander uses item_armlet
[00:25:32.414] npc_dota_hero_legion_commander uses item_armlet
[00:25:37.246] npc_dota_hero_legion_commander uses item_armlet
[00:25:42.978] npc_dota_hero_legion_commander uses item_armlet
[00:25:51.842] npc_dota_hero_legion_commander uses item_armlet
[00:25:55.675] npc_dota_hero_legion_commander uses item_armlet
[00:26:04.139] npc_dota_hero_legion_commander uses item_armlet
[00:26:11.237] npc_dota_hero_legion_commander uses item_armlet

fzaninotto

I have migrated about 11 kloc from material-ui 0.X to material ui 1.0 (a moderate size project). It has taken me more than 20 hours, and it was not a pleasant experience. cf https://github.com/marmelab/admin-on-rest/pull/1167

No Migration Path

I understand that you took the opportunity of a major BC break to rethink the API completely. But coming from 0.X, the changes often aren't consistent. Each component has changed in a different way, and for a given component, there is no way to guess the 1.0 API based on the 0.x API. Why did <ToolbarGroup> disappear? Why do I need to decompose a ListItem into so many sub components now? Why was Toggle renamed to Switch?

auzwang

Localz Driver Tracker

Localz is building a platform to track driver locations as they deliver parcels.

A driver logs into their device and begins submitting location. This location will be used for the customer to track the driver on a map.

Requirements

Please conform to the requirements below, we do not expect you to go beyond these. This is a server-side challenge.

threepointone

import tree from "./tree";

test("it should serialise the tree", () => {
  expect(tree("path/to/folder")).toMatchInlineSnapshot(); // jest will fill this in automatically
});

threepointone

(This is a draft for something I'm writing internally but figured it would be useful for everyone.)

tl;dr -

• make sure git --version returns 2.27.0 or higher.
• git clone --filter=blob:none --sparse <repo> --depth=1
• cd <repo>
• git sparse-checkout set <path> <path> <...path>

---

gatsbyjs-employees

To the Gatsby Community,

We want to start by specifically thanking Nat Alison. We support her and commend her bravery in speaking out. It is not easy to stand alone. What she experienced at Gatsby was unacceptable and speaks to wider issues. We thank her for putting pressure on the company to fix them. We vow to double down on those efforts.

While we have worked hard to give feedback and help create a healthy work environment over the past few years, change has been far too slow and the consequences have been real. The previous weeks have intensified the need for rapid change by increasing employee communication and allowing us to collectively connect some dots. We are just as outraged. As a result, we have posed a series of hard questions to management as well as a list of concrete actions they need to take.

Kyle Mathews' public apologies to both Nat Alison and Kim Crayton are small actions swiftly taken that signal the possibility for change but don't speak to the systemic issues that must be addressed.

lunasorcery

killall "⠀⠀⠀⠀⠀⠀⠀⢠⢦⡀⠀⡰⣩⠃⠀⠀⠀⠀⠀⠀⠀⠀⠀"
killall "⠀⠀⠀⠀⠀⠀⠀⠘⣄⠙⠍⠁⠙⠦⡀⠀⠀⠀⠀⠀⠀⠀⠀"
killall "⠀⠀⠀⠀⠀⠀⠀⠀⡎⠀⠀⡠⠄⠔⠊⠉⠒⠒⠒⢄⠀⠀⠀"
killall "⠀⠀⠀⠀⠀⠀⠀⢀⠇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢈⠆⠀⠀"
killall "⠀⠀⢠⢤⠜⡆⠀⢸⠀⠰⣄⠀⠀⠀⠀⠀⠀⠀⣠⠎⠀⠀⠀"
killall "⠀⠀⠱⠤⡁⠈⠑⠇⠀⠀⠀⠉⠒⠤⠤⠄⢖⠊⠀⡐⠧⣄⣀"
killall "⠀⠀⠀⠀⠘⢆⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠹⡉⠀⣀⣨⡷"
killall "⠀⠀⠀⠀⠀⠈⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢱⠜⠁⠀⠀"
killall "⠀⠀⠀⠀⠀⠀⢇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠸⣸⠱⡀⠀"
killall "⠀⠀⠀⠀⠀⠀⠸⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠸⠁⠀⣣⠀"

threepointone

(I'm enjoying doing these raw, barely edited writeups; I hope they're useful to you too)

Feature flags

This is my own writeup on feature flags; for a deep dive I'd recommend something like Martin Fowler's article (https://martinfowler.com/articles/feature-toggles.html).

So. Feature flags. The basic idea that you'll store configuration/values on a database/service somewhere, and by changing those values, you can change the user experience/features for a user on the fly.

Let's say that you're building a new feature, called 'new-button' which changes the color of buttons, which is currently red, to blue. Then you'd change code that looks like this -

soatok

<?php
/**
 * Usage: Run this from the command line to generate a secure passphrase in the format
 * of stereotypical bottom keymashing.
 *
 * php bottom-responder.php | xclip
 *
 * Why? Because furries ruin everything, including bottom jokes.
 */
function random_str(int $length, string $charset): string {

gaearon

const express = require('express');
const app = express();

// Application
app.get('/', function(req, res) {
  if (process.env.NODE_ENV === 'development') {
    for (var key in require.cache) {
      delete require.cache[key];
    }      
  }