🦋 IOKode @iokode_dev

iokode.blog/posts/opiniona…

Double post today from @Montyclt about AI coding. A new reflection on the cognitive cost of AI agents (productivity, focus, and mental training), plus a translated 2022 post to add more context. iokode.blog/posts/cognitiv…

This is very early, but it already has enough shape to explain the idea publicly. OpinionatedArch is not meant to be a neutral Arch installer. It is my attempt to make my own development machine match how I actually work. There's still a lot of work to do on this, but I'm happy with how it's going.

🦋 IOKode @iokode_dev

4 months ago

@Montyclt is introducing OpinionatedArch: an Arch-based distro for one physical person who uses multiple login users as work contexts, not as separate machines. Shared versioned dotfiles, automatic snapshots, and pre-boot returning message. iokode.blog/posts/opiniona…

0 2 2 5K 0

@Montyclt is introducing OpinionatedArch: an Arch-based distro for one physical person who uses multiple login users as work contexts, not as separate machines. Shared versioned dotfiles, automatic snapshots, and pre-boot returning message. iokode.blog/posts/opiniona…

Reflections by @Montyclt on Tailwind’s financial problems and their implications for the IOKode project. iokode.blog/posts/tailwind…

Vowels exists; use them. iokode.blog/posts/vowels

BEM and Tailwind share the same problem: they make HTML painful to read. @montyclt shares his collection of CSS practices—from naming conventions and file structure to units and theming. iokode.blog/posts/css/

@dhh I decided to do the same in the IOKode's projects and I wrote about the reasons. Thanks DHH. iokode.blog/posts/master/

The @CodelyTV's "Rule of Three" for code duplication is wrong. Deciding when to extract repeated code isn't about counting duplicates—it's about understanding your domain. Similar code ≠ Same concept #SoftwareDesign #CleanCode #Programming iokode.blog/posts/repeated…

The @iokode_blog is down (error 500) and it will be down for some hours. I'm working now to deploy a new blogging engine based on @astrodotbuild that will relace the engine written in dotnet. When deployed, two new posts explaining the changes will be published.

Vengo a aprovechar la charla de @davidjrh en #dotNET2024 para decir que yo estoy escribiendo mi propio framework opinionated llamado, (redoble de tambores): "OpinionatedFramework" xD github.com/iokode/Opinion…

El día de San Valentín es un día importante para el proyecto @iokode_es o, más bien, para su representación legal. IOKode OÜ, la sociedad que respalda el proyecto, fue fundada el día de San Valentín del año pasado y, hoy ha ocurrido algo en relación a ella (algo bueno). Dos San Valentines seguidos han ocurrido dos eventos importantes alrededor de dicha sociedad, por lo que oficialmente puedo decir que San Valentín, es un día importante para IOKode.

Curious fact: I'm using Podman in production on the @iokode_es server. Easier to install than Docker on Ubuntu: "sudo apt install podman". No need to add custom PPA like Docker.

💻 Ivan Montilla @Montyclt

3 years ago

Tried Podman Desktop on macOS and in my impression, it is faster than Docker desktop. Both options require Linux virtual machine.

0 0 0 593 0

El blog ha estado caído varias semanas por una cuestión técnica relacionada con el servidor, pero ya está funcionando de nuevo.

I'm developing a C# framework for application layer (decoupled to the infrastructure, so it can work on the web server via AspNetCore or Castle Monorail, on mobile via MAUI, on the browser via Blazor, on the console...). Based on the idea of clean architecture. The framework provide a foundation to write use cases/commands, interfaces to access services like job queue, cron, emailing, notifications, events, validations, text translations, encrypting...). The framework exposes some interfaces to the application layer to access these services (implemented in infrastructure layer) through a service locator (yes, I said a service locator, there aren't support for DI, you are allowed to blame me "that's an antipattern" 😜) and static facades (very similar to Laravel facades). That means, you can easily create an use case that send an email in your application layer, but the email sender will be implemented on infrastructure layer (of course, there are default implementations, so you don't really need to write the email sender). The main idea is that you don't need to write "EmailSender" interface each and each time that you creates a new application. I have been inspired on @laravelphp for Facace system and some of the services (like Queue, Events, Emailing...). Other Laravel services like Session or Cookie aren't available due there are part of the HTTP infrastructure and not application layer. As I know, Laravel is inspired on @rubyonrails, so I want to ask to developers that works with Laravel, Django (@mgarciadelojo) and Rails (@MartoutaTech) about their favorites features of the framework that are intended for application and not for the infrastructure. I think that can help me to think about features. Tell me too about some wanted implementations. For example, a feature that I needed is a filesystem access, with Google Cloud Storage implementation. I appreciate this information to know specific needs. Thank you! GitHub (if you have time, please read the README): github.com/iokode/Opinion…

Feliz 2024. Para este año me he propuesto dar vida a este proyecto, que lleva desde julio sin una entrada en el blog. Este año me gustaría empezar en serio a grabar vídeos y volver a publicar en el blog.

Interesantes reflexiones de Iván Montilla @Montyclt en su blog de desarrollo de software sobre su experiencia real teletrabajando: organización del tiempo, networking, productividad. 👉 iokode.blog/post/2022/mi-o…

Añadir que, donde critico a los bootcamps, el bot ha entendido que me dedico a vender bootcamps xD iokode.blog/post/2022/mi-o…

Cuando el bot spammer no entiende lo que lee y mezcla cosas, llegan al email joyitas como esta xD La entrada a la que hace referencia iokode.blog/post/2023/soft…