mattefay.com
👨🔧 Passionate engineer
🦒 Animal advocate
🧬 Scaling bio at Prolific Machines
Nerd-jock hobbies:🏅📊 sports statistics, 📷 photography, 🫘 beans, 🚴♂️ cycling
🌎: Oakland, CA
🔗: mattefay.com
37 posts
140 followers
100 following
Regular Contributor
Active Commenter
comment in response to
post
Looks rad, I'd love one just like any red-blooded American contributing to the radical Biden biomanufacturing agenda
comment in response to
post
@hankgreen.bsky.social I think this would make for a great explainer video
comment in response to
post
4) They walk back the policy, and everyone thinks they beat the insurance companies, when in reality we were conscripted in the ASA's fight with them to continue getting paiiidddd.
Seems bad!
comment in response to
post
Wow. So the timeline here is
1) Anthem announces they'll pay anesthesiologists based on Medicare rates last month.
2) A vigilante murders the CEO of the most corrupt insurer this week.
3) That news stirs up anti-insurance vibes, and the zeitgeist latches on the ASA's press release on this.
comment in response to
post
Thanks, this was really interesting. Doesn't it still lead back to shifting costs to patients though, i.e. if the insurer caps how much they'll cover for anesthesiologists, won't patients need to pay the overage?
comment in response to
post
Also, appreciate the conversation! Like I said, I'm coming around to static metadata, but I think it's clear there are real tradeoffs here, and not just in switching costs.
comment in response to
post
Given that this is only a problem for local installs, allowing the readme metadata to be dynamic seems like a strict win, in that it allows developers to generate more accurate/useful readmes, but only if they sign up for that complexity. Local install of 3rd party packages is super uncommon, right?
comment in response to
post
Yeah, that's neat! But what you're now describing is a problem with how packages of different varieties (wheel, sdist, or local) store their metadata, not that it is dynamic.
comment in response to
post
Yeah, I wouldn't argue it's at all essential. I use it today in my open-source and industry packages to automate aspects of the release process, but I'm sure we could find alternative approaches.
comment in response to
post
That said, it feels a bit odd to privilege a VSCode plugin over a build plugin. In your example, that feels more like a tradeoff in functionality than a clear-cut "tiny tax". Right?
comment in response to
post
Thanks for engaging with the substance, appreciate it! I'm coming around to the tradeoffs of static metadata, but ultimately, different tools will need to be developed to solve the problems tools like setuptools-scm solve if the community goes down that path.
comment in response to
post
Oops, the last day was apparently a blip, but you get the idea: pypistats.org/packages/set...
comment in response to
post
Appreciated the substance here, but it really detracts from your argument when you sub-tweet (skeet?) projects like hatch-fancy-pypi-readme and setuptools-scm. The latter has >3M daily downloads, so it's not like it's some zany side-project.
comment in response to
post
Ah, that makes sense, but also, disappointing! Apparently Louisiana too, but they call them parishes instead of boroughs. Language is hard!
comment in response to
post
5) So yeah, Bluesky might be the next Twitter, maybe even with better management. I'm really excited about that! But ATProto isn't the next email standard for micro-blogging.
comment in response to
post
5) So yeah, Bluesky might be the next Twitter, maybe even with better management. I'm really excited about that! But ATProto isn't the next email standard for micro-blogging.
comment in response to
post
4) They are working on "credible exit", i.e. users can take their content with them when they leave. Micro-blogging content <<< network and distribution, which isn't portable. I'd be more inclined to invest in this platform if it were. I'm not a creator, so that's not an economic decision for me.
comment in response to
post
3) They've taken VC money, and they're subject to the same social media economics as other platforms, e.g.
- you are the product, not the customer
- enshittification
- censorship vs. free-speech content moderation
comment in response to
post
2) They ARE a B corp, founders are given a lot of leeway in general, and individuals and their actions matter, so they could absolutely do a MUCH BETTER job of running Twitter 2.0 over here. So far, so good!
comment in response to
post
👋 Lead engineer at Prolific Machines, using light to control biology for bio-manufacturing, e.g. cultivated meat and therapeutic/nutritional protein production.
I'm using my career to build a better world, working to bring an end to factory farming by accelerating the alternative protein industry.
comment in response to
post
Reminds me of this: zaplib.com/docs/blog_po...
comment in response to
post
Nice! Prolific doesn't yet have one, but I'd love to join