Ioncube decoder and SourceGuardian decoder service
Put Drupal glasses or masks on any image using the rokka.io image service:
https://rokka-fun.liip.to/drupal
Make sure to share using twitter using the #CelebrateDrupal hashtag.
Thanks to Christian Stocker for swiftly implementing the idea on rokka.io and Nico Grienauer for providing the gimmicks.
The concept of decision entails a sense of finality. Often decisions feel like a Rodin sculpture: once for all perfectly cut. How terrible and scary is that? No wonder that many refrain from taking (major) decisions.
Can’t we remove this sense of fate and rigidity from decisions and turn decision-making into a lighter thing?
Does that decision feel too big? What could be a smaller decision in the same direction that is safe enough to take? Find it and take it. Breaking up a big decision in a series of small decisions often helps to move forward. “One Fear at a Time”, as John Whitmore writes in Coaching for Performance.
Be it fear or decision, breaking it up in smaller pieces also allows you to adapt the course of action.
Make explicit the fact that the decision has been taken based on finite knowledge of a situation and thus corresponds to a local optimum. Finish any decision statement, with : ” … until we know better”.
Shouldn’t we wait then, to take better decisions? Sometimes yes. Gathering more info, giving it more thoughts is always an option. There however always comes the time when Pareto’s Law kicks in, a point beyond which an imperfect decision will show greater ROI than a more perfect one.
A great question I make use of to ease my clients in taking virtuous yet still uncertain steps: “Is it safe enough to try?” Often it is. Often, this question eases the “fear of final decision”.
So decide to try, before finally deciding– if you still believe that you will have to decide once for all.
Since a decision is made at a certain point in time in a certain context and based on finite knowledge, it seems only fair to review it later down the road, doesn’t it? Fair and definitely smart. Even more in the case of a decision declared as a temporary one, like a pilot.
Define a revision date or install the license and/or duty to revise a decision when the need or new knowledge arises.
This works particularly well for any structural or strategic decision. Imagine how fit your organization would be if every agreement in it was due to be revised! Well, the distributed governance scheme of Holacracy makes it possible for anyone to trigger revision of the governance and Sociocracy 3.0 also advocates regularly reviewing agreements.
To go one step further down the road, I dream of an organizational system where decisions that are not revised get dropped, like an expiry date for anything decided, in order to keep organizational mass as low as possible.
Just as a local optimum will make sense for most cases around, there will be exceptions. Let them be and shine on the light of the decision. No exception should be hidden, for hiding exceptions calls to rigidify the decision even more.
On the contrary, collecting exceptions to any decision seems to me like a good practice— I yet still have to find a domain where this happens. Every exception enriches the understanding of the decision, sharpens the scope and effects of the decision, and brings material for further revision of it.
This list is not exhaustive, it simply exhausts my current thoughts on the topic. I yet decide here and now to share it with you as such. Definitely safe enough. And the digital medium gives me the license to revise it later down the road 😉
I hope this gives you a few concrete ways to take the next decision with a bit more joy and serenity.
Another monthly update where I explain what happened with Xdebug development in this past month. These will be published on the first Tuesday after the 5th of each month.
Patreon and GitHub supporters will get it earlier, on the first of each month.
You can become a patron or support me through GitHub Sponsors. I am currently 82% towards my $1,000 per month goal. If you’re already supporting Xdebug’s development, could you do me a favour and tweet this out?
Using @xdebug? Help its developer @derickr to get to 100% on his GitHub sponsors goal: https://github.com/sponsors/derickr #Xdebug3
If you are leading a team or company, then it is also possible to support Xdebug through a subscription.
In December, I worked on Xdebug for about 46 hours, with funding being around 30 hours. I worked mostly on the following things:
A few bugs were found in Xdebug 3.0.0, which should not come as a surprise, as with any big .0 release, users always find things that go wrong. December saw the 3.0.1 release, and the 3.0.2 released followed in the new year.
Xdebug 3.0.1 fixed several crashes and other bugs that are present in Xdebug 3.0.0. The crash when removing a breakpoint (or run-to-cursor) was the most notable fix in this release.
You’ll have to wait for the January 2021 wrap up to find out about the 3.0.2 release, or you can have a look at the release announcement.
There are also new release of PhpStorm and the VS Code Plugin to address a few Xdebug related issues from their sides. On top of that, the GitHub repository of the VS Code Plugin has been moved to the Xdebug organisation. There is a back log of pull requests and issues that need looking at.
I have started making videos to introduce Xdebug 3 and how to use it. The first one on Xdebug 3’s modes can be watched on YouTube.
I am currently working on a video to explain all the new features in Xdebug that help you find problems with running Xdebug itself.
I have been continuing to test Xdebug Cloud, and I am working with a few private alpha testers. They’re putting the hosted Cloud service through its paces.
At the same time I am working with a designer to make the https://cloud.xdebug.com look pretty too.
If you want to be kept up to date with Xdebug Cloud, please sign up to the mailinglist, which I will use to send out an update not more than once a month.
In December, no new supporters signed up, but I would like to thank Automattic, CHECK24, e3N, Edmonds Commerce, Find My Electric, Intracto, JetBrains, Private Packagist, Seravo, Strategery, Supermetrics, TYPO3 GmbH, and Tideways for their support during 20
Truncated by Planet PHP, read more at the original (another 629 bytes)
Object properties, part 2: Examples
In my last post, I went over some of the pros and cons of various proposals for making PHP objects more immutable-ish, and the contexts in which they would be useful. I also posted the link to the PHP Internals list, where it generated some interesting if meandering discussion (as is par for the course on Internals).
One of the requests was for sample code to demonstrate why I felt particular feature proposals were better than others. Fair enough! This post is in response to that request, and I think it will help illuminate the challenges better.
For this exercise, I chose to experiment with a junior version of the PSR-7 request object as a concrete example. The code below is not exactly PSR-7; it’s a representative sample of portions of a naive, slightly reduced scope version of PSR-7 requests only, and using all PHP 8.0 features available. The goal is not a complete working object, but sufficient real-world representative examples of situations that an immutability plan would need to address.
Continue reading this post on PeakD.
Larry
9 January 2021 – 6:33pm
I’m very happy to be speaking at The Online PHP Conference this year. As you can guess from the title, this is an online event so is easily accessible right from your desk.
Sebastian, Arne, and Stefan are acknowledged experts in PHP development and so an opportunity to hear their thoughts is always welcome. In this case, they have also invited a number of us to share our thoughts as well, expanding on the topics covered. It should be a good event and I encourage to buy a ticket and attend.
One area where I’ve found in-person events have the edge on virtual ones is the so-called hallway track where speakers and attendees can interact in ad-hoc conversations. I’ve always had really good conversations where I can ask and answer interesting questions and we learn things in a more informal setting. So, I was excited to discover that thePHPCC have thought about this.
From A Happy New Year 2021:
In addition to presenting much more (and more diverse) content than last time, we have made our already famous Hallway Track even better, allowing for more informal exchange between attendees and speakers. This is definitely something to look forward to. After our first edition of The Online PHP Conference, many attendees said that taking part in the Hallway Track almost felt like attending a conference in person.
I’m intrigued!
thePHP.cc have very kindly made available a couple of tickets to me that I can give to you! All you need to do is email me with your first name and last name. On Monday 11th January, I’ll pick the winners at random. I’ll delete your email afterwards and of course I’ll only email you if you win.
If you don’t win, get your company to buy a ticket anyway!
Ever since I’ve migrated to Kubernetes I’ve been working on a
Matomo Helm chart. Part of that Helm chart is having autoscale it on how
busy PHP FPM is, a.k.a. the percentage of busy workers.
Object properties and immutability
There has been much discussion in recent weeks in PHP circles about how to make objects more immutable. There have been a number of proposals made either formally or informally that relate to object property access, all aimed at making objects safer through restricting write access in some way.
Since my last mega post on PHP object ergonomics was so well-received and successful (it resulted in both constructor promotion and named arguments being added to PHP 8.0, thanks Nikita!), I figure I’ll offer another summary of the problem space in the hopes of a deeper analysis suggesting a unified way forward.
Continue reading on PeakD
Larry
28 December 2020 – 5:30pm
In this blog, Laminas Project Development Lead Matthew Weier O’Phinney breaks important milestones in the first year of the Laminas Project
Join us for an overview of the new PHP JIT compiler, including insights on performance impact and development considerations.
Another monthly update where I explain what happened with Xdebug development in this past month. These will be published on the first Tuesday after the 5th of each month.
Patreon and GitHub supporters will get it earlier, on the first of each month.
I am currently looking for more funding, especially now some companies have dropped out, and that GitHub sponsors is no longer matching supporters.
You can become a patron or support me through GitHub Sponsors. I am currently 73% towards my $1,000 per month goal.
If you are leading a team or company, then it is also possible to support Xdebug through a subscription.
In November, I worked on Xdebug for about 72 hours, with funding being around 30 hours. I worked mostly on the following things:
The biggest thing this month is the release of Xdebug 3!
After about a year and a half after starting with this massive undertaking, it is finally ready. I released it the day before PHP 8 came out. Of course Xdebug 3 also supports PHP 8. It however drops support for PHP 7.1 as per the support policy.
As is custom with a x.0.0 release, a few bugs did occur. I am currently working at addressing then. I plan to release bug release versions weekly throughout December, as long as it makes sense to do so.
Xdebug 3 should be a lot faster, as it is a lot more clever on when it hooks into things it needs to do. That does come with changes as to how Xdebug needs to be configured. Xdebug 3’s upgrade guide lists all the changes.
The https://xdebug.org web site now only contains Xdebug 3 documentation, with the old site archived at https://2.xdebug.org until the end of 2021.
I will be recording some videos about the ideas behind the changes, and how to use Xdebug 3. I am also playing with the idea of hosting “Office Hours” for an hour a week where users can drop-in with questions and problems. If that is something that you’re interested in, please let me know.
I have been continuing to test Xdebug Cloud, and I am working with a few private alpha testers. They’re putting the hosted Cloud service to its paces with the latest PhpStorm 2020.3 release candidate. As I suspected, the alpha testers found some minor issues which I will be addressing during December.
The web site for Xdebug Cloud does not have a design yet, but this is coming this month as well.
If you want to be kept up to date with Xdebug Cloud, please sign up to the mailinglist, which I will use to send out an update not more than once a month.
In November, two new supporters signed up.
Thank you Find My Electric and Edmonds Commerce!
If you, or your company, would also like to support Xdebug, head over to the support page!
Besides business support, I also maintain a Patreon page and a profile on GitHub sponsors.
_(titel_op_object),_RP-F-F08299.jpg){kind=link}