Debugging

I believe there are 3 things you need to know to interact with any system optimally: How it was intended to work. How people think it works. How it actually works. Knowing how the system was intended to work can help in finding the optimal way to interact with it. If you work with a system with the designer’s intentions in mind, you can take a path that is compatible with their future plans, and even their oversights.

I wrote a new blog post that outlines a number of techniques for decompiling and debugging AEM source code. You can [find it on my company’s engineering blog]https://web.archive.org/web/20230609044544/https://engineering.icf.com/decompiling-and-debugging-aem/)! Update 2025-04-08: It looks like the old ICF Engineering blog finally fell off the face of the internet. I’ve linked to the web archive version for now. I may repost the content here at some point in the future. I also noticed at least one website that has wholesale stolen the content word for word with no attribution, which is super frustrating.