I'm going to write about my experience so far and share a link when the post is live. In the meantime, check out the Rust Documentation guide to get started: doc.rust-lang.org/stable/
Posts by Matthew Setter
To me, this is a significant plus for learning the language, one that should make the life of any developer who's new to Rust significantly easier.
If you haven't considered documenting your Rust code, yet, I strongly encourage you to do so.
All you need to know is a little bit of Markdown and 5 - 10 minutes to learn how Rust documentation works, and you can be creating beautiful, thorough documentation, just like in any Rust package you've used, or the official documentation.
The quality of the tooling and related documentation is simply excellent. What's more, you don't need to install any extra, third-party tooling; I'm *not* knocking third-party tools, btw.
You don't even need to learn much at all, if you've documented code before (we all have, right?!). π€
A screenshot of Rust documentation.
As part of learning Rust β and being a lover of documentation (I π the docs) β today, I dove into learning how to document Rust code.
You can see an example of what I've created so far in the screenshot attached to this post.
To say that I am impressed by what I found would be an understatement!
Do I know a professional Rust developer who could critique some Rust code I wrote?
The tutorial, currently, does not address considerations such as concurrency and scalability, as it was intended as an encouragement to get started, rather than a best practice guide.
However, I'll be updating it shortly to encourage considering these considerations.
Thanks to PHP's wonderful Image Magick extension, it stores metadata alongside the actual image, such as the height, width, size, depth, and density, as well.
Sound like something you'd like to build?
Then jump in to the tutorial: lnkd.in/gdNJ9mSh
If you're storing images with your PHP apps, then here's a tutorial from my Twilio tutorial archive that shows how to build a simplistic API with PHP which supports uploading, deleting, and viewing images, storing them in a SQLite database.
One way is to store them in a database, such as the legendary SQLite. It's a single file database which is easy to work with β especially when you're using the incredible Doctrine project.
If you use images in your PHP applications, where do you store them?
In the server's filesystem? In attached storage? In an AWS Bucket?
I still don't fully understand Rust references. π₯
But, "Beginner's guide to Rust references" (dev.to/wrongbyte/ru...) has done an excellent job of helping me better understand them. π
If you're struggling with them, do yourself a favour and read this post!
If you need to send bulk SMS with PHP, here's a short(-ish) tutorial that I wrote for the Twilio blog showing how: www.twilio.com/en-us/blog/d....
I hope that it helps. Let me know if there are any issues.
But what about sending SMS in bulk?
It's no harder than sending SMS individually or to small groups. IMO Twilio makes it dead simple. Srsly!
I wrote a short post showing how to send SMS in bulk using plain old PHP (aided by the Slim Framework), powered by Twilio's Messaging Services.
The accompanying image to the tutorial: "Send Bulk SMS With PHP and Twilio". There are two key icons within the image, both in white circles. On the left is an SMS icon. On the right is the PHP mascot: ElePHPant, facing left.
There are a wealth of ways to communicate with customers in 2026. But, sometimes, nothing beats a good old-fashioned SMS!
Why:
- The recipient doesn't need an internet connection
- SMS are delivered almost instantly
- SMS works on every mobile phone
I've been writing tests for years in PHP. But, despite that, I know I've still got a lot to learn.
For example, appreciating the difference between stubs and mocks.
If you're the same, check out this article from Sebastian Bergmann: phpunit.expert/articles/tes...
I hear you! 100%.
I've been steadily reframing how I see development and tech from something "I do" to something that I know how to do, and something that I use to help others in some way, shape, or form. So long as I do the latter, I'm good. I hope that helps.
I hope that they help you if you're considering rebuilding a website, whether in PHP, another language, or with whatever technology stack that you care to use.
I tried not to go too deep into detail, rather to talk more broadly about what I learned. And, what I've shared may be missing some important points. But the ones shared are those that most came to mind.
So, in a rather lengthy post, I've shared the top 10 things that I learned: ππΌ matthewsetter.com/blog/item/le...
As I've been posting about recently, I recently rebuilt my main website in PHP using the Mezzio framework from the Laminas Project; a very valuable experience
Now that the new version's been out for a few weeks, I feel that it's time to share some of the key things that I learned.
While I was a Zoho (Books) user in the past, this was my first time using Zoho's APIs. It wasn't an easy process, but I sure learned a lot as a result.
I sincerely hope that the tutorial helps you out if you're looking to integrate Twilio and Zoho CRM.
A new Twilio (PHP) tutorial by yours truly is live!
It shows how to build a PHP-based application that can notify Zoho CRM meeting participants by SMS when theyβre involved in a new meeting or when details of an existing meeting change.
π www.twilio.com/en-us/blog/d....
Looks wonderful!
Recently, I stumbled upon Resterm, a terminal client for testing web apps and APIs, similar to Postman and Hoppscotch.
It's what I've been looking for for years!
So, I made a YouTube video to get you started with it: www.youtube.com/watch?v=-JwI...
Congratulations to the Python Foundation for staying committed to their principles: pyfound.blogspot.com/2025/10/NSF-...
Please donate if you can to help them help the broader Python community.
βWe believe many Microsoft 365 customers would have opted for the Classic plan had they been aware of all the available options.β
Sounds fair!
ia.acs.org.au/article/2025...
If you create developer video content (or video content in general), what's the experience like for you? Also, what software do you use and what are your pro tips?
I procrastinated quite a lot before diving into creating this video, assuming that it might be just as frustrating as previous times. Oh, how wrong I was!