Replying to @XMihura @GooglePlay
Yo pillé un apartado de correos y una línea de móvil dedicada. Funcionó de lujo en Apple pero el apartado de correos no coló con Google
we really need a new kind of interaction with computers
We were going to build a smart pen prototype, then @shensitivity just bought one off-the-shelf + used Codex to decompile + integrate it into our software system
And it's so smooth
Ismael Canal retweeted
Muy contentos de poder compartir por fin esta gran noticia 🎉🎉🎉
forbes.es/ultima-hora/104252…
Infinitas gracias a @BisiestoEstudio y a @relajaelcoco por unirse al barco de @secture_com 🏴☠️ (Tres empresas, un único equipo 💛🧡🖤)
@MiguelBisiesto entra como coCEO del grupo para ayudarnos a seguir creciendo.
Os comparto tambien esta entrevista de @ChemaNieto donde le contamos como ha sido el proceso y nuestros planes de futuro junto a grandes amigos youtu.be/-Lqo7RppE1s?si=9L0R…
You don’t need a camera at all, just a smarter pen:
xitter.cf/basiclines/status/2100…
Replying to @inakitajes
Iñaki estoy usando @calisteniapp enhorabuena es un producto muy bueno y lo pago con gusto
Stop. Think. Prompt.
Taking a step back and rethinking what’s taken for granted it’s a super power
small update to the sessions menu in the GitHub Copilot app 💫 worked with @gimenete to make it all a little calmer 〜
Diseñando a velocidad terminal ya está online:
youtu.be/6uTTsuF8SXQ?si=go2x…
Replying to @omixam
convergence to the mean
when everyone looks at everyone else to decide what to make, we eventually stop making anything of our own.
we copy what works. borrow the language, the aesthetic, the features. we call it learning from the market, following best practices, staying competitive. together, everything starts to feel familiar. polished, interchangeable. nothing wrong. nothing alive.
the mean isn’t necessarily bad. it’s where everything lands when we remove the reasons for it to be different.
numbers are easier to compare than feelings, so we make things that produce numbers. we study what gets attention, then shape ourselves around it. eventually the feedback stops informing the work and starts authoring it. we’re no longer asking what we want to say. we’re asking what will be rewarded for saying.
ai makes this loop frictionless. it can draw from more references than we could see in a lifetime. but access to every perspective isn’t the same as having one. it hasn’t lived a particular life that makes one detail unbearable and another beautiful. when we ask it to choose for us without bringing any intention of our own, we get something plausible, easy to approve.
then we ship it, measure it, copy it, and feed it back into the next round. a tidal wave of mid.
this changes not just the work, but the people making it.
we describe ourselves in categories platforms can distribute and markets understand. designer. founder. creator. pick a niche. build a brand. be consistent. the parts that don’t fit become inconvenient, even when those contradictions might produce our most interesting work. we become easier to classify and harder to tell apart.
i think we need to approach making things more like artists.
an artist develops a perspective through the work. making, noticing, choosing, failing, returning. learning what matters even when nobody else cares. craft gives that perspective a form precise enough for someone else to experience.
the life outside the work matters too. the places you’ve lived, the people you’ve loved, the things you’re embarrassed to care about. these aren’t distractions from having something to say. they’re how you come to have something to say.
we understand this with music, paintings, photographs, movies. we expect a person to be present in the choices. we want to experience something we wouldn’t have encountered without them.
software can do this too.
a piece of software expresses beliefs about how life should feel. what deserves your attention. what you should be free to change. whether a task should feel like paperwork or play. even a small interaction can carry someone’s care, humor, or curiosity.
but we rarely talk about software as a medium. we talk about it as an industry. markets to capture, workflows to optimize, competitors to catch up with. we add a feature because someone else has it, without asking whether it belongs. products accumulate the same parts and lose what made them worth choosing.
underneath the branding, it’s all the same thing.
artists learn from others too. the question is whether you’re absorbing those influences into a point of view, or using them to avoid developing one.
what are you trying to let someone feel, understand, or do? why this particular shape? what have you noticed that the existing tools don’t seem to notice?
those questions don’t have answers you can borrow from a competitor’s roadmap.
if we can make almost anything, deciding what deserves to exist becomes more important, not less. speed gives us more chances to exercise judgment. it doesn’t remove the responsibility.
i don’t want a world where every person becomes a more efficient distributor of the same ideas. i want people to use these tools to go further into what they actually care about. to make things specific enough that we can feel someone behind them.
what is the point of everyone being able to make something, if we all end up making the same thing?
Replying to @omixam
Que todos queremos diseñar coches de fórmula 1 pero hay pocas escuderías. Si trabajas en Dacia no esperes trabajar la aerodinámica y el peso del coche.
Preocúpate de aprender mucho de materiales económicos y de cómo optimizar cada detalle al céntimo
Conoce el negocio en el que estás y no innoves en el diseño, eso está resuelto, profundiza en optimizar el diseño de lo que es relevante para tu negocio, nada más
Specific problems tend to optimize over time to the same solutions, because that’s the optimal path to solve them
To innovate you either:
- make it 10x affordable
- make it 10x faster
- or solve a novel problem
Replying to @JordiMonPMM @MarkVillacampa
Hace calor y no soy nada del look speaker 😹
Wanna see how 1M LOC performs on ghapp?
github.com/copilot/app/launc…
How to render a huge PR with over a million changed lines across 2,200 files and 400+ review comments? The tricky part isn’t the code, it’s the comments.
I wrote about how we tackled this in the GitHub Copilot app:
github.blog/engineering/user…












