Hi and welcome. I’m a creative technologist who loves helping people shape and build their ideas into useful websites and web tools.
I specialize in bridging minds from various backgrounds, such as design and engineering; arts and technology.
One of my favorite aspects of my work is witnessing someone’s excitement when I show them a new tool/fix/improvement that resolves a problem they had.
For my day job, I work as technical program/product manager and oversee web development to support corporate marketing teams.
I also run a solo consultancy to provide web/CMS/tech services for individuals, small businesses, and larger corporations.
Over the years, I've become more passionate about helping people improve data privacy and accessibility initiatives.
Even when I'm “off the clock” as it were, I'm that person who will look for and read the privacy policy to see how my data will be shared (and how/if I can opt out). I'm that person who will often increase the text size by 120% (at least) in my browser to make the site more legible on my screen.
I love designing products and features that add value and make websites easier to use for more people.
Who likes websites that are frustrating to use? Yet there are so many out there.
Wouldn’t it be nice to find the information you need without having to guess where to go?
Wouldn’t it be cool to go Back a page and not lose your place?
Wouldn’t it be great if the text displayed on your phone was in a legible font size — or even better — legible font size and color?
Planning for better accessibility is an important step in improving usability in general.
Accessibility shouldn’t be considered a niche supplementary idea for a product; it should be part of the foundation to allow more users to use and benefit from the product.
For one way to look at web accessibility and how it dovetails with design, check out 10 Design Topics to Consider, which I wrote as a starter set of specific questions to ask about website design.
I believe in QA from start to finish.
A lot of people say “QA” when they mean “testing.” In this case, I mean QA as in checking for and improving quality in processes throughout all areas of a project, including testing.
The smoothest projects I’ve worked on have all included time to iron out sensible QA workflows — not only within engineering, but also requirements, designs, documentation, and communication in general.
It’s also important to consider a project from a wide angle, in addition to the finer details in the stages in between.
There’s the saying “Measure twice, cut once.”
There’s also “Measure seven times, cut once.”
In my experience, there’s no be-all, end-all methodology or process, because every project has its own unique quirks.
Sometimes measuring twice is perfectly fine. Maybe measuring seven times is excessive, but four times is not.
Sometimes agile makes sense; other times, it doesn’t. Sometimes waterfall doesn’t make sense; and other times, it does.