Full-stack software engineer working in health tech by day and looking to provide value to the tools we use everyday.

Most used development stack includes Vue.js, typescript, CSS, ASP.NET, and MSSQL but its important to seek alternatives when it makes sense. Also, always be learning!

There was a time when web browsers were lacking the native features to work efficiently and effectively. Many large and useful frameworks were developed to help with this. Those days are coming to a close and the large component frameworks are just not needed.

I can't count the number of times I have said, if the HTML select was just a little more customizable then we wouldn't need to pull in a framework at all. We don't need a framework or component library to build an HTML button for us. With the select menu element on its way we are as close as ever.

Another example is a data grid component. Why do we have to pull in a framework that has button and input components just to get a data grid component. I have also found that while the available data grid components are technically written in native Vue they were still ports from JQuery or React versions and thus just didn't have some of the design considerations you would expect for a native Vue component. I have started the data-grid-vue project to be a fully customizable data grid with very few dependencies that is both designed and implemented for Vue. In the feature maybe it gets converted to a web component for use with React, Angular, etc. but for now its intended to be a Vue data grid component.