Ciao, I'm Davide, and welcome to my beyond-the-resume page 🥁!

I'm currently working at Kindly as a Fullstack/Frontend Developer, creating the world's most loved AI agents.

Read along to learn more about me, and how I work.

Originally from Italy, I've called Oslo my home for the last six years. Soon after moving, I discovered a passion for coding. For two years, I taught myself to program while working full-time, a journey that launched my career as a professional developer four years ago.

What defines me as a developer is my relentless curiosity. I'm driven to ask why, questioning assumptions and challenging the status quo to uncover the real problem. My most fulfilling moments come from tackling challenges across the full stack, rethinking solutions, and finding better ways to meet users' genuine needs.

My goal is always to build software that's technically excellent and genuinely delightful to use. When I'm not at my keyboard, you'll find me embracing the Norwegian outdoors and exploring nature.

Tech I Use

I began my career focused purely on frontend development, but over the past few years, I've evolved into a full-stack developer, working across a variety of projects. Today, my interest spans the entire technology stack, and I'm always eager to dive into new tools and frameworks.

Technologies I use daily: TypeScript, React, Styled Components, Node.js with Express, MongoDB with Mongoose, Redis, Docker, Cypress, Playwright, Storybook, and more.
Also familiar with and using: Python, Django, PostgreSQL, Google Cloud Platform, Elasticsearch, CircleCI, GitHub Actions, and more.
Excited to explore: Go, React Native, and more.

Personal Projects

By now you've probably noticed: I love experimenting with new technologies, getting excited by the latest tech trends (even if just briefly), and building tools that solve real-world problems. Here are some personal projects I've built and continue to maintain:

  • The BackTab Chrome extension. It displays a sleek, dark-themed interface with a list of recently visited tabs, each showing the favicon and title of the page. A search bar is prominently featured at the top, allowing users to quickly filter through their browsing history. The overall design is clean and intuitive, emphasizing ease of use and efficient navigation.
  • The Kindly Pronto CLI tool. The command-line interface is shown in action, with colorful, easy-to-read output. It displays a list of deployment options and status updates, highlighting the tool's user-friendly design. The clean layout and clear information hierarchy make it easy for developers to manage releases and deployments efficiently.
  • The Henrikke Havaas artist portfolio website. It features a minimalist and elegant design, with a clean layout that showcases the artist's work. A beautiful, high-quality painting is prominently displayed, with a simple navigation menu and text overlay. The overall aesthetic is modern and sophisticated, reflecting the artist's creative style.

How I work

My PR Philosophy

I strongly believe that clear, well-crafted PRs are essential for a productive and collaborative engineering team. My code and PRs are always written keeping in mind that my colleagues are the audience: I'll make sure the what and the why is clear, and that the code is well-tested and follows the project's coding standards.

  • Example of a well-crafted PR description. A GitHub pull request with a clear and concise title, a detailed description of the changes, and a checklist of tasks to be completed. The description includes a summary of the changes, the motivation behind them, and instructions for testing. The PR is well-organized and easy to follow, making it simple for reviewers to understand the proposed changes and provide feedback.
  • Example of a well-crafted PR description. A GitHub pull request addressing a bug in the breadcrumbs component. The description clearly outlines the issue, the steps to reproduce it, and the proposed solution. It also includes a before-and-after comparison to visually demonstrate the fix. The PR is thorough and well-documented, making it easy for the team to review and approve the changes.
  • Example of a well-crafted PR description. A GitHub pull request that fixes a bug in the Kindly chat carousel. The description provides a clear explanation of the bug, the steps to reproduce it, and the implemented solution. It also includes a video demonstrating the fix in action. The PR is comprehensive and well-presented, making it easy for the team to understand the issue and verify the solution.
  • A GitHub pull request that fixes a bug in the Kindly chat banner message.
  • Example of a well-crafted PR description. A GitHub pull request that fixes a bug in the Kindly chat scrolling on Android.

Ensuring feature success

I am by nature a very tidy and organized person. I try to document everything that I do and that can be useful to others. Furthermore, I often like to create dashboards and graphs to visualize data related to the changes that we make, making it easy for the entire team to understand the impact of our work.

  • Example of a feature success tracking graph. A Grafana dashboard with a series of graphs and charts visualizing the impact of a new feature. The dashboard tracks key metrics such as user engagement, conversion rates, and performance. The data is presented in a clear and easy-to-understand format, allowing the team to monitor the success of the feature and make data-driven decisions.
  • Example of a feature release plan. A detailed release plan for a new feature, outlining the various stages of the release process, from development and testing to deployment and post-release monitoring. The plan includes a timeline, a list of tasks and dependencies, and a communication plan. The release plan is well-structured and comprehensive, ensuring a smooth and successful feature launch.

What I enjoy

If time allows, I genuinely enjoy writing good quality software, and not just ticking off a task as soon as possible. I also love writing documentation, and collaborating with others, whether they are part of my team or not.

My motto is "Leave the code in a better state than you found it". I know perfect code doesn't exist, but whenever I touch something, I make sure I do small improvements here and there, even if unrelated.

Always Learning

I believe great developers never stop learning. Whether it's through online courses (I usually average 3-4 Frontend Masters courses per year), hands-on projects, or reading deep dives on engineering blogs, I continuously invest in my growth and I hope the company I work for can help me do so.

×