1.5: ”A good design system is a set of Legos where you can combine simple things to make more complicated things”

1.5: ”A good design system is a set of Legos where you can combine simple things to make more complicated things”

In this episode, we're dealing with design systems – but from a slightly different angle. Instead of talking about how to set up, develop, and maintain a design system, we discuss it from a consumer's perspective. And by ”consumer” we mean a development team within an organization utilizing and contributing to a design system.

”A lot of people have this gut instinct of 'now I'm just gonna be doing boring stuff because I can't have the wild west of all possible CSS available to me anymore. I think I've done so many bad design decisions in the past that I can see the benefit of not having to customize everything from the beginning," says today's guest senior software developer Kimmo Tukiainen.

In the episode, Kimmo shares his experience working with design systems, style guides, and shared component libraries, and he explains why a utilizing a design system is more beneficial than not.

Tämä jakso on lisätty Podme-palveluun avoimen RSS-syötteen kautta eikä se ole Podmen omaa tuotantoa. Siksi jakso saattaa sisältää mainontaa.

Jaksot(13)

2.1: Getting Steve Faulkner wound up about accessibility

2.1: Getting Steve Faulkner wound up about accessibility

Steve Faulkner is really into accessibility. ”That’s all I’ve been doing for the last 20 years.” Steve has been an accessibility engineer since 2001, first with Vision Australia and currently with The...

15 Loka 20211h

1.11: ”This was supposed to be a summer special”

1.11: ”This was supposed to be a summer special”

Just another summer special, nothing special about that. Except the fact that the summer is already over, one might say. But that's incorrect! In the Northern Hemisphere, the autumnal equinox will occ...

22 Syys 202135min

1.10: ”At the end of the day, they were potatoes”

1.10: ”At the end of the day, they were potatoes”

Have you ever applied to a job as developer and ended up with a bunch of ”code challenges” or ”tasks” to solve on your own and submit? One day, William had a brilliant idea; after participating as co-...

10 Kesä 202129min

1.9: ”The yellow meatball episode”

1.9: ”The yellow meatball episode”

What is the difference between self-organizing teams and self-managing teams? What did Henrik and William learn about the updated Scrum Guide during a recent ”Scrum beer” with Swedish agile experts? A...

27 Touko 202128min

1.8: ”Failing miserably is fine as long as you don't fail the failure”

1.8: ”Failing miserably is fine as long as you don't fail the failure”

Why is it important to embrace and celebrate failure? And why is it important to foster a culture in a workplace where you are allowed to fail? ”Hopefully, your worldview is growing everyday. There's ...

12 Maalis 202135min

1.7: ”Open sourcing your code isn't sharing your profits, it's sharing your risks”

1.7: ”Open sourcing your code isn't sharing your profits, it's sharing your risks”

When Skolplattformen, a digital platform for schools in the Stockholm Region, was launched in 2018, it had already cost a staggering €100 million (roughly $120 million) of tax payers money – and the r...

24 Helmi 202148min

1.6: ”It’s about creating environments for people to meet, communicate, and do things together”

1.6: ”It’s about creating environments for people to meet, communicate, and do things together”

After mentioning the word ”culture” approximately a million times throughout the season, it's finally time to dedicate an entire episode to corporate culture. And since both Henrik and William are som...

28 Tammi 202144min