Hi, DEV! I’m Juan Pablo Abadía Medina, a full-stack developer and technology entrepreneur from Valle del Cauca, Colombia.
I founded Blockchain Technology S.A.S. and created Ponwi and Ponwi Academy. My work brings together software development, blockchain, AI, and technology education.
For my first post, I want to introduce the questions I’ll explore here—and hear what other developers are working on.
From an idea to a maintainable application
An idea can sound straightforward: verify a certificate, automate a report, or help people understand public information.
Building it raises more questions:
- Where does the information come from?
- Who can create, change, or verify a record?
- What happens when an external service becomes unavailable?
- How will someone correct a mistake?
- Who will maintain the application after launch?
I’m interested in the decisions behind those answers, including the tradeoffs that rarely appear in a product demonstration.
What I’ll write about
Blockchain and Web3
Smart contracts, application integration, verification workflows, and the practical responsibilities of operating blockchain infrastructure.
I want to explain what each component contributes and which assumptions still depend on people or organizations.
AI and automation
Workflows that reduce repetitive work, with attention to input quality, human review, and failure handling.
For example, an assistant that drafts a report still needs a clear source of information and a way for someone to check its output.
Full-stack development
The connections between interfaces, APIs, databases, and infrastructure—and the debugging that happens between them.
I plan to share focused examples, explain implementation choices, and document limitations.
Public innovation and citizen participation
I’m also interested in software that helps people understand information and contribute to public processes.
A useful starting question is: can a person understand what the application shows, take a meaningful action, and find out what happened afterward?
A small exercise before starting a project
Here is a project brief I find useful:
We are helping [a specific user] complete [a specific task].
Today, they struggle with [an observable problem].
We will evaluate progress through [a measurable outcome].
The first version will include [a limited scope].
Someone will be responsible for [review, support, and maintenance].
Consider a hypothetical reporting tool:
We are helping a small business owner prepare a weekly sales summary. Today, they manually combine several spreadsheets. We will measure preparation time and correction requests. The first version will import one agreed file format and produce a draft for review. The owner will approve the report before sharing it.
That brief gives a developer something concrete to investigate. It also creates room to decide whether the task needs a script, a conventional web application, an AI component, or another approach.
Let’s connect
I’m here to exchange ideas, learn from other builders, and contribute practical explanations.
What are you building right now—and which technical decision has been hardest to make?
You can find my work here:
Top comments (0)