This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
He is the author of numerous technical books and videos from O’Reilly, including several books on Microservices, the Software Architecture Fundamentals video series, Enterprise Messaging video series, Java Message Service, 2nd Edition, and a contributing author to 97 Things Every Software Architect Should Know.
We expect to welcome 300 software architects, who are passionate about useful, well designed, maintainable and scalable software. There will be technical talks by leading software architects from USA, UK & Spain , panel discussions and debates! George Fairbanks.
Robust and scalable software is in the center of every discussion and talk, which makes it a perfect place for people who fight for quality in the software development world. In addition to technical talks and hands-on workshops, it will be fun! Neal Ford is Director, Software Architect, and Meme Wrangler at ThoughtWorks.
But as time passes, not upgrading to the latest version may result in technical debt. It’s a systematic process of gathering a list of functional, technical, and system requirements from different stakeholders like users, vendors, IT staff, and customers. For example, let’s say your application uses React 15. The rest?—?the
But as time passes, not upgrading to the latest version may result in technical debt. It’s a systematic process of gathering a list of functional, technical, and system requirements from different stakeholders like users, vendors, IT staff, and customers. For example, let’s say your application uses React 15.
But as time passes, not upgrading to the latest version may result in technical debt. It’s a systematic process of gathering a list of functional, technical, and system requirements from different stakeholders like users, vendors, IT staff, and customers. For example, let’s say your application uses React 15.
This was a pretty technical talk. Artem Rudoi ( @rudoj_artem ) – Scalable UI. Donny Wals ( @DonnyWals ) – A Practical Approach to Adopting TDD In the Workplace. Fernando told us about the importance of constantly analyzing our code to create better strategies for the next refactor of our classes. lesarew.
We organize all of the trending information in your field so you don't have to. Join 49,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content