Edwin Maldonado talks about some of the ways to support pure content changes from the editorial team so you can handle broadcasts from your editors to multiple devices.
To design a reusable information architecture, you should take in consideration the business, project, and technical constraints in play. Edwin goes through the process of requirements gathering and the information architecture design iterations. To validate our designs we ask the following questions:
Learn by doing and make sure to bring a notebook and a pen; we’ll making diagrams and mockups.
Edwin Maldonado is an independent software architect who enjoys talking about integration, information architectures and the organization structures that builds them.
He has experience working with media companies the fintech industry, where he spent several years working with ACH (Americas) and SEPA (Europe). Besides the daily work, Edwin loves to talk about software architecture, coffee, watch history documentaries, and learn about urban planning.
Comments on this page are now closed.
For exhibition and sponsorship opportunities, email SAconf@oreilly.com
For information on trade opportunities with O'Reilly conferences, email email@example.com
View a complete list of O'Reilly Software Architecture contacts
©2019, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org
Link again as “plain text” it seems the markdown of the comment section ignored the last dash (-) of the URL:
Some of you asked me for the link to the deck I used this morning.
This is the Link to the presentation-
Feel free to contact me in case of questions related to the workshop!