Blog

As a Quality professional, it is a daunting task to keep up with the changes in technology. The need to know new programming languages, be aware of the latest-and-greatest testing tools, and know how to deliver applications faster in our daily practice are just some of the challenges we face. In addition, many organizations are focusing on AI and Machine Learning as a way to modernize their business.

We all like to believe that there’s someone else in the room who has a grasp on what’s going on when we’re feeling in over our head. Play it cool man. Pretend like you’ve done this 1000 times before. I totally got this, and if I don’t, someone else does and will tell me what to do. Until it's time to produce something, and you realize everyone around you is in the same boat, and it's called the "SS Please Send Halp."🤦♀️ (Who names their boat like that?!)

Rangle and InVision are proud to announce a strategic partnership, enabling Rangle to advise InVision’s clients on successful approaches to Design Systems and Design Operations. This new offering will cover a wide range of topics, including building and maintaining a design system using InVision Design System Manager, ensuring wide adoption, and methods to improve collaboration between designers and developers.

CSS is often belittled because it’s naturally global—which programmers wish to avoid—but doing so betrays a lack of understanding of CSS’ foundational premise and greatest strength.

Diversity is a fact, while inclusion is a human act. At Rangle, this is our mindset as we continue to enable and promote D&I (diversity and inclusion) at our office in Toronto and now in Tokyo, Atlanta, and Amsterdam too.

So you’ve been assigned to a team that you’ve never worked with before. You’re excited and nervous all at the same time because you don’t know how you’ll fit. What do you do?

Machine learning and artificial intelligence (AI) can be daunting subjects. You might've heard about neural networks, generative adversarial networks (GANs), and recurrent neural networks (RNNs) but have no clue what people are talking about.

A design system is an amorphous thing. One definition I like, and there are several, is that it's an ecosystem of tools, guidelines, and shared values and principles that helps teams more efficiently ship consistent design. Similar to how different ecosystems emerge from the interactions of its communities, a design system varies from one business to the next, according to the needs and interactions of its teams. With that in mind, it's just not possible to define a specific set of artifacts that should make up every design system, nor should we try to.