"Modifying open source programs to print out debug information to understand their internals better: SO FUN." - @b0rk
Can totally relate to this and recommend. Over the past year I've had fun poking into internals of containerd and Kubernetes while keeping notes in a Google doc
@denisenepraunig Hey! Sorry for the late reply. Hope you enjoyed the talk. π I never got around finishing it. π @bbbradsmith has been releasing a lot of NES code lately. This repo comes to mind which you might find helpful: https://t.co/RYt1fgEd4S
. @kavya719 Thanks for the insightful talk on how the Golang scheduler works. ππ I love learning about the internals of tools I use. I wish there were more talks like this one. https://t.co/ABNy9dQlxs
@thocolat @nobodywasishere I went with cc65 (more specifically ca65). I used a bunch of different resources to learn including Nerdy Nights, nesdev wiki and @nesdoug2βs tutorials.
@jazzychad Hey Chad! π Nothing concrete yet. I started this Twitter account to gauge interest: @nescasts. I believe @JeffAlyanak is also working on tutorials.
@JeffAlyanak π Iβve been meaning to try Mesen but canβt get it to compile on OS X so Iβll need to use a VM. Its Lua API seems to be more flexible for the unit testing use case. π
@JeffAlyanak Hey! That sounds awesome. Iβve been meaning to do something similar. π I havenβt open sourced anything yet but I could if youβre interested. The Lua unit testing was more of an idea than a full fledged solution. Happy to share what I have though.
@ptolts @animalsiknow @pmangg Itβs been in my book shelf for the past two months. @__xuorig__ had great things to say about it. Yaβll just convinced to start reading it. π
@orta Super interesting approach!
The approach we've been taking internally is similar to Shopify's approach: https://t.co/bwzJLvrWJW
We've been toying with the idea of adding a `success: Boolean!` so that clients don't need to do `if response.errors.length > 0`.