Skip to content

Instantly share code, notes, and snippets.

// Processing code by Etienne JACOB
// inspired by beesandbombs : https://twitter.com/beesandbombs/status/1563110024204787712
// motion blur template by beesandbombs
int[][] result;
float t, c;
// utils... most unused here
float c01(float x)

NFT Thoughts, Essays, Writings

I'm collecting here a few essays on the net about tokenization in the art world. This list is likely biased and by no means exhaustive.

@mattdesl
mattdesl / pinning.md
Last active January 28, 2023 19:56
hicetnunc IPFS pinning

Hicetnunc.xyz IPFS Pinning

💡 These steps will become easier, less technical, and more accessible as more open tools begin to emerge around Hicetnunc pinning. The steps below assume macOS but should work similarly across other platforms. This gist can be seen as a working draft toward more polished documentation; if you see any issues please post a comment below.

Basic Idea

Hicetnunc.xyz aims to be "decentralized" which means the OBJKTs are owned by the users, not the platform. So, in theory, if hicetnunc disappears, another marketplace could emerge on the same (user-owned) assets. But, this paradigm of decentralization means that you own the assets; so the responsibility to maintain them lies on the users, not the platform.

Of course, hicetnunc and some of its users will probably also make an effort to help maintain all the assets on its platform; but you should not rely purely on that, as it goes against the core ethos of dec

@spite
spite / WebGL NFT
Last active November 5, 2021 02:01
Base to make WebGL interactive shaders
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<title>WebGL NFT</title>
<meta
name="viewport"
content="width=device-width, user-scalable=no, minimum-scale=1.0, maximum-scale=1.0"
/>
<meta property="og:image" content="thumbnail.png" />

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.

var ui = document.querySelector("[title=Members]")
// requires the presence menu to be open (because React) but could be hidden via CSS
if ( !ui.className.match("selected") ) {
ui.dispatchEvent(new MouseEvent("click",{bubbles: true, cancellable: true}))
}
//ui.nextSibling.style.display = "none" // hides UI if you are streaming
previousMeasures = JSON.parse( localStorage.getItem('hubs-measurements') );
if (!previousMeasures) previousMeasures = []
/****************************************************************
*
* 🤹🏻‍♂️🤹🏻‍♂️🤹🏻‍♂️ Object & Entries 🤹🏻‍♂️🤹🏻‍♂️🤹🏻‍♂️
*
****************************************************************/
/**
* 1️⃣ Object.entries
*/
global.THREE = require("three");
const canvasSketch = require('canvas-sketch');
const Random = require('canvas-sketch-util/random');
const gradientHeight = 512;
const settings = {
dimensions: [ 2048, gradientHeight * 2 ]
};
@agentphantom
agentphantom / mx_complete.csv
Last active December 31, 2021 22:06
Casos Confirmados, Defunciones, Ambulatorios, Hospitalizados e Intubados por Municipio
entidad municipio confirmados defunciones activos ambulatorios ambulatorios_fallecidos hospitalizados hospitalizados_fallecidos intubados intubados_fallecidos
Aguascalientes Aguascalientes 32906 2613 722 27150 181 5756 2432 716 569
Aguascalientes Asientos 606 48 4 478 6 128 42 20 10
Aguascalientes Calvillo 1252 34 7 1107 2 145 32 18 13
Aguascalientes Cosío 149 14 0 108 0 41 14 10 7
Aguascalientes El Llano 129 22 2 85 0 44 22 14 12
Aguascalientes Jesús María 1236 86 48 1011 12 225 74 38 24
Aguascalientes No Especificado 2 0 0 2 0 0 0 0 0
Aguascalientes Pabellón de Arteaga 1081 76 6 905 5 176 71 37 29
Aguascalientes Rincón de Romos 1003 74 4 771 3 232 71 39 28
@vindarel
vindarel / common-lisp-VS-clojure.md
Last active June 25, 2024 03:56
Notes on Common Lisp VS Clojure

Testimonies

CL's compiler

The thing in CL I miss most doing Clojure as my day job? CL's compiler. I like having a compiler tell me at compile time about the mistakes I've made. Bogus arguments. Unreachable code because of unhandled exceptions, and so on. CL saves me round after round of bugs that in clojure aren't found until you run the code. If you test well, it's found when testing, if you don't it's found in production. "Clojure compiler" almost demands air quotes.

CL's optional but oh-so-useful model of type declarations is also infinitely more useful (to me) than Clojure's use of "spec", and instrumentation that happens only at test time because of the cost. Depending on the OPTIMIZE declarations, other type defs are a floor wax and dessert topping. Want checks for argument types? Lower optimizations. Want most efficient machine code? High optimizations.

/u/Decweb, March 2023 https://www.reddit.com/r/lisp/comments/11ttnxk/the_rise_fall_of_lisp_too_good_for_the_rest_of/jczpysp/