Ryan Magoon
6.9K posts
Ryan Magoon
@ryanmagoon
shipping paypal credit and other things
Raleigh, NC Katılım Ocak 2012
5.2K Takip Edilen1.8K Takipçiler
We solved the network interception in Node.js. All tests green. Many new tests added, all green. Working on getting the ecosystem packages green, too. Exciting times.
English
can confirm - 5.6 sol is great at fixing React useEffect slop too!
prompt: "Run npx react-doctor@latest, triage each issue and create a central draft PR, then stack verified fixes onto that PR"
gabriel@gabriel1
i put 5.6 ultra on "desloppofy my codebase and ruthlessly remove any complexity that is not required, and try every feature end to end with @ computer" been working all night and is still working
English
@59thProfile @andrewqu over time, like the first 7 are always accurate?
English
@andrewqu That is true but CS has deterministic non-random bullet spray pattern vs something like CoD which has random bloom
English
@ryanmagoon fps games ~usually have too much bloom (which does contribute to a specific skill, but is ultimately luck)
English
Ryan Magoon retweetledi
Ryan Magoon retweetledi
my single biggest piece of advice when choosing OSS tech is this:
make sure you and the authors have aligned incentives
e.g. if you're a SaaS platform looking at a web framework built by a consultancy that sells courses, consider you have different outcomes in mind
Ben Vinegar@bentlegen
A short story about deferring tech choices to thought leaders: Early days at Disqus (~2010-2012), we made several frontend choices based largely on what thought leaders were promoting at the time. One example: there was a big movement toward "micro-frameworks." Instead of larger, well-tested libraries like jQuery, you'd stitch together tiny interoperable micro libraries (Ender.js was one). Disqus was an embeddable JavaScript app, so file size mattered. It fit our use case, so we went with it. Then it went live, and we were serving millions of users. The reality of those choices became clear. Micro libraries meant that instead of one good semi-bloated library, you ran 6-7 smaller, less-tested, crappier ones. We burned a ton of cycles fixing bugs and covering corner cases when we could've been shipping product. We made a few choices like this. At conferences, I'd track down those same thought leaders and ask for advice. "I'm hitting problem X, Y, Z. How did you solve this?" That's when I learned my lesson: they rarely had answers, because they'd never reached our scale. Their energy went into promoting new stuff, not running it. You should know this has never stopped. It's happening right now with AI. It'll happen again with whatever comes next. Do your own homework. Test a lot. Don't just go with what somebody tells you.
English
mise will hit 30k stars tonight. Thanks everyone for using it, sending feedback and PRs over the past 3.5 years. At this point there's no question it's the most impactful work I've done in my career.
github.com/jdx/mise
English
Ryan Magoon retweetledi
This topic is so dumb and I’m sorry to participate in it.
Hire competent people. Let go of underperformers. You will be left with people who thrive in your environment. Repeat.
Harry Stebbings@HarryStebbings
Why Remote Work is White Collar Fraud. "I have a three-year-old and a five-year-old. The idea that I could do any work at my house is like a total fantasy. The kids come home at 3pm, your work day needs to keep going. I'm highly against it." @typesfast
English
@tbpn @PalmerLuckey @modretro @PalmerLuckey I just want a 4:3 high refresh rate OLED I can run CRT shaders on
English
"I flirt with the idea that smart TVs should be illegal. I hate them so much." - @PalmerLuckey
Instead of building a TV, manufacturers feel like they need to be a services company, an app store, etc.
"I wouldn't be surprised to see @modretro make a modern technology display."
From his appearance on the show in October.
English
@Pragmatic_Eng @no_erez It absolutely matters. The less iterations you can get in a certain time window, the less polished/refined the product will be, so that matters as much for agents as it did for high performing non-AI enabled teams. It also affects the ability to continuously dogfood the product.
English
Does CI/CD pipeline speed matter with AI? Rob Erez(@no_erez), principal engineer at Octopus Deploy, on why thoroughness outweighs speed when agents are babysitting the build:
“One of the things you often talk about when there's a human element to the pipeline is speeding up the cycle to get that feedback quicker.
If you've got engineers sitting there waiting for their code to run tests, they can get back to it and fix it. The shorter and shorter you can make that feedback loop the better it becomes because they don't need to context switch, et cetera.
I think in a world where the majority of your code is being developed by AI, that becomes perhaps less important.
If you can kick out your build and test process and it takes 30 minutes versus 20 minutes, does it really matter if the engineer's already long gone, moved on to the next problem and the actual AI agent themselves itself can kind of babysit the process and review the problem that came up and issue a new fix?
So I think there'll be a de-emphasis on some of the speed of the pipeline itself and more on increasing or decreasing risk, the risk that comes from having AI agents generate code."
English
@GeringerAdam @VicVijayakumar I’m in palladium plaza on back of red hat
English
@GeringerAdam @VicVijayakumar Yeah I bike out of downtown all over the place. I am newer to road bikes but I have decent fitness from running
English
Ryan Magoon retweetledi
@file_mutex people who dont read the code are not serious people
and it takes a serious person to ship production software
English
Ryan Magoon retweetledi
Instead of waiting for a new model to fix your problems
Why not just fix your problems
English