Field notes, primers, and case-tested patterns from Rangle on agentic systems, design systems, frontend, and AI strategy.
Showing 360–371 of 505 posts
Now that Bridge applications are open again, we've gotten a lot of questions about what it's like to be in the program. So this week we sat down with three alumni to chat about their Bridge experience. Who better to speak about what it's really like than the students?
Build Engineering Capability
AngularConnect, Europe's largest Angular conference, took place on November 7 and 8 in London, England. As the premium sponsor, Rangle had the honor of being the keynote presenter during the second day of the conference. Our CTO, Yuri Takhteyev, took the stage to share the thrilling story of how far both Angular, the leading open source JavaScript application framework, and Rangle had come in the past four years.
Angular
At Rangle, we realize that while we try to maintain the team-first approach to quality as defined in the Scrum Guide, there are just some things that our Business Quality Analysts (BQAs) are better at. The role of the BQA on a development team at Rangle is not as a tester as in other organizations, as my colleague Eric has already alluded to in his article BQAs: Why We Combined the Business and Quality Analyst Roles. We help to ensure that the Scrum Team develops cross-functional skills in testing and in story writing; we're essentially Quality Coaches who work to assist our team members to adopt a testing mindset while thinking of quality from the product's inception.
Build Engineering Capability
Whether you're interested in expanding the online presence of your brick and mortar business, or optimizing your digital store, there have never been more exciting times to discuss eCommerce, traditional retail and the technologies that will affect both. Today we will focus on AI (specifically on machine learning) and how the stores of the very near future will require you and your team to leverage it.
Modernize Your Stack
Rangle has acquired key insights doing Agile software development projects for a diverse group of clients. In this article, we take a look at when testing ought to happen, which parts of it are actually worth doing, and how to tell.
As we've discussed in previous articles, the role of the QA has transformed over the years. Affected by a shift towards Continuous Delivery, technological advances (such as A.I. and machine learning) and changing expectations from clients and their own teams alike, the role of QAs of today isn't what it used to be a few years ago. Naturally, the skills that will be required of them in the future will also evolve.
Our recent whitepaper Advanced Agile: Five Ways to Accelerate Delivery, Improve Flexibility, and Reduce Waste (Available through our Contact Us form) summarizes five of the key insights Rangle has acquired doing Agile software development projects for a diverse group of clients.
Align Product Strategy
Our recent whitepaper
Build Engineering Capability
Quality assurance has a bad reputation. Despite being a vital part of the development process, some argue that if developers were writing good code in the first place, then QAs wouldn't be necessary. Yet constant testing is vital to ensure things work as they're supposed to.
Build Engineering Capability
Components can be tested with snapshot testing. Tools like Jest (often combined with Enzyme) that offer this functionality take a 'snapshot' of what your component renders--everything from divs, attributes, classNames, props, and state--and saves it to a file, kind of like this:
Frontend Development
With support from Alex Karasyov. Although Agile development is common practice within many of the world's leading tech companies, many aspects of the process are still misunderstood, misused, or all alone ignored. Agile software development refers to a set of best practices, methodologies and team values that allow organizations to quickly adapt to changing customer needs and respond to competitors, all while solidifying team morale.
Align Product Strategy
In Creating Forms with Redux Part I, we hooked up our forms to Redux, learned about the reduxForm HOC and Field component, styled our forms, and made a custom input component. In this section, we continue creating reusable components for the most common form widgets, learn how to do field-level validation, and dive a bit deeper into the built-in action creators and selectors to help us create a more dynamic form.
Frontend Development