NIH syndrome? I am guilty of it too. I love implementing things from scratch, you learn a lot by doing so and you get to own the codebase end-to-end, so no surprises and fighting around othersโ choices. It can get exhausting too though, in the end I succumb to using off-the-shelf components because my primary goals move at a higher level.
Any conversation
๐
let N=6,D0=[0,1,0,-1],D1=[1,0,-1,0],s=[],g={},d=x=y=xa=xb=ya=yb=0;
for(let n=0;n<N;n++){s=s.concat([1]).concat(s.map(x=>!x).reverse())}
for(let i=0;i<s.length;i++) {
x<xa && (xa=x);y<ya && (ya=y);x>xb && (xb=x);y>yb && (yb=y);
let t=s[i]?1:-1,e=(d+t+4)%4;
g[x]||(g[x]={});
g[x][y]=g[x][y]?"โผ":"โโโโ"[(t*(D0[d]+D0[e])>0?0:2)+(t*(D1[d]+D1[e])>0?0:1)];
x+=D0[e];y+=D1[e];d=e;
}
for(j=yb;j>=ya;j--) {
let u=""; for(i=xa;i<=xb;i++){u+=(g[i][j]||"ยท")} console.log(u);
}ยทโโโโยทยทยทยทยทยทยท
โโโโผโยทยทยทยทโโยท
โยทยทโโโโยทยทยทโโ
ยทยทยทโโผโผโยทยทยทโโ
ยทยทยทโโผโผโโโโโผโ
ยทยทยทโโผโโโผโผโโโ
ยทยทยทโโผโยทโโผโยทยท
ยทยทยทยทโโยทยทโโยทยทkรฉsztetรฉst รฉrzek, hogy valami ilyesmivel (is) foglalkozzam, a kรณdolรกshoz egyelลre nincs agyam, de majd azt is szeretnรฉk, csak scripteket, semmi komoly programnyelv, de vรฉgรผlis a JavaScript is scriptnyelv
I feel the urge to do something like this, I don't have the brains for coding yet, but I would like to, just scripts, no serious programming languages, but after all, JavaScript is also a scripting language
I subscribe to the Tony Stark school of engineering. "Sometimes you have to run before you walk." Earlier this year, I built my own static site generator. I hate literally every static site generator out there (not joking). get-taxus.org
At moms house for the holiday weekend so the kids can see Nana. She has a "premium Plex" account on her tv serving a truly massive amount of content. Allegedly the brother of a long time friend is offering the "service". She says that the service will go down when the host is having outages, so the infra is likely local.
I brought my year this weekend. We are going to dig in to this guys operation. Intuition dictates that there is some hand rolled accounting going on. I'd like to see it.
code quality is about coupling.
coupling is not a technical property of the code bytes.
code acquires its meaning in contact with the cultural environment, and coupling is about meaning.
two constants with no semantic relationship are nonetheless coupled in pragmatics if they refer to the same domain concept.
if your goal is to minimise the time integral of future work, you must understand your domain: it decides which lines will need changing.
to carve up a codebase is to carve up the world.


