Ryan Day

[Ryan Day @soldair]

@adam_baldwin What about water pie?

[Ryan Day @soldair]

@ag_dubs This made me feel special. Ty!

[Ryan Day @soldair]

Hey all! My team is hiring. 😃
Come work on wasm at Google https://t.co/YIttFMFzUZ

[Ryan Day @soldair]

@MylesBorins Thanks Myles! Excited for you to keep doing you. Kittens and rainbows 🐱🌈

[Ryan Day @soldair]

@caraesten I've been shopping for bay kayaking as well. Ty!

[Ryan Day @soldair]

@evenstensberg "data at rest should match the access pattern" is great advice for this problem space.

[Ryan Day @soldair]

@adam_baldwin Haha absolutely. I think it's a copepod

[Ryan Day @soldair]

Anyone know what this is? They ate all the algae in an experiment I was doing :)

[Ryan Day @soldair]

@sebmck @wesleytodd EventEmitter is a decent thing to use if you want to compose requirements as you build it. 😀

It's a node process, so your async lock is probably already any variable in scope of the emitter. And the var could be a map for your cache! Anyway. Good luck! These are fun choices.

[Ryan Day @soldair]

@sebmck @wesleytodd Decent is carrying a really heavy load of otherwise unspecified requirements there 😅

[Ryan Day @soldair]

Monday I start working on wasm at google. Nice to start a new adventure.

[Ryan Day @soldair]

@MagicznySzymek @matteocollina DI is just fancy arg passing haha. And the more automated the container the more you either depend on a build step or instantiation complexity. That complexity is harder and harder to test by nature and scales up. You need to track all the edges, the less magic it is the better.

[Ryan Day @soldair]

@MagicznySzymek @matteocollina It doesn't. just make your state instantiatable. :shrug: this is about how you feel like passing arguments to the functions in your program. You pass state in as an arg, you make objects with a factory that injects state, or you put it in the vm somewhere where you can get it.

[Ryan Day @soldair]

@matteocollina Export the state. Make your state mockable. Solve it in one spot.
Making local changes in code bases like this is usually way easier than any other form of advanced di or additional positional arguments. Nike code ;)

[Ryan Day @soldair]

@mountain_ghosts You can redirect it for everything in the whole script but that's often solving a different problem

[Ryan Day @soldair]

@JPMajor @quephird My dad worked on this. I saw it take off at the cape, and was there in viewing at cal tech when they burned it up. Always makes me smile seeing through it's lens. Ty!

[Ryan Day @soldair]

@jfhbrook Seems like the only way is to make a sh wrapper for the node binary. Once something is a process it only really knows it's path env and args. Can snoop around in /proc/pid and see. Or just use "node" if it's resolved by which