Free PHPFree PHP scripts classes and info

Voices of the ElePHPant: Interview with Omni Adams

@omnicolor

Show Notes BeerCalc BrewerWall

Audio

This episode is sponsored by

The post Interview with Omni Adams appeared first on Voices of the ElePHPant.

Laravel News: Laravel Process Stamps Logs the Process Used to Update Models

                            Laravel Process Stamp is a package by Tom Schlick which makes it easy to track which process created or updated a model record in your database. 

            Visit Laravel News for the full post. 
            The post Laravel Process Stamps Logs the Proces...

425 Too Early

When a HTTP client makes a connection to a HTTPS server, it uses TLS to create a secure connection. TLS can have a bit of a complicated ‘handshake’ to establish the connection. Because there’s a bunch of back and forward, this can take a long time, especially when there’s a lot of latency between server and client.

There are ways for clients to optimize this setup by sending a bunch of data very early in the process, before the full TLS connection is completely setup.

In some cases this can cause security problems. In those cases a the server can tell the client to retry a specific HTTP request after the TLS connection has been fully set up

In these situations, it will return the 425 Too Early status code.

Normally, you would never have to deal with this status code as a developer, unless you are creating HTTP(s) servers from scratch.

References

• RFC8470, Section 5.2 - 425 Too Early

Changes

It was 6 years ago when I was last looking for a change after being a freelancer for a very long time. The idea was simple. I was tired of being the accountant, salesperson, consultant, developer, collections, sysadmin, and more. As a freelance “developer” I had to be all these things to support my family and live in a manner I was accustomed. But I was growing tired of it all, and wanted to have a little more fun by doing the parts I enjoyed most…consulting.

A good friend had been working at a well-known company for about a year and was very happy doing it. He also had grown tired of being a freelance developer, and a job at the company was his answer. So, when I saw an open consulting position on their website, I applied for it.

About a week later I received a call, then went through the typical round of interviews and questions. I was hired!

It was an exciting time, filled with learning new systems, people, and experiences. I was suddenly thrust into meetings with very large companies, and large teams of developers, who needed my help. There were new problems to solve on a weekly basis, and with each problem came new challenges. The number of things I learned during my six years of consulting at the company was mind-blowing, and with each day I discovered there was more and more I didn’t know. I basically went from knowing a bunch of things to village idiot overnight when I was hired.

“I went from knowing a bunch of things to village idiot overnight when I was hired.”

As I transitioned from one customer to another, it also led to traveling quite a bit. I spent half of each year away from home as I went onsite to meet new teams, learn network and application infrastructures, and build relationships with hundreds of people.

I continued to learn a great deal, and with each engagement, I spent less time on search engines and could draw from my own knowledge more often. (Of course, there was still a bunch of searching, but it was less. I’m still the village idiot learning daily.)

As a user group organizer, and speaker, I’ve always enjoyed teaching and sharing, and it was wonderful that my employer encouraged this activity. So I tended to share my knowledge with anyone who would listen, as I began speaking at conferences, user groups, and online from blog posts, podcasts, and videos, as well as through code via online source code repositories.

Through the process, I also did a fair amount of evangelism around products, libraries, and frameworks I believed in and witnessed some real growth from these efforts which drove me to do more.

However, as times change and acquisitions happen, so do the directions companies take. For good, or bad, companies are forced to make decisions and make changes to help them move forward and grow. I’ve witnessed and lived through some events these past couple years that have left me feeling dissatisfied and a little disconnected from the things I’ve come to hold dear.

This doesn’t mean the company is bad. It simply means our paths have diverged for the time being. Therefore, I will be leaving my current employer, as it is time once again for a change.

Community News: Latest PECL Releases (05.14.2019)

Latest PECL Releases:

• ds 1.2.9
  Fix segfault when iterating an implicit instance of Stack, Queue or PriorityQueue.

• datadog_trace 0.23.0
  **NOTE: We changed the way the service name can be configured. Now you must use `DD_SERVICE_NAME` instead of `DD_TRACE_APP_NAME` for consistency with other tracers. Usage of `DD_TRACE_APP_NAME` is now deprecated and will be removed in a future release.**

  Added

  • Support for Lumen 5.2+ #416
  • Tracing support from the CLI SAPI #422
  • Support for Laravel Artisan #422

  Changed

  • Now the way to configure service name is through DD_SERVICE_NAME instead of DD_TRACE_APP_NAME #432
• parallel 0.9.0
  - Channels: bi-directional communication between tasks and runtimes - Improvements to copying making it vastly more efficient - Improvements to runtime stack, making it more efficient - Tasks may use lexical scope - Events - an experimental, quite primitive event loop for reading/writing sets of channels and futures - Support for rethrowing exceptions uncaught in tasks - Simplified Runtime constructor - Remove Future::select (in favour of the superior events interface) - Task cancellation - Closure support - Drop support for PHP 7.1
• datadog_trace 0.22.0
  ### Added - Official support for PHP 7.3 #429 - Tracer limited mode where spans are not created to preserve resources #417

  Fixed

  • Error when a subclassed integration returns an object that cannot be cast as a string #423

Interview with Omni Adams

This episode is sponsored by

The post Interview with Omni Adams appeared first on Voices of the ElePHPant.