Posts

Over the past decade of building Android libraries, I’ve realized they differ not just by what they do, but by how tightly they’re coupled to the Android OS. ...

In the rapidly evolving landscape of AI-assisted software engineering, we routinely fall into the “specs-to-code” cycle: a frustrating endless cycle of prompt engineering, trying to perfect instructions rather than engaging with the messy, architectural reality of our thoughts and of our projects. The reality is that the specs-to-code approach currently doesn’t work very effectively. LLM’s lack the contextual knowledge, but until the technology evolves, we must find more deliberate ways to work with LLMs. ...

Today I watched an incredible Google I/O presentation by Adam Bender titled “Software Engineering at the Tipping Point.” It perfectly articulated something I’ve been thinking about a lot: as AI automates the “how” of writing code, our jobs are rapidly shifting toward the “why.” For decades, as software engineers, we have poured our values, our ethos, and our intentions into products through our code. We used our techne—our technical craft—to express what we valued. We valued mastery over specific languages like Kotlin or framework architectures. ...

A tiny story about AI ...

Prefer language tools, if they exist, rather than relying on assumptions. ...

What happens often, is when people ask direct questions, the danger of being perceived as negative is high. So how does one maintain a positive perception, while still being able to ask and receive questions? Quick answer: Context and perception. Why would asking questions could be perceived as negative? Timing inconvenience. Imagine you are an expert in satellites, and you are speaking in a conference about a technology that satellites use. Then an attendee raises a hand and asks for a satellite definition. ...

I have written a small presentation for developers starting on Dependency Injection frameworks in general, and getting a more detailed view of the basics of Dagger2 for Android The presentation is hosted at slides.com and you can view it following this link https://slides.com/chronvas/dagger-2

Scroll to read, or continue reding in I’ve came across the “hustle” of creating an app that will use Realm, having the database previously populated with data and just include the created database file in the published app, omitting the Json (or any other file) that is being used to populate it. Doing so for a “to be published” app saves time (parsing the file and populating a db) and space (omitting the file which used to create the database). ...