Lightning Talks: Ad Tech History, Software Architecture, PHP Dependency Management, and Auction Mechanics
A recent internal tech meetup brought together practitioners from across the AdTech and software development space for a series of lightning talks and longer presentations. The agenda covered ground from the origins of online advertising all the way through to auction theory — a broad but cohesive mix that reflects how multidisciplinary AdTech engineering tends to be in practice.
Ad Tech History in 15 Minutes
The first online ad was a banner ad from AT&T, displayed on hotwired.com — the web presence of Wired Magazine — in 1993. At the time, buying and selling ad inventory was a straightforward direct deal between an advertiser and a publisher. No intermediaries, no auction layers, no demand-side platforms.
Fast forward just 12 years and that simple arrangement had evolved into a multi-billion dollar industry populated by complex technology platforms, specialized intermediaries, and major players including Facebook, Google, and Yahoo. The pace of that transformation is worth pausing on: what began as a single banner unit on a single website became one of the most technically sophisticated commercial ecosystems ever built, in roughly a decade.
The talk covering this arc walked through the progression in detail — how the pipes got built, who built them, and what the industry looks like as a result.
4+1 Architecture Perspectives
When building software, teams frequently adopt a view model framework to keep different stakeholders aligned. A view model defines a set of structured perspectives, each aimed at a different audience — end users, developers, project managers, product owners — so that documentation actually speaks to the people who need it.
One talk examined the 4+1 architecture view model as a practical example of this approach.
The four core views in the model are:
- Logical View: Concerned with the end user. Focuses on the functionality the system provides them.
- Development View: Paints the system from a programmer's perspective. Addresses software components such as repositories and packages.
- Process View: Aimed at system designers. Covers dynamic system behaviour, inter-process communication, and performance and scalability considerations.
- Physical View: Also called the deployment view. Addresses the topology of software components on the physical layer and the connections between them — essentially what's running where and how it's wired together.
The +1 in the model refers to Scenarios (Use Case View). Scenarios help stakeholders understand how the system is intended to be used. They're typically the starting point for architecture prototype testing and are gathered through requirements analysis.
Beyond the model itself, the talk addressed the practical side of documentation — what good practice looks like versus common pitfalls — which is often more useful than any formal framework on its own.
Composer — Not Just a Vendor Manager
Composer is a dependency management tool for PHP projects. It allows development teams to define, install, and maintain all project dependencies in a consistent and reproducible way — a task that sounds mundane until it isn't.
A presentation from a software manager with experience at an analytics platform dug into the advanced usage patterns that often go unexplored. Most PHP developers know Composer as the thing that runs composer install. The talk went further: showing practical examples of advanced configurations, laying out the benefits of treating Composer as a first-class tool rather than a formality, and walking through concrete use cases where smarter Composer usage pays off.
Auction Mechanisms Primer
Auctions govern far more than art and real estate. They're central to how online advertising inventory is bought and sold through real-time bidding (RTB), and they underpin consumer platforms like eBay as well.
A project manager with a background in auction theory presented an overview of the different mechanisms in use — the mechanics behind each, the strategies available to bidders and sellers, and how the goals of each party shape the design of the auction itself.
The session focused particularly on the second-price auction model, which is the dominant format in RTB and widely used on online marketplace platforms. To make the mechanics tangible, the presenter ran a live social experiment with attendees — always a reliable way to demonstrate why rational bidding strategy isn't as intuitive as it first appears.