Happy to announce that @mikegood and I started a thing.
β Whiskers β The Creative Engineering Agency
If you need a partner for web apps, landing pages, web3, or AI, hit us up! Weβre booking our first Q1 slots.
Letβs build: https://whiskers.agency
Join us for live Noundry trait iteration sessions
Every Wednesday on Nouns Discord (alternating between 15:00 UTC and 23:00 UTC):
https://discord.gg/Z47Qpz26Fe
weekend Noundry shipping: Remixing
streamlined flow from Gallery to Studio and back to the Gallery to help you quickly iterate on traits, and also to up our collab game!
live now. give it a go!
PSA: Join the #noundry channel on Nouns Discord
https://discord.gg/hTfpSsSJ2R and let's get some community calls going
who wants to do some live trait critique + iteration?
https://potetm.com/devtalk/stability-by-design.html
the Clojure ecosystem sounds interesting, but I'm sure this post is a bit one-sided on the trade-offs analysis. I could imagine this strategy leads to considerable semantic drift and steeper learning curves, so best for high-context devs who'll work on the codebase in the long term, worse for onboarding and projects with a higher maintainer/contributor turnover.
What do you say, Clojure folks?
(are the Clojure devs in the room with us right now?)