I've been doing full-stack development using Laravel since 2015 — that's 9 years of learning new things every day, so far. I work at Whitecube, and we like to take on challenging projects where we build bespoke solutions to the specific problems our clients face. This has lead me to a lot of rabbit-holes of searching for and learning new tech solutions. And in doing so, I've learned the importance of using the right tool for the right job, and how it's sometimes easy to pick the wrong one and have it come back to haunt you later.
Which brings me to the purpose of this blog; Riveting Research.
It's a series of articles hosted on this blog that aim to do deep-dives on highly specific tech questions. Most of the time, this means comparing two (or more) solutions for one problem and figuring out the pros and cons of each, so that hopefully, when you or I face the problem, we can make an educated decision on which path to take.
Since I do full-stack work, these articles will cover a bit of everything, be it interesting front-end techniques, noteworthy back-end design patterns, or obscure server and database configuration options.
My hope is that by writing these, I will be able to reference them later myself, but I also would love for them to be useful to other people. If you've come across one of the articles and found them useful for something you're working on, I'd love to hear about it! You can tweet at me or send me an e-mail using the contact link in the menu.