From Monolith to Microservices in 5 Minutes a microservice architectural style is an approach to developing a single app

This, more than anything, I feel is the true root of the prevalence and unique intensity of imposter syndrome among designers — the relentless fear that despite our best efforts to seek adequate knowledge and guidance, we still aren’t fully prepared to do justice to the work we’re hired to do even when we actually are. This fear gets internalized in so many other destructive ways that go far beyond just second-guessing ourselves doing the work. Ways like — we don’t always speak up for the integrity of outcomes when we need to. We don’t feel empowered to call out unethical practices. Or we feel lowkey apologetic about demanding that clients and employers stick to the terms of our service. It’s a dark cloud that hangs over many of us that we adapt to instead of eradicating. Instead of confronting its causes, we collectively ascribe it to human nature — just a thing we have to make peace with. And to a certain extent, that is true — imposter syndrome definitely is a normal part of life. Still, we can mitigate the crippling degree that we experience as designers by being honest with ourselves about the overarching contributing factors, facing them head-on, and then forcing ourselves to radically rebuild how we work and teach.,Right about now, you may be asking, “Why would you dare kick the hornet’s nest that is the community of Design, Lisa? Why would you risk the inevitable onslaught of ‘reply-guy’ comments or attempts to discredit your statements?” The answer is that I’ve talked to too many of my peers who recognize that something is wrong and want to help but don’t know where to start. And I’ve heard from more than enough young designers who are genuinely lost and blaming themselves for it that I can’t just watch it continue any longer. They deserve better from those of us who have been doing this work for decades and have been actively forging the path for those who follow.,I’ve criticized Apple plenty of times for its fixation on keeping options limited, and I don’t think it’s a bad thing that the company is introducing a smaller phone. Kids and other people with small hands, casual users, or people who use their phones in active contexts — I imagine a restaurant manager, for example, navigating a busy environment with a small iPhone tucked into their pants pocket — will clearly benefit from the smaller device. But anyone who does a lot of work and reading on their phone may as well give in to what their brain really wants (or needs) and stick with a bigger phone. If you really want a cute little tether that will let you further disconnect while making you look Luddite-cool, might I suggest a Baby Phone instead?,How people engage with technology has evolved significantly over the last decade. Our methods for designing products for that technology have not kept up. We tweak methods we’ve never held accountable for efficacy and then debate the merits of those “improvements”. But at what point do we say, “The outcomes produced by X method don’t warrant the effort we put into it, so maybe it shouldn’t be our go-to anymore.”,Are you good? Great. Let’s proceed to dive into my “top of mind” areas that are most obviously not working in our wacky world of digital design. This is an attempt to raise issues, not cover them in any exhaustive way. That will require a lot more discussion, research, and time from all of us collectively. There are also some critical topics that I intentionally left out that I intend to cover in the future. Feel free to bring up your own topics in the comments, but trust me, this is a long enough rant as it is.,A Fibonacci sequence is a series of numbers that every number is the sum of the two numbers before it. The first two numbers, X₀ and X₁, are special. They are 0 and 1 respectively. Since X₂, the patter is as above-mentioned, it is the sum of X₀ and X₁, so X₂=1. Then, X₃ is X₁ X₂ =2, X₄ is X₂ X₃=3, X₅ is X₃ X₄ = 5, and so on.,Layers in Software Architecture that Every Sofware Architect should Know “All architectures have the same objective - the separation of concerns. They all achieve it by dividing the software…danielrusnok.medium.com,The design industry is a living paradox. By many measures, it is smugly self-satisfied and self-absorbed while simultaneously being full of some of the most talented and generous people you’ll ever meet. But self-awareness is not our strong suit. We ascribe our inability to get equal consideration in workplaces to external factors. We act as though we come to businesses all buttoned-up with strategically chosen professional methods and standardized workflows. And we all know that’s a lie. Name any other profession that could continually get away with the incredible inconsistencies in quality that we collectively generate. Now I know every industry has a bit of messiness when you look under the hood, but we’re designers. We’re uniquely positioned to create a better way. We have the ability to solve this. It’s not enough to just go on Facebook or Twitter and rant about what’s not working. We have to come to an industry-wide understanding of why these issues exist and commit to doing something about them.,With this portentous beginning to many a well-intentioned post, you can almost be certain that what follows will be some distillation of painfully direct life advice intended to remind people of what’s important. Consider this article a really extended version of that, directed primarily at digital designers in senior and leadership roles as they are our industry’s best chance to right the ship. In order to bring you to the forward-thinking, uplifting bit, I’m going to have to first unsettle you with some difficult truths.,For the last few years of my career, I’ve felt the weighty realization that the design industry’s accepted and most practiced ways of creating digital products are more deeply flawed than I ever imagined and much more than most will admit — as is the way we educate aspiring designers. This has been nagging at me to such an extent that I realized I could not stay complacently on the sidelines watching it happen any longer. If you follow me on Twitter, then you know I haven’t exactly been silent on this topic, but up until now, I haven’t really pushed for action, and that platform doesn’t really lend itself to fully expressing ideas. This then is my attempt to get a lot of my thoughts out in one place to hopefully catalyze new discussions. And I know many of you share these feelings even if you don’t dare talk about them.,So in that spirit, I’m letting loose a rant I’ve been sitting on for a long time about what I see as some of the most major roadblocks to good practice in design and then touch on some suggestions that I hope will spark productive dialogues.,I’ve criticized Apple plenty of times for its fixation on keeping options limited, and I don’t think it’s a bad thing that the company is introducing a smaller phone. Kids and other people with small hands, casual users, or people who use their phones in active contexts — I imagine a restaurant manager, for example, navigating a busy environment with a small iPhone tucked into their pants pocket — will clearly benefit from the smaller device. But anyone who does a lot of work and reading on their phone may as well give in to what their brain really wants (or needs) and stick with a bigger phone. If you really want a cute little tether that will let you further disconnect while making you look Luddite-cool, might I suggest a Baby Phone instead?,Layers in Software Architecture that Every Sofware Architect should Know “All architectures have the same objective - the separation of concerns. They all achieve it by dividing the software…danielrusnok.medium.com,“Leave safety behind. Put your body on the line. Stand before the people you fear and speak your mind — even if your voice shakes. When you least expect it, someone may actually listen to what you have to say. Well-aimed slingshots can topple giants. And do your homework.”,We have to call these issues out by name and own them. Our social media feeds are full of astute observations of the problems, but where is the next level of conversation? When do we finally get to the part where we tackle solutions?