![architectural details made from taskboard architectural details made from taskboard](https://static.wixstatic.com/media/00f75a_29f15b9b9a324a22b5427af4d59ef9f9~mv2.jpg)
- #Architectural details made from taskboard how to
- #Architectural details made from taskboard full
- #Architectural details made from taskboard software
- #Architectural details made from taskboard code
#Architectural details made from taskboard software
“If you ask a software engineer if they’ve ever been part of a brainstorm, 99 percent will likely say yes,” Pato says. “Not to mention that MURAL, as a tool, is extremely aligned with facilitating the process, too.” One of the first steps of design thinking is ideation, or what we often call brainstorming. “I love the concept of design thinking and that I get to apply it to my day to day,” he explains. The role of design thinking: What is a brainstorm?įinding and implementing solutions starts with ideas, so it’s no surprise that Pato thinks about the ideation process a lot. “It’s a virtuous cycle, if you will,” he explains. “MURAL, the tool, helps us gather those ideas, collaborate, and accommodate all kinds of perspectives.” So when he uses MURAL in his day-to-day, Pato can’t help but appreciate the fact that the tool he’s helping to build is not just serving our customers, but it’s helping him and his team find better solutions, too. “Diversity of thought helps us see the range of possibilities and truly choose the best way forward,” he says. He not only believes that when people work together they can find the best solution to a problem, but also that the more diverse perspectives involved, the better. The idea of working together is something that Pato values and consciously strives to incorporate into his environment. “Software development, as a craft, is all about finding solutions together - MURAL helps me and my team do that and empowers other teams to find better solutions together too,” he adds. “The fact that the product I’m helping to build helps engineers be better at their daily work is incredibly motivating to me,” he says. Pato loves that MURAL helps people solve problems, because it helps him become a better problem solver, too. Getting meta: Using MURAL to build MURAL But what intrigued him more was the ability to build tools that other developers across the globe would use.
![architectural details made from taskboard architectural details made from taskboard](https://static.wixstatic.com/media/00f75a_9b0dd14d8f784ed8804c9d5881ffd628~mv2_d_2448_3264_s_4_2.jpg)
“I’d used MURAL before and shared an office with the team, so it felt like a natural place to transition,” Pato says. And that’s where he got hooked on building tools that other developers use - ultimately, this is what led him to MURAL.
#Architectural details made from taskboard code
When he ventured from a large corporation to his first startup, he joined a company that was building a code reviewing platform.
#Architectural details made from taskboard full
A few years into his career working as a full time software engineer, Pato noticed the pain he and his team felt when it came to code reviews. At 17, he got his first job as a programmer: “I couldn’t believe I was getting paid to code,” he says. His parents then bought him and his brother two network computers, on which they’d play games and write modifications, inviting their friends over to test out their programs.
![architectural details made from taskboard architectural details made from taskboard](https://www.epiloglaser.ca/assets/img/how-works/photos/ppr-puzzle-lights.jpg)
![architectural details made from taskboard architectural details made from taskboard](https://i.pinimg.com/originals/12/bb/d4/12bbd419eab614c47412661a174e84ad.jpg)
“It was empowering to solve problems using code,” he remembers. He quickly signed up for a basic programming course and discovered the rush he felt when he was able to build a solution. Pato’s journey to being a software engineer started when he was 13 and got his first computer. “I work to find a set of possible approaches and then, as a team, we reach a consensus - there’s never an imposition of an outcome, we always work together.” The process Pato is a part of is core to MURAL’s DNA, in fact: we never want to dictate what our teams do, but instead, collaborate to find the best route forward for everyone - both in their careers or in our product roadmaps and solutions. “My role is to be part of the negotiation and collaboration process to find the best solution,” he explains.
#Architectural details made from taskboard how to
Then Pato steps in to figure out how to actually solve the problem they’ve identified. The process starts with our Product Engineering team looking at data and user research, coming up with a problem statement, exploring the issue at hand, and establishing the scope. “I need to be solving problems during the day.” Which leads us to today: Pato is an Architecture Lead on our Product Engineering team, where he helps come up with solutions to our technical problems. “I wake up with code in my fingertips,” says Pato Zavolinsky. It didn’t take long for Pato to discover that his passion in engineering was on the technical side.