Andrew Cassell


Talks (By Name)

Date Presented | Last Commented | By Comment | By Name

Domain-Driven Design in PHP

Domain-Driven Design in PHP Workshop

Domain-driven Design Deconstructed

Domain-driven Design in PHP

Immutability to Save an Ever-Changing World

Immutability to save an ever-changing world

Introduction to domain-driven design in PHP

Manage Private Internal Dependencies With Composer and Satis

No Modes - The Future of All Web Applications

No Modes – The Future of all Web Applications

Obtaining Closure with Anonymous Functions

Responsive Web Design for Non-Designers

Virtual Reality and Augmented Reality Web Apps


(Show Details)
(Hide Details)
Rating: 0 of 5 
Obtaining Closure with Anonymous Functions
Slides have been posted.
Rating: 5 of 5 
Containerizing PHP Applications
Great overview of getting Docker setup for a dev environment.
Rating: 4 of 5 
All the Laravel Things - Up & Running to Making $$
Presentation was a great overview of how to get into the Laravel ecosystem. Presentation quality and performance was excellent and I would give a 5/5 for that. Great job Joe!
Rating: 5 of 5 
Symfony vs. Silex, Micro vs. Full Stack
I use both Symfony and Silex. This was an excellent presentation comparing and contrasting the difference. I learned a few things I didn't know about the performance considerations. My only feedback would be that I would have liked to hear more about your suggestions of which one to use depending on the type of project. Great presentation!
Rating: 3 of 5 
Using a Monolithic Repository Strategy
The presentation explained things very well, but I think the applications are limited to people with large codebases and/or large infrastructures. I still enjoyed it.
Rating: 4 of 5 
Cruft to Class: NPR's 15-year Journey with PHP
Great presentation. I thought the history part of the presentation was a little bit dry. However, I really liked the 7 strategies portion of the talk a lot more. I would have liked to learn more about the challenges of implementing those 7 strategies in a larger organization like NPR. Great Job!
Rating: 4 of 5 
Up to My Eyeballs in Technical Debt!
This presentation was both excellent and confusing at times. For example, I was a little confused by some of the examples such as what he referred to as a dependency and recipe-cpt.php, but maybe those make more sense to a Wordpress developer. However, I thought Steve did a nice job of explaining that technical debt is, when it is bad, and when it is good. I thought the idea of making documentation review a part of the code review process was a superb idea.
Rating: 5 of 5 
DC PHP User Group Meeting
This presentation was excellent. The overview of Blackfire was nice, but the explanation of profiling in PHP and how to make things go faster made it worth attending. Thank you!
Rating: 4 of 5 
Shipped is Better than Perfect
I really enjoyed this presentation. Fad based development can really be a problem (Command Bus example was great) and new developers think they need something complicated to be "professional". The presentation used a side project but I felt like the rules & needs when implementing a side project might be a little different than implementing an application a business is going to rely on. On the positive side, I don't necessarily apply YAGNI to code and infrastructure as I do features, but Graham made a great case for keeping it simple. I don't think I've ever had the problem of being a perfectionist otherwise I probably would have rated this talk a 5/5. Thank you & great job!
Rating: 5 of 5 
Building APIs with Slim Framework
Excellent. Described everything in a thoughtful and well developed manner. I may even learned something :). Great job.
Rating: 5 of 5 
Excellent. Obviously there was a bit of confusion on the timing, but the question & answer period was good.
Rating: 4 of 5 
Solving Cross-Cutting Concerns in PHP
Well presented. I thought the explanation of using AOP for logging and caching was great. I don't think a lot of PHP programmers know about AOP. I disagreed with the use of AOP for security when it appeared that the code was expected to be used inside of a framework any, or should have been stressed that if the developer is using Laravel or Symfony to just let the framework handle it. Also, I felt like the suggestion that using AOP instead of a mediator would be simpler to be not accurate, as there is quite a bit of spooky action at a distance that can cause unintended problems and makes the code harder to follow and requires integration testing instead of unit testing to verify. I thought the negatives of using the AOP framework could have been better described with examples of exception stack traces or debugging while using the framework.
Rating: 5 of 5 
Year with event sourcing and CQRS
This was a great story. I really enjoyed the humor and storytelling style. I really agreed with Miro that stressing a firm understanding of testing was going to be required before going down the path. Only (minor) improvements I can think of were: It was slightly confusing switching back and forth between the TicketSwap and personal projects; The value object explanation could be improved, left out, or use some slides; Explaining the difference between an event listeners and process/saga. Great job!
Rating: 5 of 5 
Time is an illusion (lunchtime doubly so)
Very well presented. Having wrestled with timezones in the past I enjoyed every minute of it. My only suggestion would be to clarify never to use the timezone abbreviation other than showing it in an app where you know your users aren't going to be confused by it (also never store it).

Events They'll Be At

No events so far

Events They Were At

True North PHP 2016 Nov 03, 2016
php[cruise] Jul 16, 2016
php[tek] 2015 May 18, 2015
php[tek] 2014 May 19, 2014
php[tek] 2016 May 25, 2016
© 2019