EvolveDrupal Summit Toronto, 2024
The Pitfalls of building scalable systems.
Not clickbait, I promise. There is a real risk here. Let me explain.
See, knowledge sharing and mentorship are a significant part of who I am as a designer; why I pour my personal time into mentoring designers and creatives all over the world.
Public Speaking, My new passion!
When I get over the crippling nerves and pound back enough coffee to offset the sleep I’ve lost developing the entire talk at short notice, that is.
The ability to share with large groups, while soaking up the power of shared learning is a real high.
Getting back to those Pitfalls we started off with...
The TL;DR is:
Be careful what you prioritize.
As developers we love to play with technology. We build features that make our lives easier.
We build tools that make making more content easier.
However…
If we prioritize our own convenience, We the Developer, become the customer. That means the actual paying customer/player facing experience becomes less of a priority.
A quick glance at the games industry circa 2024-2025 should convince you why this isn’t a trait you want to be known for.
You scoff, probably. You shouldn’t.
I’ve worked on dozens of teams on dozens of projects over my career. I’ve seen this scenario play out over and over, usually with the outcome of completely robbing teams of any real velocity or chance of getting that game out the door, where it can start generating revenue.
Check out the video. Share some thoughts. You know where to find me.
