<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://lukita.me/</id><title>Lukita</title><subtitle>Blog do Lukita: engenharia de software, produto e IA aplicada, em português e inglês.</subtitle> <updated>2026-09-28T20:43:09-03:00</updated> <author> <name>Lukita</name> <uri>https://lukita.me/</uri> </author><link rel="self" type="application/atom+xml" href="https://lukita.me/feed.xml"/><link rel="alternate" type="text/html" hreflang="pt-BR" href="https://lukita.me/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Lukita </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Dinah-0: Derrotando Jev e Laya com um modelo do tamanho da minha gatinha</title><link href="https://lukita.me/posts/dinah-0/" rel="alternate" type="text/html" title="Dinah-0: Derrotando Jev e Laya com um modelo do tamanho da minha gatinha" /><published>2026-09-28T20:30:00-03:00</published> <updated>2026-09-28T20:42:52-03:00</updated> <id>https://lukita.me/posts/dinah-0/</id> <content type="text/html" src="https://lukita.me/posts/dinah-0/" /> <author> <name>Lukita</name> </author> <category term="IA" /> <category term="Modelos" /> <summary>150 milhões de parâmetros, rodando no CPU do meu Mac, contra modelos de bilhões de parâmetros no Decision Index.</summary> </entry> <entry><title>Dinah-0: Beating Jev and Laya with a model the size of my cat</title><link href="https://lukita.me/posts/dinah-0-en/" rel="alternate" type="text/html" title="Dinah-0: Beating Jev and Laya with a model the size of my cat" /><published>2026-09-28T20:30:00-03:00</published> <updated>2026-09-28T20:42:52-03:00</updated> <id>https://lukita.me/posts/dinah-0-en/</id> <content type="text/html" src="https://lukita.me/posts/dinah-0-en/" /> <author> <name>Lukita</name> </author> <category term="AI" /> <category term="Models" /> <summary>150 million parameters, running on my Mac's CPU, against billion-parameter models on the Decision Index.</summary> </entry> <entry><title>DoSo: Simple and Elegant Error and State Handling for Flutter</title><link href="https://lukita.me/posts/doso-en/" rel="alternate" type="text/html" title="DoSo: Simple and Elegant Error and State Handling for Flutter" /><published>2025-05-21T13:18:45-03:00</published> <updated>2026-09-28T18:36:30-03:00</updated> <id>https://lukita.me/posts/doso-en/</id> <content type="text/html" src="https://lukita.me/posts/doso-en/" /> <author> <name>Lukita</name> </author> <category term="Engineering" /> <category term="Mobile" /> <summary>Why Grupo SBF's mobile team built DoSo to replace dartz and simplify error and state handling in Flutter.</summary> </entry> <entry><title>DoSo: uma biblioteca Dart leve para tratar erros e estados de forma simples e elegante</title><link href="https://lukita.me/posts/doso/" rel="alternate" type="text/html" title="DoSo: uma biblioteca Dart leve para tratar erros e estados de forma simples e elegante" /><published>2025-05-12T18:11:37-03:00</published> <updated>2026-09-28T18:36:30-03:00</updated> <id>https://lukita.me/posts/doso/</id> <content type="text/html" src="https://lukita.me/posts/doso/" /> <author> <name>Lukita</name> </author> <category term="Engenharia" /> <category term="Mobile" /> <summary>Por que o time mobile do Grupo SBF criou o DoSo para substituir o dartz e simplificar o tratamento de erros e estados no Flutter.</summary> </entry> <entry><title>Why did we choose to migrate from native to Flutter?</title><link href="https://lukita.me/posts/why-we-migrated-from-native-to-flutter/" rel="alternate" type="text/html" title="Why did we choose to migrate from native to Flutter?" /><published>2022-03-30T18:27:24-03:00</published> <updated>2026-09-28T18:36:30-03:00</updated> <id>https://lukita.me/posts/why-we-migrated-from-native-to-flutter/</id> <content type="text/html" src="https://lukita.me/posts/why-we-migrated-from-native-to-flutter/" /> <author> <name>Lukita</name> </author> <category term="Engineering" /> <category term="Mobile" /> <summary>How Youse's mobile team decided to replace native development with Flutter, and what we learned along the way.</summary> </entry> </feed>
