“Your present identity should not constrain your future habits”.
For this quote from the audio book “Hello, Habits“. Obviously the book is about ‘habits’, but the phrase could easily have been “Your present identity should not constrain your future self”.
In either reading of this, it’s been stuck in my head for while now.
How does this phrase land with you?
I stumbled on an article from Matt Galligan about the initial versions of Cir.ca, a news aggregator app from a few years ago that recently closed up. So the article talked about many of the design ideas they had, and the struggles they worked through before changing or abandoning some ideas. This is an example…
This has been a thorny issue for a while, and *may* have been resolved in Laravel 9 (have not upgraded projects to 9 yet). Testing both that an email was triggered in a Laravel test, as well as verifying the content of the mail body – that has often seemed to be a tricky step….
Have been needing to programmatically fill out an I9 PDF, retrieved from gov site. Should be fairly straightforward, right? Well… the field names are… a mess. Field names like topmostSubform[0].Page1[0].U\.S\._Social_Security_Number__Last_4_numbers_[0]topmostSubform[0].Page1[0].expiration_date__if_applicable__mm_dd_yyyy[0] topmostSubform[0].Page2[0].Employers_Business_or_Organization_Address_Street_Number_and_Name[0] and so on make it pretty… not straightforward to create a usable key/value combination to search and replace. But… today, I noticed it got…
I get an email newsletter from Martin Joo every week or so. The newsletters generally have some useful tips around the Laravel framework or sometimes just general development tips. I’ve learned a couple of neat tricks here and there, and will continue to receive. This morning I received an email with a Laravel ‘tip’ regarding…
Small note, mostly for myself, as a reminder that when doing large imports of data, you may not need each block to be processed as an Eloquent model. That code above would generally be faster as Obviously there are even faster ways – preparing your data in some text format, and using your DB cli…
phpinsights is a tool you can use to get a nice overview of the quality state of a PHP project. The tool will analyze the code, complexity, architecture and some code style rules, then present four corresponding scores. Measuring over time will give you a sense of which areas of your code are improving, and…