Alain Schlesser: The Eternal Struggle – Backward Compatibility VS Technical Debt

Continue the discussion

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Published

January 6, 2019

WordPress draws a lot of its success from the fact that it jumps through hoops to maintain backward compatibility. Most WordPress sites can be smoothly updated to the latest version of WordPress Core with the click of a button. However, this compatibility comes at a steep price: through this absolute priority on backward compatibility, the project sets itself up to continuously accumulate technical debt in the process. The effects of this are an increasing effort to maintain the codebase and an increasing difficulty to add new features. Let’s examine how these two factors interrelate and what this means for WordPress’ current state and future evolution.

Presentation Slides »

Rate this:

Event

WordCamp Nijmegen 2018 19

Speakers

Alain Schlesser 15

Tags

Backward Compatibility 1
Technical Debt 1

Language

English 7835

Download
MP4: Low, Med, High
OGG: Low
Subtitles
Subtitle this video →
Producer
%d bloggers like this: