getify

An Open Letter To Assholes Who Hire People

About a month ago I tweeted out some frustrations about an interview process I had gone through.

Recently interviewed with a major (global) tech company. They absolutely knew me and my background. Still tried to have me run thru multiple rounds of tech interviews.

..thread..

getify

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.

getify

Download Icon: https://jumpshare.com/v/T5yuKIP3Zc6Rr29GH5ye

How To Use

1. While focused on an open window (like a browser or editor), hit the "record" hotkey (default: win+ctrl+shift+?) to add an app to the focus cycle list. Tooltips will pop up notifying you of recorded apps, or if there's an issue recording.

2. To cycle forward through recorded apps, use the "cycle forward" hotkey (default: win+ctrl+shift+>), or click the system-tray icon, or click the menu Item "Cycle Apps" menu item.

3. To cycle backward, use the "cycle backward" hotkey (default: win+ctrl+shift+<).

getify

Monads and Friends...

Over the last 24-48 hours, I've fielded quite a flurry of tweets related to a couple of threads I posted recently. Upon reflection on the feedback, especially the negative stuff, I decided to write this blog post to clarify a few things about my background on the topic, what I was trying to say, what I've done so far, and what I'm hoping to do (and learn!) in the future.

It's a bit of a lengthy read, but if you find you've got the time, I hope you'll read it.

To be clear, the feedback has been on a broad spectrum. A lot of it was actually quite positive, people thanking me and appreciating my continued efforts to try to make dev topics approachable. As a matter of fact, over the years, I've received boat loads of such positive feedback, and I'm tremendously grateful that I've had a helpful impact on so many lives.

But some of it veered decidedly the other direction. I'm deliberately not linking to it, because I don't want to either amplify or gang up on those folks. I'm offended an

getify

async function main() {
   var btn = document.getElementById("my-button");
  
   // eventStream here is a native JS async iterator
   var eventStream = onEvent(btn)("click");
  
   // this is the key thing: we can use a `for-await..of` loop
   // to consume the async-iterator
   for await (let evt of eventStream) {
      console.log("click!");

getify

// setup all the utilities to be used

var delay = (ms,cancel = new AbortController()) => {
  var pr = new Promise(res => {
    var intv = setTimeout(res,ms);
    cancel.signal.addEventListener("abort",() => { clearTimeout(intv); res(); });
  });
  pr.abort = () => cancel.abort();
  return pr;
};

getify

#include VA.ahk

SwitchMicDevice(micName) {
    return VA_SetDefaultEndpoint(micName,1)
}

GetMicDeviceID(micName) {
    Loop
    {
        deviceIDPtr := GetMicDevice(A_Index)

getify

Keybase proof

I hereby claim:

• I am getify on github.
• I am getify (https://keybase.io/getify) on keybase.
• I have a public key ASCMGyYZgzXV7OoA4Aw_DzSwADaqpyFN2enUhGeeAbxaZgo

To claim this, I am signing this object:

getify

function SomeCounter() {
    const [ counter, updateCounter ] = useState(0);
    
    useEffect(function listening(){
        const btn = document.getElementById("increment-counter-btn");
        btn.addEventListener("click",onClick);
    },[]);
    
    useEffect(function logger(){
        // this logger() is updated each time `counter` changes, so

getify

btn.addEventListener("send-btn",onSend);
send = CAF(send);
var prevSend = Promise.resolve();

function onSend(evt) {
   prevSend.finally(function f(){
     prevSend = send(
       CAF.timeout(1000,"send took too long."),
       { some: "data" }
     )