I'm John Braun, living in The Netherlands. I'm a software developer working mostly with Laravel and created LaravelPackage.com as an open-source tutorial to PHP package development.
While I was in high school, I was already fascinated by programming; however, my interest in chemistry took over at a certain point. Chemistry: the science that describes the incredibly tiny particles that make up our world: from the air you breathe to your DNA and (unless you're standing) even the chair you are sitting on while reading this. My desire to understand how all of this works motivated me to dig deeper. After studying chemistry, I eventually got a chance to start my PhD research in Organic Chemistry.
During my time in the research group, I discovered the potential to enhance our workflow by creating custom-made tools. Since I had some experience in PHP, creating web applications seemed the obvious choice. Additionally, one of the vast advantages of web applications is that they're device-agnostic: it works in the browser and doesn't require any knowledge on building Android or IOS apps. On top of that, I learned that it is effortless to make the site look great on phones and tablets in the era of mobile-first applications.
Soon I discovered PHP was back in business as it had improved a lot since version 7, and a wide variety of frameworks had emerged.
One of these frameworks, Laravel, was getting more and more popular. Laravel's philosophy is aimed at developer happiness, which is immediately evident from the great documentation. On top of that, first-party companion tools like Laravel Valet (enabling fast, easy local development) and Laravel Forge (easy deployment of projects) really take away the hard work to develop and host your Laravel applications. In addition to Laravel's own solutions, I also want to pay attention to the fantastic people at Spatie, which create helpful packages and empower the Laravel ecosystem.
Additionally, I'll have to admit that the fantastic video tutorials by Jeffrey Way on Laracasts tremendously lowered the entrance barrier to Laravel and motivated me to just get started.
The first Laravel project I worked on was to improve our inventory database, holding a little over 2000 in-house chemicals. At that time, the software we used was sharing a Microsoft Access database file in a shared Dropbox folder. Everyone had reading rights (so they could search), and only our lab manager had the right to write changes to our database. Meaning that our lab manager needs to be notified for each update to persist the change (!).
Consequently, at our yearly 'lab cleaning', everyone would get handed out to them a printed list. Next, we would run through all chemicals on that list, checking if a chemical was still present, wrongly located, or consumed. In the latter cases, adjustments were added on paper, and the report would then be returned to our poor lab manager, whose task was to make all the changes in the actual database file. A horrible job, I aimed to eliminate by employing Laravel.
I'm proud that our research group now uses this chemical inventory application daily, offering a better experience for its users. Everyone can add, update and (soft) delete chemicals. The yearly "lab cleaning" now only takes 2 days, instead of a week and provides a simple wizard guiding the users through chemicals in a specific cabinet.
After programming this inventory database, I made a couple of other tools for the group, amongst others: a reservation system for booking our equipment, calculators for our NMR analysis, and a Supporting Info Manager (S.I.M.) for managing and automating writing up the Supporting Info section of our papers, based on the synthesized (new) compounds.
I re-experienced how fun and satisfactory programming can be, and I am eager to keep learning. Through this blog, I want to share tips and tricks for (beginning) developers.