Hi, I am
Michael Hastrich
Freelance front-end developer

I am passionate about the accessible web, semantic markup and cascading style sheets. On this website I’ll share some of the projects I’ve worked on and some of my thoughts about earlier mentioned passions. If you want to get in touch, just drop me a line on hi@michaelhastrich.nl.

Things I do best

Front-end development covers so many different skills that I'd like to emphasize what I'm good at and what I care about. If you are looking for someone to help you set up a maintainable and solid codebase, maybe I can help. Below are the things I care most about in my work.

  1. Design

    I have had the pleasure of working with a lot of different designers over the years. I speak their "language" and get why details like line-height and white space are important. I understand that sometimes an extra variant of a header is necessary to make a component stand out a bit extra. I love to sit down with designers to discover systems within their ideas and shape those ideas into a design system that we can use in (almost) every context and use-case.

  2. Inclusiveness

    I believe it's essential that whoever visits a website or uses an app to do something, is able to do what they came to do. Regardless of their abilities. In practice what that means, is that I try to make my work as accessible as possible. Whether someone uses a keyboard to navigate the website or uses assistive technology like a screenreader, my goal is to make the experience as seamless as possible for as many people as possible. I ensure that by writing clean and semantic markup, keeping an eye on document structure, sticking with native components as much as possible and working closely with designers to come up with solutions that work for everyone.

  3. Maintainability

    I like simple solutions that make sense to people. That means I like to keep my tool chain within a project as lean as possible. Do we really need Bootstrap or Tailwinds? Why do we write a bunch of mixins that are used only once or twice and nobody understands anymore 2 months down the road? And if we decide we actually do need them, let's document them as best as we can, so the next developer or our future-selfs at least have an understanding of what the problem was we were solving. Removing 'the magic' from a code base gives me great pleasure.

  4. Usability

    Making sure your visitors understand what they need to do on your website to get what they came for. That sounds logical. Unfortunately that is not always the case for a lot of digital products that exist today. Of course UX designers play a huge part in this, but I do feel it's my duty as a front-end developer as well to keep a broad view of the elements in a project and how they behave. "We already have something that does something similar. Maybe we could use that, instead of adding a new, slightly different, thing?"

Previous projects

Over the years I've worked on a variety of projects for clients ranging from design agencies to the national airport and Dutch government. Usually I'm the person responsible for markup and styling, setting up and maintaining component libraries and safe-guarding usability and accessibility.

Would you like to team up?

Do you want to know more or find out if I could be a valuable addition to your team and the product your working on?

Simply send me an email or connect on Linkedin. I'm more than happy to drop by your office for a coffee and to answer any questions.