Miguel Ferreira

A nossa velocidade de execução é unheard of em Portugal (mais ainda tendo em conta o tamanho da equipa). Se genuinamente gostas de trabalhar, queres fazer algo com um enorme impacto na vida e no dia-a-dia dos nossos utilizadores, e não está para tretas, queres é fazer, junta-te a nós!

Sim, concordo a 100%, o meu ponto é mais do hustle propriamente dito! Vários dos meus “melhores dias” (wtv that means) são os mais calmos. A malta tem que descansar (e garantir que é um bom descanso!), mas também tem que/deve esforçar-se bastante! E o que sinto é que muita malta que diz que trabalha muito, talvez acreditem mesmo que o façam, mas não o fazem, de todo (seja por ineficiência ou falta de horas)! É preciso ganhar alguma resistência :)

@marrf_tech As pessoas têm que descansar, andar sempre com cortisol alto é fazer para desmanchar. Tenho alturas que faço 10h por dia e só faço merda, tenho dias que faço 5h e resolvo muitos problemas a longo prazo, as vezes menos é mais.

If it is 8pm and everyone is offline on slack, you are ngmi

What’s the best way to find like-minded creative people that want to work extremely hard on AI in Portugal?

Então não é que a segunda maior empresa portuguesa, a Galp, tem no seu atendimento automático por telefone uma mensagem a dizer que este mês estão com um problema a enviar faturas por email e vão enviar por carta. (Motivo pelo qual liguei, anyway). 🫠

Today we’re introducing two big steps for health at OpenAI: - ChatGPT for Clinicians, a free version of ChatGPT designed for clinical work - HealthBench Professional, a new benchmark to evaluate real clinician chat tasks We’re excited about what this can unlock for care. ❤️

say it with me now. experts are fake, smart generalists rule the world, everything is designed by people no smarter than you, and courage is in shorter supply than genius

The Apple homepage now has a "Community Letter From Tim" To the Apple community: For the past 15 years I’ve started just about every morning the same way. I open my email and I read notes I received the day before from Apple’s users all over the world. You share little pieces of your lives with me and tell me things you want me to know about how Apple has touched you. About the moment your mom was saved by her Apple Watch. About the perfect selfie you captured at the summit of a mountain that seemed impossible to climb. You thank me for the ways Mac has changed what you can do at work and sometimes give me a hard time because something you care about isn’t working like it should. In every one of those emails I feel the beating heart of our shared humanity. I feel a sense of deepening obligation to work harder and push further. But most of all, I feel a gratitude that I cannot put into words, that I somehow got to be the person on the other end of those emails, the leader of a company that ignites imaginations and enriches lives in such profound ways it defies description. What an honor and a privilege it has been. Today we announced that I’m taking the next step in my journey at Apple. Over the coming months I will be transitioning into a new role, leaving the CEO job behind in September and becoming Apple’s executive chairman. A new person will be stepping into what I know in my heart is the best job in the world. That leader is John Ternus, a brilliant engineer and thinker who has spent the past 25 years building the Apple products our users love so much, obsessed with every detail, focused on every possible way we can make something better, bolder, more beautiful, and more meaningful. He is the perfect person for the job. John cares so much about who we are at Apple, what we do at Apple, who we reach at Apple, and he has the heart and character to lead with extraordinary integrity. I am so proud to call him Apple’s next CEO. This company will reach such incredible heights under his leadership, and you will feel his impact in every bit of delight and discovery that grows out of the products and services to come. I can’t wait for you to get to know him like I do. This is not goodbye. But at this moment of transition, I wanted to take the opportunity to say thank you. Not on behalf of the company, this time, though there is a wellspring of gratitude for you that overflows inside our walls. But simply on behalf of me. Tim. A person who grew up in a rural place in a different time and, for these magical moments, got to be the CEO of the greatest company in the world. Thank you for the confidence and kindness you’ve shown me. Thank you for saying hi to me on the street and in our stores. Thank you for cheering alongside me when we unveiled a new product or service. Thank you, most of all, for believing in me to lead the company that has always put you at the center of our work. Every day we get up and think about what we can do to make your life a little bit better. And every day, you’ve made mine the best I could have asked for. Thank you. Tim Cook

wooooow!

@jose_goncalves_ So cool, awesome job!

Dozens of top app teams share my videos on their Slacks. You can get the same information as them for free.

