Good Kaizen – Laravel
A blog about doing good and getting better at life, code, design, and business. We do our best to write in a way that clients will find valuable.
Kaizen is the practice of continuous improvement.
Recently the Zaengle team was asked to look over an existing Laravel application and give a review of the overall state of the code. We were to act as an independent third party, between a new studio who had inherited the codebase, and the client, who was anticipating launching the product. The studio had some concerns about the quality of the code and wanted an independent review prior to picking up development on the project. Here are a few thoughts on the process I followed and several takeaways I had from the experience!
Earlier today I was working on coding up a design that displays a varying number of cards, each with a unique title and description think masonry/pinterest-esque. I’ve been using Faker to stub out a bunch of cards, each with different content. Once I’d hooked up the dummy data to the cards, I realized that the design didn’t work as well with titles that had more than 20 or so characters.
Unbeknownst to their audience, technical teachers must walk a very fine line. Without realizing it, readers put a lot of faith into the teacher. After all, they must be on the path ahead of the reader, drawing from their experiences, and distilling down the parts they feel would benefit students the most.
If you are anything like me, you view new projects as an opportunity to stretch your abilities, tackle a challenge, and improve your coding. This blog entry is an attempt to share a few items that stood out to me on one of Zaengle's Laravel integrations. Hopefully this will stimulate your thinking as you find creative solutions for similar problems!