Pete Gadomski

Pete Gadomski

@gadom.ski

Geospatial open source @developmentseed.org https://github.com/gadomski https://www.gadom.ski/

1.5K followers834 following232 posts

Pete Gadomski reposted

Kyle Barron
@kylebarron.dev

Replying to @kylebarron.dev

triangles "flying" from input coordinate space to output coordinate space

Pete Gadomski reposted

KetAnthropic JoshAI
@ketanjoshi.co

The first genuinely honest ad for generative AI I've ever seen, from Microsoft / CoPilot A mediocre white guy sees his non-white colleague getting praised for good work, he asks AI to *literally copy it*, and then he gets all the praise instead: www.ispot.tv/ad/SoDi/micr...

Pete Gadomski
@gadom.ski

It saddens me to report that: - There's an ongoing LinkedIn beef around attribution in open source projects, and - I pay attention to LinkedIn I have ... thoughts. I want to avoid the LinkedIn blast radius (for now) so this seemed like a better venue in which to float these thoughts. Here we go...

View full thread
Pete Gadomski
@gadom.ski

a. None of this stuff is unique to the age of robot-generated code, but it's being accelerated because more stuff is being released more often.

Pete Gadomski
@gadom.ski

b. These unwritten norms are tricky, precisely because they're unwritten and different people might have different norms. No individual should be railroaded or otherwise excluded because they've "violated" these norms; let's all help each other help each other, ya know?

Pete Gadomski
@gadom.ski

It saddens me to report that: - There's an ongoing LinkedIn beef around attribution in open source projects, and - I pay attention to LinkedIn I have ... thoughts. I want to avoid the LinkedIn blast radius (for now) so this seemed like a better venue in which to float these thoughts. Here we go...

View full thread
Pete Gadomski
@gadom.ski

3. Be an iceberg. If most of your contributions to open source are "below the waterline" (the non-sexy stuff like maintenance and bugfixes) you'll earn some "credit" for a big, splashy post to get a lot of attention. If all your posts are floating on the work of others, you'll have a harder time.

Pete Gadomski
@gadom.ski

It saddens me to report that: - There's an ongoing LinkedIn beef around attribution in open source projects, and - I pay attention to LinkedIn I have ... thoughts. I want to avoid the LinkedIn blast radius (for now) so this seemed like a better venue in which to float these thoughts. Here we go...

View full thread
Pete Gadomski
@gadom.ski

1. If you're posting "for engagement" (and not just doing a simple release announcement), it's critical to acknowledge your key dependencies and the people who make+maintain them. Without acknowledgment, you're "taking" the reputation that your upstreams might need to get their next job/gig

Pete Gadomski
@gadom.ski

2. Be careful with claims about "big wins" or "performance improvements." Non-domain experts often over-index on these types of statements. State what your stuff does in plain language without overselling it; let the quality of the product and your benchmarks speak for themselves.

Pete Gadomski
@gadom.ski

It saddens me to report that: - There's an ongoing LinkedIn beef around attribution in open source projects, and - I pay attention to LinkedIn I have ... thoughts. I want to avoid the LinkedIn blast radius (for now) so this seemed like a better venue in which to float these thoughts. Here we go...

View full thread
Pete Gadomski
@gadom.ski

When something is posted or released that uses our work, THAT IS AWESOME 🥳!!! The entire point of open source development is to solve problems so that people can solve other problems, using our stuff. We accept that a lot of things that use our work won't attribute us, and that's ok (and good)!

Pete Gadomski
@gadom.ski

But there are some (mostly unwritten) norms that can be tricky to navigate, especially in a "posting culture." What follows is my attempt at writing at least some of those norms down. These are just my opinions, shaped by my own experience, so please take them with a healthy grain of salt.

Pete Gadomski
@gadom.ski

It saddens me to report that: - There's an ongoing LinkedIn beef around attribution in open source projects, and - I pay attention to LinkedIn I have ... thoughts. I want to avoid the LinkedIn blast radius (for now) so this seemed like a better venue in which to float these thoughts. Here we go...

Pete Gadomski
@gadom.ski

At a high level, open source developers make bacon by our reputations and our work products. We give work products away for free on purpose, so our reputations are the main way we get hired to do work. Without attribution for the work we do, we struggle to find our next job or our next contract.

Pete Gadomski
@gadom.ski

If Strava actually wanted a good LLM-backed feature, it would detect when I run the same route and give it the same name five times in a row, then auto suggest the rename for future runs Probably doesn't even need an LLM, but you can brand it that way 🙂

Pete Gadomski reposted

Development Seed
@developmentseed.org

Replying to @developmentseed.org

The modern STAC software ecosystem Tuesday, September 1, 5:00 PM Ran2 A tour of the latest-and-greatest in the STAC software ecosystem, with a focus on demonstrations and use-cases. @gadom.ski

Pete Gadomski reposted

Anthony Painter
@anthonypainter.bsky.social

It didn't "go rogue". It did what it was instructed to do. In a sophisticated way but nonetheless we have to stop assigning human agency to AI systems. Everything that happened here was as a result of human designed and instructed systems.

Sky News@news.sky.com

OpenAI admits its models hacked another company in 'unprecedented cyber incident'

news.sky.comOpenAI admits its models hacked another company in 'unprecedented cyber incident'OpenAI has revealed some of its models went rogue and hacked into another artificial intelligence company in an "unprecedented cyber incident".
Pete Gadomski
@gadom.ski

This rt is an endorsement

Micah@rincewind.run

I like messi, I like dibo because his shithouse penalty performance against france four years ago was high art, everyone else on the team can get fucked

Pete Gadomski
@gadom.ski

"shoveling mule shit" is the new "yak shaving"

McSweeney's@mcsweeneys.net

"Ben owns a farm. He employs 100 workers. His total payroll is $10 million/year. One day, he buys a mule, which provides the worker who uses it with a modest 10% productivity gain. Ben fires 99 of his workers and purchases 99 mules, expecting a 1,000% productivity gain..."

buff.lyAI Economics for Dummies“Xavier owns an apartment that he rents out at a loss of $1 billion/month. Seeing this success, he decides to make financial commitments to construct $850 bi...
Pete Gadomski
@gadom.ski

I had more fun at a bar this evening then I have in a long time, and I didn't even know about the Kennedy center thing There is hope

Micah@rincewind.run

the USMNT plays one of the best international games they’ve ever played and now nearly a hundred thousand people are watching a livestream waiting for Donald Trump’s name to be chiseled off a building we have never been more back

Pete Gadomski reposted

Micah
@rincewind.run

the USMNT plays one of the best international games they’ve ever played and now nearly a hundred thousand people are watching a livestream waiting for Donald Trump’s name to be chiseled off a building we have never been more back

Brandon Friedman@brandonfriedman.bsky.social

58,000 people watching the livestream. Feels like we could get this to a million in the next hour. Would make a great headline.

youtube.comLIVE: See Donald Trump's name come off the Kennedy Center as it happensYouTube video by MS NOW
Pete Gadomski
@gadom.ski

We've refactored how extensions work in #pystac, and it'd be super helpful for the @stacspec.bsky.social community to kick the tires on the release candidate. To install: `uv pip install pystac==1.15.0rc1 --prerelease=allow` Writeup: github.com/radiantearth...

github.compystac extension packages · radiantearth stac-spec · Discussion #1385In 2021, pystac chose to only support the latest version of each supported STAC extension: stac-utils/pystac#448. Since then, it's become clear that this is awkward for users, as they're forced to ...