Gimbel et al's methodology and limitations are well described. The data is available. And crucially Joshua Kendall's code is available online (https://github.com/Budget-Lab-Yale/AI-Employment-Model). I wish more research was done this way.
Readit Newsbattwell commented on Evaluating the impact of AI on the labor market: Current state of affairs budgetlab.yale.edu/resear... · Posted by u/Bender
battwell commented on GenAI has limited engineer productivity impact (case study) techblog.cloudkitchens.co... · Posted by u/charlax
The impact is not terrible given active coding takes <25% of engineers time at most companies1. GenAI can't help too much with high level design work, collecting feedback, etc.
1 https://www.microsoft.com/en-us/research/wp-content/uploads/...
battwell commented on ML Infrastructure Doesn't Have to Suck techblog.citystoragesyste... · Posted by u/battwell
I didn't write this post. But I work with the guys
We've been doing data science and ml for years. After iterating on our tooling for a few years, we've finally settled on some tools that we're happy with. A lot of the wins came from spending more time data with DS teams to understand what they really wanted tbh
And ray has been great!
battwell commented on How Figma's databases team lived to tell the scale figma.com/blog/how-figmas... · Posted by u/pinser98
This is such a familiar story. Company starts with a centralized database, runs into scaling problems, then spends man-years sharding it. Just use a distributed database.
Doesn't seem a crazy way to start a company. RDS will have scaling problems but is very mature and fairly easy to use early on when you're working on your MVP
I've used CRDB early on at a startup. There was some overhead. You don't get all the nice PSQL features
Although it did save us a giant migration later on
battwell commented on Nanoscope: Method-Tracing Tool for Android ubere.ng/2rfNFeX... · Posted by u/battwell
battwell commented on Nanoscope: Method-Tracing Tool for Android ubere.ng/2rfNFeX... · Posted by u/battwell
battwell commented on Nanoscope: Method-Tracing Tool for Android ubere.ng/2rfNFeX... · Posted by u/battwell
battwell commented on Nanoscope: Method-Tracing Tool for Android ubere.ng/2rfNFeX... · Posted by u/battwell
One of the things that I would love to see would be an easy way to do a before/after accounting on some visual flourishes. "How much time does this take to do X" and check in something akin to a profile in parallel to source control. "Is this fast" is something that can be really hard to answer in retrospec and I'd love to have a tool that does something like that for Android, and it seems like nanoscope might be lightweight enough for it.
We've been building up CI tooling on top of Nanoscope. The short term goal for this is: make sure that none of our internal libraries (analytics, experimentation, etc) contribute a significant percentage of the time it takes to respond to any tap in the app. We have a lot of internal mobile libraries, so preventing perf regressions in them is a big rock.
If our CI efforts prove stable, then what you're suggesting should also be possible, if I understand it correctly.