Kyle Simpson getify

## what-hiring-should-look-like.md

      
              1 file
            
          
              28 forks
            
          
                22 comments
              
            
              239 stars
            
          
                getify
                / what-hiring-should-look-like.md
            
            
              Created
              August 14, 2020 21:01
            
          
    What Hiring Should Look Like

This is definitely not the first time I've written about this topic, but I haven't written formally about it in quite awhile. So I want to revisit why I think technical-position interviewing is so poorly designed, and lay out what I think would be a better process.
I'm just one guy, with a bunch of strong opinions and a bunch of flaws. So take these suggestions with a grain of salt. I'm sure there's a lot of talented, passionate folks with other thoughts, and some are probably a lot more interesting and useful than my own.
But at the same time, I hope you'll set aside the assumptions and status quo of how interviewing is always done. Just because you were hired a certain way, and even if you liked it, doesn't mean that it's a good interview process to repeat.
If you're happy with the way technical interviewing currently works at your company, fine. Just stop, don't read any further. I'm not going to spend any effort trying to convince you otherwise.

  
## todoovy-preview-1.js
// ..

const nextTodoID = State(state => {
	var todoCounter = (state.todoCounter ?? 0) + 1;
	return {
		value: todoCounter,
		state: {
			...state,
			todoCounter
		}

## 1.js
let {
	name: USER_NAME,
	displayName: USER_DISPLAY_NAME,
	id: USER_ID,
	regChallenge: USER_REG_CHALLENGE
} = await (
	fetch("/api/register-passkey",{
		// ..
	})
	.then(resp => resp.json())

## 1.md

      
              1 file
            
          
              0 forks
            
          
                4 comments
              
            
              50 stars
            
          
                getify
                / 1.md
            
            
              Last active
              September 2, 2025 12:49
            
              
                In defense of using blocks to create localized scope for variables... (part 1 of 2)
              
          
    In defense of blocks for local scopes (Part 1)


[EDIT: I've added a part 2 to this blog post, to address some of the feedback that has come up: https://gist.github.com/getify/706e5e10822a298375da40f9cc1fa295]

Recently, this article on "The JavaScript Block Statement" came out, and it received some good discussion in a reddit thread. But the general reaction seems to be against this approach. That saddens me.

  
## 1-setup.js
// Adapted from: https://www.geeksforgeeks.org/find-length-largest-region-boolean-matrix/

"use strict";

var M1 = [
	[ 0, 0, 1, 1, 0 ],
	[ 1, 0, 1, 1, 0 ],
	[ 0, 1, 0, 0, 0 ],
	[ 0, 0, 0, 1, 1 ]
];

## 1.html
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=0">
<title>Test Page</title>

<script>
// early compute the vw/vh units more reliably than CSS does itself
computeViewportDimensions();

## 1-post.md

      
              5 files
            
          
              2 forks
            
          
                1 comment
              
            
              16 stars
            
          
                getify
                / 1-post.md
            
            
              Last active
              February 22, 2025 17:10
            
              
                Comparing: array method chaining, generator delegations, and transducing
              
          
    Comparing: array method chaining, generator delegations, and transducing

I'm writing this quick post to respond to a recent twitter conversation where claims were made about the merits (or lack thereof) of transducers, as they relate to composing list comprehensions (map, filter).
For comparison sake throughout the rest of my post, below you'll find three (actually four!) implementations of a simple list operation demo:

Array Method Chaining (jump to analysis)

Alternate: Array Method Composition (jump to analysis)


Generator/Iterator Delegations (jump to analysis)
Transducing (jump to analysis)


## 01.js
var mockData = getMockData(); // mock API response data
var movieIDs = [ 627, 699, 378, 92, 933, 725, 528, 3, 156, ];

var movieListings = [];

for (let movieID of movieIDs) {
	if (validMovie(movieID)) {
		let movieData = lookupMovie(movieID);
		if (recentMovie(movieData)) {
			movieListings.push(

## 1.md

      
              1 file
            
          
              0 forks
            
          
                0 comments
              
            
              0 stars
            
          
                getify
                / 1.md
            
            
              Created
              December 26, 2024 17:14
            
              
                an AI-assisted explanation of what an LLM is and how it works, for either non-technical folks, or those with basic technological (but not engineering) proficiency.
              
          
    How an AI Language Model Predicts Words

Think of a language model as working kind of like a giant database with an index—but let’s start with what a database index is first.

Step 1: What’s a Database Index?

Imagine you’re reading a long book, and as you go, you use post-it notes to mark important words or ideas—like “apple,” “recipe,” or “Paris.”

  
## 1.js
var filterReducer = pf => cf => (acc,v) => pf(v) ? cf(acc,v) : acc;
var mapReducer = mf => cf => (acc,v) => cf(acc,mf(v));
var compose = (...fs) => v => fs.reduceRight((r,f) => f(r),v);
var concat = (acc,v) => [ ...acc, v ];
var sum = (x,y) => x + y;

// ************************************

var onlyOdds = v => v % 2 == 1;
var double = v => v * 2;
	// ..

	const nextTodoID = State(state => {
	var todoCounter = (state.todoCounter ?? 0) + 1;
	return {
	value: todoCounter,
	state: {
	...state,
	todoCounter
	}
	let {
	name: USER_NAME,
	displayName: USER_DISPLAY_NAME,
	id: USER_ID,
	regChallenge: USER_REG_CHALLENGE
	} = await (
	fetch("/api/register-passkey",{
	// ..
	})
	.then(resp => resp.json())
	// Adapted from: https://www.geeksforgeeks.org/find-length-largest-region-boolean-matrix/

	"use strict";

	var M1 = [
	[ 0, 0, 1, 1, 0 ],
	[ 1, 0, 1, 1, 0 ],
	[ 0, 1, 0, 0, 0 ],
	[ 0, 0, 0, 1, 1 ]
	];
	<!DOCTYPE html>
	<html>
	<head>
	<meta charset="utf-8">
	<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=0">
	<title>Test Page</title>

	<script>
	// early compute the vw/vh units more reliably than CSS does itself
	computeViewportDimensions();
	var mockData = getMockData(); // mock API response data
	var movieIDs = [ 627, 699, 378, 92, 933, 725, 528, 3, 156, ];

	var movieListings = [];

	for (let movieID of movieIDs) {
	if (validMovie(movieID)) {
	let movieData = lookupMovie(movieID);
	if (recentMovie(movieData)) {
	movieListings.push(
	var filterReducer = pf => cf => (acc,v) => pf(v) ? cf(acc,v) : acc;
	var mapReducer = mf => cf => (acc,v) => cf(acc,mf(v));
	var compose = (...fs) => v => fs.reduceRight((r,f) => f(r),v);
	var concat = (acc,v) => [ ...acc, v ];
	var sum = (x,y) => x + y;

	// ************************************

	var onlyOdds = v => v % 2 == 1;
	var double = v => v * 2;