About Thomas

I build for the web with purpose and precision.

I'm Thomas Hondo Chacha, a software engineer from Kenya focused on modern websites, interactive applications and practical digital solutions.

Independent practice Based in Kenya
Portrait of Thomas Hondo Chacha in a computer lab, wearing a cap and badge that read Software Engineer.
Thomas Hondo Chacha Software Engineer
Kenya
Name
Thomas Hondo Chacha
Based in
Kenya
Focus
Websites & web applications
Languages
English · Kiswahili

Who I am

A builder with an eye for the whole picture.

I work across software engineering with a focus on front-end development and practical web systems. I enjoy the part where a real problem becomes a clear interface: structuring content, shaping interactions and making sure the result behaves well on every screen.

My foundation is semantic HTML, responsive CSS and vanilla JavaScript. When a project needs server-side logic, I work with Node.js, Express and PostgreSQL, and I connect interfaces to supported APIs where it makes sense.

I'm not interested in showing off the longest list of technologies. I choose tools that suit the problem and place the emphasis on clarity, accessibility and code that can be maintained.

Thomas Hondo Chacha

Software Engineer

What I build

Digital products with a clear job to do.

The technology should serve the purpose. These are the kinds of problems I focus on.

Modern websites

Responsive, content-led websites that help businesses and organisations explain who they are and make the next step obvious.

Interactive web applications

Browser-based tools shaped around a workflow — structured input, understandable interfaces and useful feedback.

Practical improvements

Redesigns, responsive fixes, accessibility improvements and technical clean-up for existing digital products.

How I approach projects

Thoughtful decisions, not decoration.

A good interface should feel obvious. Getting there takes careful thinking.
Thomas Hondo Chacha · Working principle
01

Understand before building

I ask about the audience, the content and the outcome before settling on a layout or a technical approach.

02

Simplify the path

Clear hierarchy and direct language usually do more for a project than another visual effect.

03

Build responsibly

Semantic markup, responsive styles, accessible controls and readable code are part of the work, not extras.

04

Test and refine

I test the actual experience on different screen sizes and fix the details that get in the way.

Technologies and tools

Fundamentals, used with intent.

I work with a focused set of tools. There are no proficiency percentages here — the projects are the evidence.

Front-end

  • HTML5
  • CSS3
  • JavaScript
  • Responsive design
  • Accessibility
  • Semantic HTML

Back-end

  • Node.js
  • Express
  • PostgreSQL
  • REST APIs

Workflow

  • Git
  • GitHub
  • VS Code
  • Browser dev tools

Integration

  • API integration
  • JSON
  • Forms
  • Third-party APIs

Currently exploring

Still curious.

The work gets better when the learning continues. At the moment I'm spending time with:

  • Modern CSS layout, custom properties and interface systems
  • Accessible interaction patterns and keyboard-first design
  • Full-stack JavaScript and cleaner API boundaries
  • Performance-minded front-end architecture

Next step

Have a project in mind? Let's make it real.

Tell me what you're building or improving. We can start with a short, no-obligation conversation about the problem, the scope and the right way forward.