eddietejeda
Here is our write up on the Ducklake blog: https://ducklake.select/2026/07/29/bringing-ducklake-to-data...
For context, we previously built custom catalogs optimized for specific use cases. But they were hard to maintain, especially as requirements changed, and Apache Iceberg was too heavy for our specific low-latency work.
Since Ducklake is only a spec, we implemented datafusion-ducklake, and it performs as well as any custom or specialized catalog we built. We use Postgres as the catalog store, and it does not get much simpler than that: a transactional database for transactional data.
Plus, it gives us a clear spec for implementing complex parts like time travel, snapshots, etc.
It's been a godsend.
We welcome and encourage contributors!
Why SQL Needs Software Libraries
Mode is a modern analytics and BI solution that combines SQL, Python, R and visual analysis to answer questions faster.
Used by Segment, Shopify, Twitch, Lyft, Doordash, NYTimes. Learn more about customers. https://mode.com/customers/
Open roles: - Senior Back-End Engineer - Experience with production engineering, mostly Java, some Go and Python - Senior DevOps Engineer - Terraform, Go, AWS ECS
Ping me if you have questions.
The new field called “attribution science”
https://18f.gsa.gov/2015/10/15/best-practices-for-distribute...
Open positions: https://join.tts.gsa.gov/
The concern:
https://www.scientificamerican.com/article/plastics-plants-a...
An insider view of industry:
https://www.mckinsey.com/industries/chemicals/our-insights/p...
My source: my wife is an environmental lawyer who is very concerned about climate change and works closely on these issues.
More about the company: https://www.navapbc.com/services/
Open Roles:
- Infrastructure Engineer, Terraform (NYC, DC, SF, Remote) https://jobs.lever.co/nava/817283f6-9911-4f72-a5ef-fbcdd2c04...
- Software Engineer (NYC, DC, SF, Remote) https://jobs.lever.co/nava/c280510a-e3ed-4b6c-b64f-8ce82801d...
- Software Engineer, Lead (NYC, DC, SF, Remote) https://jobs.lever.co/nava/26679fe1-b47a-4e55-bd62-775b16be3...
More Roles: https://jobs.lever.co/nava/
Ping me if you have questions.
Clearly, some people think there is value. That's it.
You can estimate here: https://www.federalpay.org/gs/calculator
Also, the sense of duty and serving the public is real. And this is not expressed in a tongue and cheek way... it’s an earnest desire to do meaningful work.
Many people who join USDS, 18F, and PIF from the tech industry are there because they genuinely want to do good work.
Server-side rendering no-reload JavaScript framework
Personally, I am very excited for this release.
* Matz's goal to get Ruby 3 to be 3x faster than Ruby 2.
--
@sosodev Thanks for the updated info!
Gitlab sped up Puma using sleep sort
VMWare email blast: Pivotal Web Services End of Availability
“The Federal Source Code Policy (FSCP) called for the establishment of the the Code.gov program office and corresponding technical platform of a website and application programming interface (API). The program office assists agencies with policy, acquisition, and code inventory creation. We are a small but mighty team with five members with expertise and beliefs pertaining to discovering, sharing, and open sourcing the People's code.”
You may also want to read up on 18f.gsa.gov. They publish and share lots of open source code.
I started at 18F and now run https://github.com/cloud-gov
I think the reason people dislike blockchain so much is because the promise that blockchain will do DoEverythingBetter™ is not very convincing.
All things considered, this industry is pretty small... but it's an industry. It's already been around a decade and could easily last for many more.
In that time, people who work in the blockchain space will bring those ideas, concepts, and ideologies to other industries.
When you think of it that way, looking under the surface for interesting ideas does not seem so far fetched. I think this post did a great job telling a story about the new and fascinating concepts.
Here's my take: the title is unclear. The federal government has required https for a while.
Learn more here: https://https.cio.gov/
OMB wrote a memo requiring https in 2015: https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/me...
If you see the "announcement" linked in the article, you'll notice that it's referencing this page: https://home.dotgov.gov/, which is about the HSTS preload list.
The team at Basecamp, Shopify, and GitHub are all running Rails 6 RC-1
I prefer to see it as a build environment for your code, data, and assets. The data can change all the time, but it either changes as part of a build process or pulled from an external API.
Here's a good summary of a team choosing this approach for their data-heavy site: https://revenuedata.doi.gov/blog/homepage-revamp-part-two/
We do everything in the open, so feel free to follow our work here: https://github.com/18F/federalist
We also implement the USWDS, which you can follow here: https://github.com/18F/federalist-uswds-jekyll
Let me know if you have any questions!