A big part of my work has to do with code. I’ve worked as system administrator – installing, patching, and configuring someone else’s code. I’ve worked as independent programmer, writing code on my own. I also programmed as part of the team. And on top of that, I worked as Team Leader and Project Manager, where I had to interact a lot with programmers. Programming world on its own is as huge as the universe. There is always something to learn. When I find something worthy or something that I understand enough to write about, I share it in this category.
“State of the Word” is a big thing for anyone who is involved with WordPress. This year’s “State of the Word” is even more important, following the release of WordPress 5.0 and the switch over to Gutenberg editor.
If an almost one hour talk is too much for you, then read through the Post Status summary of the talk with all the highlights and useful links.
spatie/period is a PHP library that provides complex period comparisons. It implements a variety of methods for calculating gaps, boundaries, overlaps, and other operations on multiple dates.
Password Exposed Helper Function is a tiny PHP library that helps checking user passwords against the Have I Been P0wned website API.
This is quite common new functionality on many websites and services (see GitHub, for example), which is now available as a quick composer dependency for your PHP projects.
“Advanced web security topics” blog post goes over a variety of ways that a web application can get p0wned. Some of these include:
There’s a lot of confusion between git merge and git rebase even among seasoned users of git. “An Introduction to Git Merge and Git Rebase: What They Do and When to Use Them” is a great article explaining the pros and cons of each, and when and why using each of this is better.
While I understand it a lot better now, I still much prefer the merge approach. It’s simpler and less dangerous, and maintains the full history. This might get noisy at times, but works as a last resort when trying to understand what was going through the developer’s head when he was working on a piece of code.