PgQue v0.1.0 is out. PgQ -- the Postgres queue system built at Skype 20 years ago for 1B-user-scale workloads -- repackaged for the managed-Postgres era. One SQL file. No C extension. No external daemon. pg_cron to tick. Why bother reviving a 2007 architecture? Every major Postgres queue in production today uses some flavor of SKIP LOCKED + UPDATE/DELETE. It works under light load. When you have more data and higher load, it degrades predictably. Then you get posts like these: - Brandur at Heroku, 2015: 60k job backlog in one hour from a single open transaction - PlanetScale, 2026: death spiral at 800 jobs/sec - River issue #59, awa issue #169 and so on, Oban's partitioning work, PGMQ's autovacuum tuning guide and duct-taping with pg_partman The core issue is how Postgres MVCC is implemented and how we deal with it. Dead tuples in the hot path, xmin horizon pinned, vacuum falling behind, query performance quickly degrades. This happens every time you run pg_dump, execute an analytical query, or have a lagging/unused logical replication slot. PgQ solved this in 2007 with snapshot-based batching and TRUNCATE rotation -- zero dead tuples in the event path, by design. But PgQ needed a C extension and an external daemon. Which means it doesn't run on RDS, Aurora, Cloud SQL, AlloyDB, Supabase, or Neon -- i.e., where most Postgres lives now. PgQue closes that gap. 💎 Pure SQL + PL/pgSQL (PgQ engine) 👩‍💻 \i sql/pgque.sql -- you're done 🕑 pg_cron replaces pgqd (optional, recommended) 💻 Python, Go, TypeScript client examples shipped 💙 Apache 2.0 Trade-off: end-to-end event delivery latency is up to a second, it depends on ticking frequency. If you need sub-3ms job dispatch, use River, Oban, or graphile-worker (and avoid anything that blocks xmin horizon). If you need high-throughput event streaming with fan-out inside Postgres -- Kafka-shaped, without Kafka and dealing with transactional outbox implementation -- this is the right shape of tool. Kudos to Marko Kreen and Skype engineers who implemented this decades ago, for the original PgQ, and to Alexander Kukushkin whose recent "Rediscovering PgQ" talk brought this quiet corner of the Postgres ecosystem back into view. Stars, issues, PRs, and honest criticism all welcome. Link 👇

I feel bad dunking on them so much but it's genuinely absurd how bad the new Claude Code desktop app is. You can feel the vibe code leaking everywhere. Every "feature" is barely integrated and full of edge cases that weren't considered. Every menu feels barren, stuffed in last second for some random toggle. Every hotkey breaks as soon as you try to do anything else. I've lost track of how many bugs I've encountered. I found at least 40 in under an hour. And it's all truly absurd arcane shit. Stuff like voice mode typing in all input boxes instead of just the one you have focused. Any one of these issues would have been enough for me to do a massive post-mortem and likely fire someone. A $400b company shipping this is absurd. I feel like I'm going mad. How does anyone seriously use this?? It is broken on fundamental levels that are hard to comprehend. How are we supposed to trust the code these models produce if Anthropic's official showcases are absolute slop? Dedicated video on this coming tomorrow. Just needed to get this off my chest.

❤️

Software isn't dead. Creating it became easier — but thats a good thing, because making good software is still hard. Change my mind.

human optimism has risen again

@sama What a cute picture! :) Stay safe

I wrote this early this morning and I wasn't sure if I would actually publish it, but here it is: blog.samaltman.com/2279512

somewhere along the way we stopped caring. make products worth caring about again.

I should be doing 47 other things, but details like these make me happy :)

Such a good article! willybrauner.com/journal/signal…

It's so annoying that so many times (always?) when I copy text with new lines and bullet points into Claude, it always formats it wrong. If i copy it into Codex/ChatGPT it works perfectly. Even worse....! If I write the text directly in Claude, say in 'Chat' mode, and then copy it to any of the other modes (Code or Cowork) it ALSO messes up the formatting. From its own text. Jesus.

For some weird but lovely reason the hi-fi world is full of elegantly built and well thought out hardware. This volume knob is as smooth as it gets when you rotate it manually. If you rotate it via the controller (yes!) it has an ease-in acceleration curve, adding to the whole experience (I assume it's made this way to help with smaller volume increases). Just... so good.