My name is Adam Roesner, I am a Full Stack Web Developer based in Richmond, VA who is passionate about building cool things that make people happy and learning all there is to know about my field. Let's build something together!
What do I do? Take a look at some of the tools that I use for front- and backend development and deployment:
Projects
A promotional site for a social media influencer built in collaboration with the influencer themself. This project was exciting to me as it offered the opportunity to solve a lot of different problems: they wanted the phones to be clickable and to display screenshots of their actual video content (solved using css); they also wanted their metrics to update automatically. To solve the latter problem, I created a database and an authenticated api that the site fetches data from, and which I can scrape and upate data to automatically.
I took this project over from a contract agency when I joined a local nonprofit as their sole web developer (and IT admin). I received some theme files database records from them, but there was still a lot to do before the site was ready to launch. I integrated the donation page with our CRM platform, automated email receipts and created a database of donor information, and reconstructed/reorganized about half of the site from what we got. My major challenge here was that I hadn't worked with Wordpress professionally and I needed to learn it while also deciphering what the previous team had done without being able to really ask them any questions. Thankfully, I have years of experience of figuring out what other people's code is up to!
A blog site built with some of my colleagues front-to-back. Initially we chose to build it using Vite and React, but due to some concerns about routing and performance we decided to migrate the project to NextJS and see what all the hype was about.
To be deployed soon . . .
I built this API for a frontend site that needed data to be updated automatically, and after shopping around at different options I realized that including the webscraper in the frontend was just too heavy and not resource efficient. I decided to build the api so that I could separate out my front and backend concerns, and I expect to use this individual api for more databases in the future. At the moment, the frontend is not pretty but I expect to add something there soon.