Our People team built its own software this year. No engineering background. Just vibe coding and a lot of iteration.
$10k saved. Hours reclaimed. And tools that actually fit how we work.
www.netlify.com/blog/the-yea... DX got us here. AX gets us further.
Netlify CEO @biilmann.blog is speaking at @wearedevelopers.bsky.social World Congress North America this September on what happens when humans and AI agents build together.
www.wearedevelopers.com/world-congre... 
Ship Quickly, Stay Secure!
Dive into AI prototyping that withstands production challenges
Discover how to safeguard your database while learning the essentials of project handoff without losing safety standards
Secure your spot today: supabase.com/events/agenc... 
another to add to the pete.garden/the-nature-of-the-job collection: seangoedecke.com/will-my-job-still-exist 
Leap Week is back. March 24-26.
Three days of live sessions on what comes after the interface.
Nine sessions + some big partner reveals dropping soon.
Register for free → leapweek.directus.io 
come hang out with us on Discord for live Q&A, AI support, direct access to our team, and help from the community 👇
pris.ly/discord 
star the repo
└ github.com/ahmadawais/...
└ npmjs.com/package/pli...
└ built with Command Code
└ $ npm i -g command-code tested on real macOS apps (VS Code, MTLReplayer, etc). handles nested dicts, arrays, dates, buffers, booleans. all the plist types.
built with Command Code. following the taste system for consistency.
if you work with plists and want modern tooling, give it a try. const data = parse(xmlString);
build js objects back to xml:
const { build } = require('plist-next');
const xml = build(data);
also ships with a CLI:
$ npm install -g plist-cli
$ plist parse Info.plist
$ plist build '{"name":"app"}' • Zod validation at boundaries — catch errors early
• 45 comprehensive tests — edge cases covered
• ESM + CJS — both module formats, tree-shakeable
• Zero CLI dependencies — library stays lean
$ npm install plist-next
parse xml plists to js objects:
const { parse } = require('plist-next'); introducing plist-next 📋
i wanted a modern plist parser that just works. no bloat, no legacy baggage, just typescript + strict types + zod validation.
the original plist.js is solid, but it's 2026. we can do better.
plist-next:
• TypeScript first — strict mode, full type safety Know a woman building with AI? Drop a link. 👇
Built for adult learners who want a serious, motivating way to improve. 🎹
Melissa on LinkedIn: www.linkedin.com/in/mcleanmel/ “I built this app to solve my own pain-point. Most options on the market are tailored to children and feel demotivating to me as an adult learner.”
Melissa built Glissando — sight-reading drills designed for adults learning piano, with exercises that progressively get more challenging as mastery grows.
glissandovcg.netlify.app Women builders spotlight (5/5): Melissa McLean
Fractional Principal Product Designer · Founder, Spark North Design (www.sparknorth.design) 
Know a woman building with AI? Drop a link. 👇
Uses OpenAI (tone analysis) + @elevenlabs.io (speech practice). And it’s rooted in a real need: decoding professional communication without spiraling into hours of overthinking. Women builders spotlight (4/5): Ciara Wearen
Built for the @bolt.new hackathon (hosted on Netlify): a communication platform for neurodiverse professionals.
t.co/XORkmQZFdD 
if you're using coding agents seriously, curious what surprised you most about how your workflow actually changed. here's what i didn't expect: rebuilding old projects to teach Command Code my taste is more valuable than i thought. each one reinforces patterns i want the agent to know. not because my way is universal, but because consistency matters when you're working at this pace. the result isn't just speed. it's that i can trust the output without the usual "let me rewrite half of this" step. i'm shipping a project most days now because the friction dropped to nearly zero.