AI in our day-to-day: Support tool or silent copilot?
The real question isn't whether we're going to use AI or not, but how to do so without losing the essence that defines us.
Artificial intelligence is here to stay; that is a truth no one disputes anymore. However, within the software development ecosystem, the real question isn’t if we are going to use it, but how to do so without losing the essence of what defines us.
At Grava, our compass has always been the open source spirit. To us, tools are not closed black boxes; they are elements to be explored, dismantled, questioned, and reinvented. We are approaching AI under that same premise: testing models, adjusting workflows, making mistakes, and trying again. We are in the middle of a learning curve and, quite honestly, we prefer to admit that we don’t have all the answers yet.
The developer as an artist
We like to think of software development as an art form. An artist is someone who cares for the details that truly matter: the expression, the intent, and the stroke that gives meaning to the work. In this scenario, AI functions as a tool that can fill in the background, correct shadows, or adjust the brightness, but the primary brushstroke remains ours.
In programming, this distinction is vital:
-
Architecture: A human construction based on context.
-
Design decisions: Debated as a team, not in a prompt chat.
-
Critical thinking: The filter that separates a functional solution from a brilliant one.
-
Creativity: That spark that motivates us to develop something from scratch does not reside in a language model.
The balance between efficiency and challenge
Integrating AI has forced us to ask uncomfortable questions: Are we truly more productive, or just better organized? Are we automating what frustrates us… or also what challenges us and makes us grow?
The current challenge is finding that balance. We want AI to handle the repetitive tasks that take up time but offer no creative value:
-
Drafting basic technical documentation.
-
Code cleaning and mechanical refactoring.
-
Generating unit tests.
-
Meeting summaries or simple automations.
By delegating these tasks, we protect what keeps us curious. We want to remain the ones imagining new ways to solve complex problems and debating solutions on a whiteboard (whether physical or digital).
A journey in progress
We don’t use AI to set the pace of our work, but to accompany it. The intention is for it to remain in a strategic background: useful and available, but never decisive. At the end of the day, what we are passionate about in software development isn’t just delivering a product, but the thought process behind it. In that process, curiosity remains the primary engine.