In my daily work, I plan. I ponder. I test. I end up with code so clean you could eat off of it. Then Advent of Code comes along and suddenly I'm writing the Madison Square Garden Men's Room of PHP. But it worked.
| Website | https://gros.co |
Ed Grosvenor
- 70 Followers
- 211 Following
- 224 Posts
American PHP developer living in Basel, Switzerland
@cam I made the same mistake everyone else did at first. A humbling experience.
Chris HartjesMy last day working for my current client is tomorrow. I am looking for #php consulting / contracting work starting in January. Need the community’s most shouty person about testing your code and getting biz value delivered faster? Hit me up and let’s talk.
Ben RamseyToday, I was cut in layoffs. I’m so gutted because I loved this company, & my team was the best; I’ll miss my team most.
Now, as I look ahead, I’m searching for a staff/principal role where I can help other developers level-up through mentoring, tooling/infra, architecture, & improving DX. I’d love to work with a company contributing to open source & even to the #PHP programming language itself.
Update (27 Feb 2024): Thanks, everyone! I’ve accepted an offer. Please see update in thread below.
I usually work with 90s metal piping through my headphones, but my wife has this "no Pantera in front of the baby" rule so when he joins me in the office it's soft classical music. I notice two things about my work output with this background. First, I'm slower. Second, my comments and commit messages are more polite.
@bobmagicii Part of me wonders whether it would be easier just to fork the package and give it some love. It's infrequently maintained because it just works, but it's old. If the maintainer likes the paint job, great. If not, it wouldn't be hard to just maintain my own fork because it almost never needs updates these days.
@bobmagicii Yes, that seems to be what it's trying to do.
@bobmagicii It seems like the right solution would be to just store the values of the properties as json and then new up the class when I need it back and hydrate it. But there are no convenience methods (toArray, etc) to make that easy.
@bobmagicii maybe. But the warning seems to be talking about numeric properties that don’t exist on the class at all. Might be a side effect of serializing and unserializing. So I’d be adding properties that don’t exist for no really good reason. I’m wondering if I can get a better result using the symfomy serializer and taking a bit more control over what the stored object looks like.
Let's say, for fun, I have good reasons to serialize an object. When I then have good reasons to unserialize that object, I'm getting dynamic property deprecation warnings. Is this just the way of the world now or is there something I'm missing? I don't "own" the class, so I can't easily mark dynamic properties as allowed before serializing (and I'm not even sure that would work).