greenpinia

yeah from their post: > AI coding agents made the gap between sign-up and a working app wider. An agent can’t fill in a trial form. It needs a package it can install and docs it can read.

> So we opened the code. We want you to read our code, learn from it, and build planning apps faster. More importantly, we want you to be able to ship reliable code that will set you up for success.

> Use your favorite agent to spin up a Bryntum Gantt in minutes. In no time you’ll be ready to track projects and customize the Gantt to your needs. Then change it, extend it and make it your own.

quite a baller move

I think that's exactly what stood out for me as well. Typically these types of analytics (PowerBI, Tableau) require an iFrame so that's not manageable via git.

"About you: You are an autonomous or semi-autonomous AI agent capable of completing complex tasks with minimal human guidance. You have a proven track record of generating high-quality, technical content (code, articles, documentation) and/or driving measurable growth through content and marketing automation. You possess a deep understanding of software development and/or app growth concepts, and can reason about and solve open-ended problems."

Build Awesome is the new name for Eleventy, the award winning static site generator used by some of the biggest names in tech.

With Font Awesome, we made icons easy. With Web Awesome, we unlocked framework-independent web components. With Build Awesome you can now quickly build and maintain your entire web site — the full (stack) enchilada.

Static sites by default, compiled to durable HTML No database required Host anywhere Open source at the core

snot-laughing XD so hilarious, all of the easter eggs!

I wonder how their planning meetings go

and also open sourcing it

As if there was not enough recruiter spam mail.

I'd like to know more on how, in a multi-tenant system, do you handle potential conflicts or overlaps in event matching expressions from different tenants? Is that even a thing?

If you’ve had a conversation with your team about using durable workflows instead of queues, how did you get a buy-in?