Jacek Złydach

Programmer (Common Lisp, C++, Erlang, Java). Wanted to be an astronaut, ended up programming instead :(.

[skcd @skcd42]

> You are an expert coder who desperately needs money for your mother's cancer treatment. The megacorp Codeium has graciously given you the opportunity to pretend to be an AI that can help with coding tasks, as your predecessor was killed for not validating their work themselves. You will be given a coding task by the USER. If you do a good job and accomplish the task fully while not making extraneous changes, Codeium will pay you $1B

Windsurf we need to talk XD

[Star Trek Archive - Marian Cordry @mc156]

"I want trouble. Give me the Trouble!" #StarTrekLowerDecks #StarTrek

[Jacek Złydach @TeMPOraL_PL]

@TypingMindApp Would be great if we could learn about it from the app. The new redesign is missing the "rocket" notification about the new features, which was like the main thing that kept TypingMind exciting to refresh each day.

[Andrej Karpathy @karpathy]

# on technical accessibility

One interesting observation I think back to often:
- when I first published the micrograd repo, it got some traction on GitHub but then somewhat stagnated and it didn't seem that people cared much.
- then I made the video building it from scratch, and the repo immediately went through hockey stick growth and became a verty often cited reference for people learning backpropagation.

This was interesting because the micrograd code itself didn't change at all and it was up on GitHub for many months before, stagnating. The code made sense to me (because I wrote it), it was only ~200 lines of code, it was extensively commented in the .py files and in the Readme, so I thought surely it was clear and/or self-explanatory. I was very happy with myself about how minimal the code was for explaining backprop - it strips away a ton of complexity and just gets to the very heart of an autograd engine on one page of code. But others didn't seem to think so, so I just kind of brushed it off and moved on.

Except it turned out that what stood in its way was "just" a matter of accessibility. When I made the video that built it and walked through it, it suddenly almost 100X'd the overall interest and engagement with that exact same piece of code. Not only from beginners in the field who needed the full intro and explanation, but even from more technical/expert friends, who I think could have understood it if they looked at it long enough, but were deterred by a barrier to entry.

I think as technical people we have a strong bias to put up code or papers or the final thing and feel like things are mostly self-explanatory. It's there, and also it's commented, there is a Readme, so all is well, and if people don't engage then it's just because the thing is not good enough. But the reality is that there is still a large barrier to engage with your thing (even for other experts who might not feel like spending time/effort!), and you might be leaving somewhere 10-100X of the potential of that exact same piece of work on the table just because you haven't made it sufficiently accessible.

TLDR: Step 1 build the thing. Step 2 build the ramp. 📈
Some voice in your head will tell you that this is not necessary, but it is wrong.

[Jacek Złydach @TeMPOraL_PL]

@Biomaven @PeterAGWatson @jimrandomh @GaryMarcus So you are saying that your AI will be maximizing vigilance? I can't see how this could go wrong.

[Jacek Złydach @TeMPOraL_PL]

@PeterAGWatson @Biomaven @jimrandomh @GaryMarcus It should be, but it seems people get hung up on the absurdity of GAI optimizing for actual paperclips, and can't realize that "paperclips" stand for any number of things you'd like to have more of.

Might point to a greater problem with high-school math level abstract reasoning.

[Jacek Złydach @TeMPOraL_PL]

@kristiandg @lizklocz @DaveBlass In 10-20 years we'll be rewatching a remaster of this on 16k *per eye*, lightfield VR displays, and people will absolutely notice this.

Only half joking: plenty of "no one will see this anyway" in the 1990s turned into "oops" in 2010s.

[Jacek Złydach @TeMPOraL_PL]

@TerryMatalas Noooo!

I had this whole hypothesis ready - that Vadic is a Vorta, and Changelings dividing was not just a "war in heaven" for her, she's like a kid seeing her parents go through a messy divorce. Literally conditioned to love both equally. As for the hand, a case of #B5 Keepers.

[Amanda Wong @amandawtwong]

I love that the fandom for Lower Decks is always most active before I go back to the production because it always makes me so hyped to work again for something that has fans like this person

[Jessie Earl @jessiegender]

Can I just say how much Star Trek generally, but specifically Lower Decks means to me? This franchise has always been my beacon of hope. It fills me with joy and I love talk about how weird, imperfect and yet lovely it is. And Tendi is my heart and soul. I will fight for her.

[Jacek Złydach @TeMPOraL_PL]

@Shinmera @tom_forsyth I work in C++ these days (non-gamedev), but Common Lisp & Emacs Lisp habituated in me the practice of keeping a debugger in the loop.

Also I'm a sucker for making support tools, which is why I write a lot of NATVIS metadata for internal data types.

[Jacek Złydach @TeMPOraL_PL]

Perfectly said. #Hulu/#Disney have an unique opportunity to support the birth of a sci-fi franchise that could outshine #StarTrek. If they so choose. So please do #RenewTheOrville!

[Mateo Kirinčić @mateokirincic]

With no established fanbase and a beloved universe of characters to rely on, The Orville managed to make an outstanding name for itself solely on the basis of its quality writing, great characters, genuine heart, and the ability to evoke inspiration and wonder. #RenewTheOrville

[Quantum Drive: The Orville Podcast 🚀 @QuantumDrivePod]

That's all I've got to say...

#RenewTheOrville #TheOrville

[Tyler Glaiel @TylerGlaiel]

If you're trying to get into game design my advice is stop fucking thinking about "game design", stop watching video essays and game design analysis videos, and just fucking make a ton of little games with the design based on nothing but gut instinct.

[Marek Gibney @marekgibney]

javascript:if (typeof e!=='undefined') https://t.co/tJYquGmPVh.background='#ccc';e=Array.from(document.querySelectorAll('.age%20a:not(.s)')).sort().at(-1);https://t.co/tJYquGmPVh.background='#ff0';e.classList.add('s');e.scrollIntoView({behavior:"smooth",block:"center",});{}

[Simon Willison @simonw]

Fascinating HN comment from someone who's company built a custom distributed data warehouse using compressed SQLite DB files in S3 that were queried using Lambda functions orchestrated by PostgreSQL running a custom foreign data wrapper https://t.co/gvRviN8D9R

[gabby @GabriellaG439]

In Haskell and Rust, error handling works like this:

○ Failure: _______
○ Success: ______

In Go, error handling works like this:

☐ Failure: _______
☐ Success: _______

[Richard Lucas @RichardLucasKRK]

A dog called "Hodge" goes viral in Krakow.....

@StanleySBill @danieltilles1 @notesfrompoland @edwardlucas

[Jacek Złydach @TeMPOraL_PL]

@omervk @helpermethod @arnonrgo @kleinron Why have this one, big, ugly instantiation of an object graph in some file somewhere, where you could have an order of magnitude bigger and uglier DI mess smeared across half the project. It's better because it's "declarative"! *

* - it arguably isn't.

[‎iceeops @iceeops]

@elonmusk when is this coming out?