Blog

Introduction In general, design systems is a systematic approach to creating and maintaining consistent user interfaces which coherently communicate the brand values and empower user experience.

Design systems standardise and simplify the process of interface design and development, they bring new approaches and form their own ecosystem. However, there is no solid understanding of the concepts and terms forming the design systems. To solve the term inconsistency and provide structured professional language, this article focuses on the vocabulary used in the design systems domain by observing a range of materials on the topic, from both academic and popular sources.

Company internal communication is a crucial aspect of forming innovation-friendly environment, in which employees can effectively apply their expertise and creativity for achieving business goals. Creative people need “emotional ownership” in the goals and objectives, which becomes even more important speaking about the corporate world where such people are not co-founders but employees. (Sarasvathy, 2008) Establishing right communicational practices very much contributes to developing this kind of ownership and makes innovation possible.

Last year, during my studies of IDBM program at Aalto University, I took a course "Design in Innovation Context" which covered entrepreneurial innovations and behavior. Even out of study context but in everyday life I have always been interested in the answer to the question “What is so special about entrepreneurs that makes them who they are?”. Below, I have tried to summarize the knowledge I got and answer this question.

Interview to Cristiano Rastelli about using BEM in developing frontend.

Two weeks ago, I have started a new project of migrating a large website to React. Although this is not developing from scratch but refactoring, there still was a great chance to reconsider the project file structure in its client part. As a proof-of-concept, I have chosen a pair of components: shopping cart and adding button. This is e-commerce what we are building here :-) My initial goal was to create simple components and demonstrate their reusing as well as introduce Redux as a glue to the components in the data area. As a result, I think I provided a nice and neat structure which helps a developer to understand what serves what. On the other hand, I tried to keep it simple. In the beginning, there is no need in overcomplicated.