Replying to @RisingSunInt_
I did something very similar when Astra dropped a month or so ago, I’ve been meaning to see how Opus could polish gtai.online
16
Replying to @nateherk
1
21
Replying to @peduarte
If people didn’t think this way then your product would surely not exist… I would of thought your founder shared the same sentiment when starting Raycast
Replying to @LinusEkenstam
Ai has been able to build electron (desktop) apps for ages though which I’m guessing this is wrapper ontop of. This is great but there was no puzzle piece missing
95
deprogram.sol retweeted
This has been said a thousand times before, but allow me to add my own voice: the era of humans writing code is over. Disturbing for those of us who identify as SWEs, but no less true. That's not to say SWEs don't have work to do, but writing syntax directly is not it.
deprogram.sol retweeted
Getting to great design isn’t about narrowing your focus onto one tiny problem or building yet another “purpose‑built” tool. It’s about learning to see through the surface and recognize the truths underneath everything we do – the same patterns, the same flows, the same ideas repeated across different tools and teams.
For years, our tools have siloed us. Each one arrives with a strong opinion about how work “should” be done. “This is a project, so it must go through these stages.” “This is design, so it must be framed and canvas.” “This is engineering, so it must be elusive.” The tools became selfish. They stopped being mirrors for how we think and started dictating how we’re allowed to think. You have your way of working, your way of seeing, but you’re forced to pick one box, one stack, one workflow.
Craft is not just animation, motion, or detail. Craft is the coherence of the entire system – how ideas move from a note to a sketch to a prototype to a running product, how teams move from chaos to clarity without feeling like they need to change who they are just to fit into a tool.
Great tools should unify, not fragment. They should connect the designer’s canvas with the builder’s editor, connect the writer’s outline with the team’s roadmap, and let patterns repeat and evolve across everything instead of trapping them in separate silos.
Designers can build. Builders can design. The old line between “design tools” and “dev tools” is an artifact of the software we had, not the people we are.
Let the dreamers build. Let the builders dream. Give people systems that get out of the way, that adapt to how they think, that make it feel natural to go from idea to reality without asking for permission at every step.
That’s the future that matters – not more purpose‑built boxes, but one coherent universe where all the pieces finally talk to each other, and you get to be your whole self while you work.
Whenever a new design to code tool comes around, people get excited. It’s considered the holy grail of design. You can now design with code. This is the final evolution.
But I don’t agree. It’s only the holy grail if you value output higher than the process of design.
Whenever a designer becomes more of a builder, some idealism and creativity dies. Not because building is bad, but because you start out including constraints earlier in the process than they should.
I’m one that very much thinks design is ultimately what is shipped. But before it shipped, there is a lot of stages that don’t benefit from code or some implementation constraints.
In architecture, a lot of the best work is started with sketches and some of the best architects still draw by hand. People forget that the creative process is not about tools. It’s about forming a vision, and then translating that vision into some form. You can use various tools as part of the process, but designers job is really communicating that vision.
Once you become the architect and the builder, or the designer and the developer, you start making more conservative bets. You gravitate to what you already know is feasible or supported. You make smaller iterations. You stop dreaming something big. This is not design.
Designers, don’t do that. Your job is to imagine the future, and sometimes code and convention gets in the way. Use tools. Understand the domain. Get close to the medium.
But don’t lose your greatest strength ability to dream. Work with engineers to realize those dreams.
Designing in code is just a path to local maxima and ruin.
deprogram.sol retweeted
GM
Our virtual space for Tezos artists and non digital art Byron Bay, is growing and has a new group of professional collaborators. createart.studio, @_deprogram_ , @paul_g_brown + Louis Ponte, at aerial-perspectives.au
Replying to @RhysSullivan
Hmmm if I get in a taxi, and ask them to take me somewhere am I a driver
1
23









