Life at Windmill • Windmill

In this installment of our series, we’re excited to introduce Ivan Myronov, the Principal Technologist at 1PLTFRM and leader of the React team at Windmill. Join us as Ivan explores the many facets of React and shares how his team’s approach sets Windmill apart from the competition.

What Exactly is React?

Ivan Myronov Explains:

  • React in a Nutshell: React is a JavaScript library, not a framework, which means it’s more flexible and focused. It helps developers build user interfaces by managing the view layer for web and mobile apps.
  • Common Misconceptions: It’s often mistaken for a framework because it’s so comprehensive, but React is all about giving developers the freedom to structure their projects their way.

Unique Features of Windmill’s React Team

Ivan’s Insights:

  • Dedicated Practice: Our team dedicates countless hours to mastering React, emphasizing clean code and frequent refactoring to enhance project quality.
  • Collaborative Learning: We hold bi-weekly meetings to discuss our technical debt and prioritize our tasks, ensuring we’re always at the forefront of industry standards.

React vs. Angular: Choosing the Right Tool

Technical Comparison by Ivan:

  • Coding Style: React uses a declarative programming style that reduces boilerplate code and simplifies debugging.
  • Data Binding: Unlike Angular’s two-way binding, React employs a one-way data flow that makes it easier to track changes and debug applications.
  • Learning Curve: React’s fewer abstractions make it more approachable for beginners compared to Angular.

Advantages and Considerations of Using React

Why React?

  • Developer Efficiency: React allows for building applications using reusable components that are easy to maintain.
  • Community Support: With backing from Facebook and a vibrant community, React offers extensive resources for learning and troubleshooting.

Things to Consider:

  • Application Size: React apps can be larger in size, which might affect performance especially on mobile devices.
  • Virtual DOM Overheads: Managing virtual DOMs can add complexity and require optimization to ensure performance, particularly with larger applications.

The Virtual DOM Explained

How React Uses the Virtual DOM:

  • Efficiency in Updates: React creates a virtual copy of the UI in memory, which it updates based on changes in the data model before rendering those changes in the browser efficiently.
  • Myth Busting: It’s a common myth that the virtual DOM provides unmatched speed. However, React’s real benefit is in making the development process faster and less error-prone.

Entering the Field: Advice for Graduates

Ivan’s Advice:

  • Stay Curious: React is a gateway to modern web development with a robust community and a plethora of learning resources.
  • Master the Basics: Solid knowledge of JavaScript, HTML, and CSS is crucial before diving into React to fully leverage its capabilities.

React’s Role at Windmill

Problem Solving with React:

  • Enterprise Applications: React’s modular nature makes it ideal for rapidly developing enterprise-level applications and expanding existing applications.
  • Legacy Projects: It’s excellent for incremental upgrades, allowing teams to refactor and improve legacy systems gradually.

Windmill Digital offers a variety of digital product design and digital product strategy services that will help you stand out against your competitors. For more information, contact us here.  

What does DevOps mean to you?

The DevOps model is defined as practices and tools that improve the ability of any organization to deliver applications and services at a faster rate than the traditional software development models and management processes. For me, all these DevOps principles and practices are adopted through the evolution of process and tools and culture as an organization matures. The key focus should be on the culture change and the key points of the DevOps culture are effective collaboration, constant learning and experimentation leading to improvements and fast feedback.

What are your main responsibilities as a DevOps Engineer?

The DevOps engineer at Windmill collaborates with multiple stakeholders, including the client, to understand project requirements and KPIs during the end-to-end software development lifecycle. We ensure that security and compliance are not compromised in a bid to release products at an accelerated timeline. After planning the blueprint of the development and delivery process, we implement the infrastructure and the development and automation tools. This is accompanied by defining the right build, test, release, and update cycle for DevOps operations. We ensure that the code and infrastructure is properly verified and validated, and that the proper monitoring is present to help us troubleshoot and fix any bugs.
For me, my most important responsibility is to make sure to identify and deploy cybersecurity measures by continuously performing vulnerability assessments and risk management.

How has your approach to DevOps evolved during your time at Windmill? How has technology changed?

The first thing that comes to mind is tools and technology obviously, but it was also accompanied by the change in mindset and the strengthening DevOps culture.
DevOps was originally a simplistic idea, which revolved around making developers and IT engineers talk more effectively with each other. It was only over time that specific types of tools–like containers and their orchestration–were associated with DevOps. And it took longer for the DevOps concept to be extended to all parts of the organization, rather than just development and IT. Throughout my experience in DevOps, there was initially more focus towards on-premise infrastructures with various vendors offering only certain type of services catering towards specific functionality of DevOps. Then there was a shift towards using mostly cloud-native managed services for all the practices of DevOps. Docker and Kubernetes provided an application deployment format that could be used in both development and production environments seamlessly, which facilitated one of the core goals of DevOps.
Every process associated with DevOps today is always supposed to be “continuous”, referring to the idea that processes should occur at all stages of the pipeline. When I joined Windmill, I learned how to make this focus on “continuous” into “comprehensible” and “predictable”, if not literally continuous, which gives better results. Also, there are so many cloud-agnostic tools now which have helped make DevOps processes much faster with faster feedback.

What are some DevOps best practices that are important to the Windmill team ?
  • Infrastructure as Code (IAC): This is where we use scripts to deploy the infra for housing the application. It helps us test the infra in the same way we would source code, and we use virtual machines which behave like production environments early on. This makes it easier to scale and create multiple environments in days rather than months.
  • Cloud Infrastructure: We have used cloud infra as a hybrid of on-prem and cloud or within public clouds for all their managed services. But with the recent shift towards serverless architectures on cloud, we have been able to eliminate or minimize the server management operations.
  • Micro-services: This is the standard in Windmill, whereby customer apps are built as a set of independently-configured services which communicate with each other. This loose coupling helps in isolating issues, and ensuring failures in one service do not break the functionality in others. So the entire system stays stable while we can fix problems in isolation.
  • Containerization and Orchestration: Containers, more lightweight and packaged with all runtime components without the whole OS systems unlike the virtual machines, are used to instantly deploy applications across various environments and this is well combined with the IAC approach. For orchestrating these containers, Kubernetes and other cloud-native Kubernetes tools like AKS and EKS are increasingly advanced.
  • Configuration Management: This means to use code to automate servers, host configurations, operations, tasks and more. We focus on this so that changes in configurations are much more standardized, thereby saving the effort of manually configuring applications, servers, OS, software, etc.
  • Continuous Integration (CI): Our developers frequently merge their codes into the source code management repository, leading to automated builds and tests.
  • Continuous Delivery: This practice extends CI where all the successfully tested builds are later deployed to the testing and/or production environment.
  • Continuous Monitoring and Logging: The goal of this practice is to detect the problematic areas and analyzing feedback from the team and users to improve the product’s features and functionality.
What is the career path or paths of a DevOps engineer?

DevOps Engineer is a very versatile, multi-faceted role as it keeps evolving as increasingly many organizations rely on streamlining operations and the development process, along with constantly evolving the tools used for DevOps, which often means more exciting learning opportunities. DevOps Engineers typically have a background in Software/IT. Most of the times, they landed their role after spending time developing software as well as managing operations, since DevOps bridges the gap between the two. Some important skills of DevOps engineers include:

  • demonstrate that you can work as an individual contributor as well as a collaborator
  • firm understanding of using technologies for automation tools and procedures, CICD, cloud technology, source code management as well as project management
  • ability to close the gap in current technological infrastructure and come up with the right solutions

With that being said, some of the DevOps career roles are: Release Manager, Software Developer, Security Engineer, Operations Engineer, Systems Administrators, highly Technical Support Engineers with L4-L5 Support experience, and more.

What are some key resources you rely on or books from which you have learnt?

I have mostly learned everything from inexpensive Udemy courses offered by certified Cloud Professionals like Stephane Maarek (AWS), Colt Steele (Coding Bootcamps), Zeal Vora (AWS and IAC- Terraform), Mumshad Mannambeth and Edward Viaene (Kubernetes). Apart from this there is always opensource documentation available for all the cloud services. For coding my favorite book series is the Headfirst series for popular languages like Java and Python. Currently I am reading the book ‘The Pragmatic Programmer’ by Andrew Hunt, David Thomas, which offers an insight into the journey of a programmer from increasing specialization to study the core processes of the software lifecycle. It is a great book, covering lots of topics ranging from career development to architecture techniques to managing the flexibility, adaptability, and reusability of software code.

In this edition of Windmill Experts, we spoke with the head of Windmill’s CMS development department, Viacheslav Oblan. We discussed the factors that make Windmill-built websites functional as well as looking great; and what keeps the CMS department a well-oiled machine, among other things.

What kind of projects do you usually work on?

Viacheslav Oblan: We build great websites. When Windmill builds a web app or mobile app, it usually needs a business website to be presented for potential clients, so we do that. We usually work with CMS WordPress but have experience with other CMS platforms. Also, we work on projects for the e-commerce sector.

What role does the CMS department play in enhancing the Windmill website?

VO: Actually, we built it and we continue to support the website. We develop new features, update existing features, make improvements, and fully support the website. We also work closely with the marketing team to achieve marketing goals.

What are some key technologies used by the CMS department?

VO: We usually work with HTML, CSS, SASS, JavaScript, PHP, and different CMS platforms, and we are familiar with web animation (we use Greensock.js, Three.js). We usually use Github actions or Bitbucket pipelines for code deployment from a git repository; it is flexible and lets us automate many things. For accurate QA results, we use not only real devices but also Browserstack, which helps us check our implemented features on all possible devices, OS, and platforms, even if we don’t have a specific device physically.

What is the best way to build great websites?

VO: In my opinion, the key point is striving for perfect quality. We use modern approaches and technologies in web development but the details and responsibility of each team member to what he or she does are very important. On the development step, we think about how the site will be used in business, creating correct architecture so it is easy to use and easy to support. Of course, we should aim to create perfect code and pay close attention to quality assurance.

What do fresh graduates need to be aware of when pursuing a career in your field?

VO: I really appreciate people’s expertise. Everyone working in CMS development should strive to become an expert in a specific area. A person can then increase their areas of expertise and gain additional skills, but the key point is to start with a deep understanding of something. Don’t try to be everywhere and know everything from the start. So, my advice is to try to focus on something that you love and become an expert in this area.

How do you see the future of CMS development? Will the rise of mobile-first browsing or other technological advancements impact your work? 

VO: A “mobile first” approach is not something new for us in building responsive layouts. High performance and quick server responses are needed to ensure phone users will not wait long when the website is loaded. These standards are constantly increasing. I think CMS platforms will live and grow, transforming into different solutions. For example, it was popular recently to use SAAS products, e.g., Shopify. The main goal of a CMS is to make an admin’s life easier and let them work with the website without any specific knowledge in programming, so everyone needs one.

Have you observed any trends in terms of what clients are demanding of late? 

VO: Previously, we have done many things with the “scroll snap” effect (full-screen scrolling) and it looks like the popularity of this feature is coming back. We even have our own small product for this feature implementation and we plan to release this JavaScript library soon so everybody can use it.

It has become very popular to use the Hubspot CMS for building landing pages. We can have the main website in WordPress, for example, but build specific landing pages in Hubspot. It is a powerful solution for the marketing team.

For all our websites, we work with our great design team and get clear requirements from the design department about the animations and any UI components.

What factors make the CMS department at Windmill stand out in terms of its quality and efficiency?

VO: First of all, these are the people who work in my team. Each of them is a professional in their field, loves their job, and aims to do their job as well as possible. In addition, they are wonderful people and we have friendly relations with everyone; we easily find a common language.

Another very important point is the process.

In our CMS team, the process of working with a project is very strict but understandable. Each member of my team follows this process impeccably, which allows us to automate many tasks, set short-term and long-term priorities for several projects for each team member, change priorities if necessary quickly and without wasting time for additional communication and discussion and without sacrificing productivity.

Our process allows me not only to control the quality of work and to help my team (as a technical leader) in time but also to own the actual and detailed information about each of the projects that we do, build the correct roadmaps, plan the delivery of functionality, and correctly allocate the resources of our team depending on the priority of projects (like a project manager on some projects).

Then, when we start any project, we estimate it first. The goal is not only to know how many hours we will spend on a particular feature, but to figure out all possible issues and unclear aspects before we start development. This helps reduce the count of risked points and positions us to take a proper architecture decision from the start.

Windmill Digital offers an extensive array of digital product strategy and design services that will make your products stand out in the market. To keep up with the latest updates, contact us here!

This series explores thought leadership at Windmill. It focuses on showcasing the great minds behind Windmill’s award-winning product design and development that our clients love.

Sergii Pashko is Principal Technologist at Topaz, a Windmill Ventures company, and leads the front-end department at Windmill.

What is the structure of the front-end department at Windmill?

Sergii Pashko: In our company, the front-end development department is divided into four parts: HTML/CSS, CMS, React, and Angular teams. Each of them brings irreplaceable value to product development, so each has a separate lead. I lead both the front-end development department as a whole and the Angular team specifically. 

Usually, the HTML/CSS team works together with design teams to bring the most daring designers’ ideas to life and to provide the ideal user interfaces that our company is proud of. The CMS team implements high-quality business websites and landing pages using content management systems like WordPress. They work mainly on PHP, JavaScript, CSS, and search engine optimization. The results of these teams are most visible to a wide range of audiences because they advertise businesses: Windmill Digital and Topaz Digital are brilliant examples of their work.

The case studies on Windmill’s website show the results of the Angular and React teams’ work on client projects.

Angular developers implement the logic of single-page applications. It is not usually publicly available, hidden beyond authorization flows and accessible only after signing up. Such apps solve specific problems of the product’s end-user and bring value to the business.

Front-end developers usually work in squads or project teams together with back-end, mobile devs, product owners, quality assurance engineers etc. Each product has from 1 to 15 front-end engineers, sometimes even more.

What role does Angular play in the front-end development department?

SP: Angular is one of the most used technologies for FinTech, Wellness, and some other domains in Windmill. It is a universal framework. It allows us to naturally transform the interactivity and functionality of web applications to provide the best user experience (UX). We use TypeScript (a superset of JavaScript), Angular’s modularity, routing, event handling, composability, unit testing, and more to bring structure and simplification to the application building process.

It is easy to learn this framework. Some developers implement one website after another in a hurry in most outsourcing companies. They repeat the same forms for many years in different projects, while they don’t even have a good understanding of JavaScript’s core functionality, patterns, and paradigms. It’s not required for small projects.

In our company, it’s different. We usually omit simple projects. Based on our low-code solutions over Angular, customers can create hundreds of various websites almost without coding.

How essential is Angular to the development and design of fintech products? 

SP: In the past, everyone was accustomed to banks requiring Java Applets to access user account details. It was a huge step forward from just in-person banking in boring offices, but still was not a perfect solution. Do you remember when banking software required installing a few levels of certificates and additional applications (like Java JRE) on your Windows PC? The software didn’t support either Linux or Mac, and some banks even required a specific version of Internet Explorer! Of course, that’s far from a great user experience as well as problematic in terms of accessibility and flexibility.

Since then, online finance products have transformed multiple times and nowadays even Google Chrome on your phone supports online banking web apps with no issues.

It’s exactly those cases where Angular is a great choice. Thanks to Angular’s Incremental DOM approach, which involves an optimized bundle size and memory footprint, web applications based on this technology have the best performance on mobile devices.

Performance and UX are significant, but what about security in Angular? Isn’t it the most valuable part for fintech?

SP: The most critical work in terms of security is usually covered at the infrastructure, backend, and transport (TLS) levels. But Angular is one of the best security options required for client apps.

It provides a proper architecture out of the box, built-in protections against common vulnerabilities and attacks such as cross-site scripting (XSS), request forgery (XSRF or CSRF), script inclusion (XSSI), etc. Angular treats all values as untrusted by default; it sanitizes and escapes them. Its HttpClient has built-in support for the client-side half of a common anti-XSRF and anti-XSSI techniques.

What are some key features of Angular? 

SP: Angular has a great modular architecture provided out of the box. There are many well-defined coding standards provided directly by framework creators. It allows you to be relaxed about architecture and spend more time on actual development.

Also, the framework has a command-line interface (CLI) for code generating, updating, scaffolding, etc. We also build our custom Angular Schematics that extend a base CLI functionality to speed up our development process.

Angular has a components approach, RxJS, high testability, a deep usage of TypeScript features that enhance the developer experience and code quality control.

What role does Webpack 5 play in your department? 

SP: Webpack is a static module builder for JavaScript applications. Version 5 with Module Federation was released a year ago and allowed developers to create separate bundles from a single application to build and deploy them separately. It also allows combining multiple apps developed with different technologies in one. We started hacking on it immediately. It wasn’t even officially supported by Angular 11 (the latest release at that moment).

Now, Angular 12 and onwards have the support of Module Federation. While many companies around the world only start proof of concept (PoC) projects on it, Windmill’s Team has finished its framework over Angular that helps to roll out new federated micro-frontends on this technology fast.

Was there any other way to implement Micro-frontends when Webpack 5 didn’t exist?

SP: Yeah, micro-frontend architectures have been around for a long time. I’d split them by integration approach: build-time and run-time integrations. I know many companies that use the first approach — they publish each sub-project as a separate NPM package. Then they use it in the main app as a library. It gives an appropriate level of flexibility: using various library sets allow you to implement a new app by combining packages in a new way. Still, build-time integration in most cases won’t allow the team to follow all the micro-frontend principles such as independent deployment.

Here we come to real-time integrations, which can solve this problem. For instance, the iframe approach is one of them, which existed even when nobody used the term “micro-frontend” for it. Also WebComponents which was presented in 2011. This technology has a native browser’s support. Then there was single-spa, a JavaScript router library for front-end microservices, and they have a few competitors, cannot recall the name of each now.

Nowadays, we can call all these approaches “traditional” while Webpack 5 module federation is the cutting-edge technology at the moment.

Are there any other tools you use in your job?

SP: Micro-frontends are just a hot topic in the front-end world and one of the reasons why good developers choose Windmill for their next job. We use Angular Material, Highcharts, Ag-Grid, Azure, Bitbucket, etc. Technologists always use the right tools for each part of their responsibilities, so the list of tools is almost infinite. In a few weeks, the list could change unrecognizably.

For example, for chats between team members we used Slack for some time, but then moved to Google Meet. A few months ago, we decided to try Microsoft services, migrated all the communication of one project into MS Teams. Now we are deciding to move back or try something else. We are not afraid to make mistakes but we won’t stay on uncomfortable instruments.

How important are tools like Git, Bitbucket, and VS Code/WebStorm compared to others?

SP: Usage of Git is an industry-standard now, just decentralized and one of the fastest and popular version control systems. Bitbucket is a Git repository management solution. In simple words, we store our code there, run builds, git-flow processes, but from project to project Angular team is flexible in choosing alternatives. Some projects may use GitLab, GitHub, or even Azure DevOps.

VS Code and WebStorm are competitors themselves. We build our projects in a way that supports both IDEs with no issues. If someone is more performant on VIM, Emacs, or even Notepad++, they are free to choose.

What expert advice can you offer an engineer that develops features to enhance the user experience?

SP: Usually, it’s not enough to just have strong knowledge of JavaScript, HTML, CSS, and one of the frameworks (like Angular, React, or Vue) to become a good front-end developer. They don’t only have to work on their tasks, but also need to have an understanding of the business reasons of the project, its technology varieties, and needs.

Spending ten years working on some technology doesn’t make you a Senior Developer. It depends on your attitude to work, attention to detail, and communication skills more than just how well you know Angular.

A good developer has to be proactive (developers shouldn’t say that they can’t do a feature because they don’t have a particular tool), understand the pros and cons of different tools, and handle a development process themselves. They have to feel like the project is their own business, as if they pay for its development out of their credit card. Good developers build projects that they are proud of.

Windmill Digital offers high-quality product design services. Our experts are highly skilled in their field and are experienced in creating exceptional products for our broad range of clients. For more information, contact us here.

Editors’s note: In the few weeks since the following interview took place, Akshata has been promoted to Windmill’s Senior Leadership Team as Windmill’s India team HR representative. We are immensely proud of Akshata’s development and progress at Windmill during her six years here! 

In the latest edition of We Are Windmill, we spoke to Akshata Bhandare about her career in HR and her journey at Windmill. 

How did you start at Windmill? Tell me a bit about your interview and first meetings with the team. 

It was 2017 and my previous experience belonged to the manufacturing industry, but here I was entering the IT world. My final interview was with the founder himself, Sunny Gambhir, who asked me just one question: What are you passionate about? This one question was enough for him to decide whether I was selected or not.  

While I was still feeling conflicted about whether I made the right decision to switch between industries, an incident came up in which a founder of a recruitment agency asked my manager if I could cope with the IT industry. My mentor confidently replied, “Yes of course, Akshata has potential and I am sure she will be able to do a great job!” This motivation was all that I required to keep me moving ahead and to live up to the expectations of my mentor. 

I was challenged enough by both my mentor and Windmill’s then-CTO of India, who always answered all my tech expertise-related questions. They wanted me to be technically strong, to avoid me looking unprepared or someone who does not have technical knowledge when I took technical interviews with candidates. 

How has the company changed since then?  

As I was handling an HR generalist profile, I was interested in the operations side of the things too. I was never asked why I required to know any information. I was supported by all my mentors and, as a result, I started looking into operations activities as well. Initially along with India, I also assisted for recruitment in Ukraine. 

As time passed, Windmill grew as an organization and we now have specialists for every activity.   

Focus on marketing has increased as compared to the past years, we have a dedicated marketing team taking care of several marketing campaigns and every individual in the organization feels responsible for the company branding. In short there is an awareness among the employees for the same.  

Roles and people performing those roles are clearer, the teams are becoming more aware & focused. 

How has Windmill supported your personal development? 

Windmill has always been an organization that gives opportunities to experiment with roles. In case an employee believes that he/she can perform a particular role or handle a function, they always get a chance to prove themselves and explore their career options.  

The company believes in the potential of their employees as much or sometimes even more than the employees believe in themselves.  

Windmill has helped me to grow myself in the IT domain. My knowledge of Agile & Scrum methodologies has also widened.  

Apart from HR, I have been given the opportunity to explore and deliver any role/function that I wanted. I have completed certifications and continue to pursue more as I am working at Windmill; this has helped me to stay updated with the current and emerging trends in the industry. 

What contributions have you made to the company? 

During the pandemic we were focusing on reimagining the fundamentals of the organization and rethinking the operating model and ways of working in the “new normal”. As an HR representative, I have played a central role in how the company builds organizational resilience and drives value.  

To be successful, a transformation should touch every face of an organization—people, process, strategy, structure, and technology. HR can help create an iterative approach by developing core elements of the people-management process, including new career paths for agile teams, revamped performance management, and capability building. The next step for me in the company is to link technology and analytics with day-to-day HR functions.  

The accelerating pace of technological change is widening skill gaps, making them more common and quicker to develop. To survive and deliver on their strategic objectives, all organizations will need to reskill and upskill significant portions of their workforce over the next ten years. This is where the HR function in Windmill can play a vital role to minimize employee skill gaps.  

What advice would you give to new colleagues? 

Windmill is an organization that believes in the latest technology and the potential of the employees. If you have the potential to work smartly and develop yourself, your efforts will never go unseen in Windmill. Windmill always has acknowledged and rewarded good work and effort.   

Do your best, upskill yourself, set clear goals & expectations to keep you moving forward.

 

Windmill Digital designs and builds outstanding digital products. Find out how your business can join the community of beneficiaries of Windmill’s experience-led design ethos.  

In this installment of Windmill’s Thought Leadership Series, we sat down with Alexander Molchanov, our seasoned engineering manager who also leads the HTML/CSS team. Alexander provided valuable insights into his area of expertise and discussed his experiences working at Windmill.

What is Windmill’s HTML/CSS team responsible for? 

Alexander Molchanov: Well, first of all, Windmill is a company that cares about design solutions, and, as such, there is a big team of great designers who create innovative experience designs. The HTML/CSS team works closely with designers to implement their vision and any avante garde ideas they have in the first-class web applications of our company. By keeping a keen eye for small details, using the best approaches and modern technologies, and improving the final results with several stages of testing and reviews, we bring this experience to end-users.  

We are also responsible for design systems, responsive design (rendering on displays of various sizes), accessibility, image optimization, SEO, email templates, and print styles, etc. Sometimes we can work independently on some types of projects, but mostly we work together with other development teams, such as Angular and React, on large, complex web applications. 

What are the key technical skills for HTML/CSS developers at Windmill?

AM: Of course, HTML and CSS are basic and key skills, but that’s not all. The list of key skills also includes SCSS, SVG, WAI-ARIA, JavaScript/TypeScript. Also, our work involves knowledge of React and Angular (at least at a basic level), GIT, design and build tools, UI component libraries, package managers, design systems, and so on. There are even more secondary skills, but it makes no sense to dwell on them. In total, the list of skills and knowledge areas in our Team Levels Framework consists of 87 items at the moment.  

We used to also learn and practice jQuery, PHP, MySQL, server administration for our WordPress-based websites, but now another team is in charge of that, so we have more time to hone our core skills and learn some new related technologies. 

What other Front-End teams are there in the company? 

AM: Currently there are four Front-End teams in the company: HTML/CSS, Angular, React and CMS. Each team has many excellent specialists in their field, who have years of experience behind them and are still intensively developing to reach the peak of their capacity and efficiency. Depending on the requirements of the project, selected technologies and some other aspects, front-end developers from different teams form mixed sub-teams and united in squads with other teams (such as Back-End, Quality Assurance, Management, etc.) jointly develop modern and high-quality products of the company. This model has proven itself, especially in large long-term projects. 

What do you think is the advantage of highly specialized Front-End teams? 

AM: The main advantage is the ability of such teams to create projects of any complexity with well-thought-out solutions and excellent quality. 

It’s no secret that every developer is limited in the way of his development by a number of factors, for example, the ability to assimilate a certain amount of information per unit of time, free time for learning, memory stability, monotony or technological limitations of projects, and so on. In addition, technologies do not stand still and are continuously developing, supplementing, changing every day. Also, new auxiliary tools appear, new specifications come out, more and more libraries and frameworks are invented, while something becomes irrevocably outdated and loses its relevance. 

And all this leads to the fact that it is easier for developers with a smaller technology stack to stay on the wave of relevance. They have more opportunities not only to go as far as possible into the jungle of their technologies, experiment, practice non-standard approaches, understand the slightest nuances and specifics of the selected technologies, but also more often and deeper to track any innovations. They hone their skills almost to the ideal, can solve the task of any complexity within their specialization, write cleaner and more optimized code, make fewer mistakes, use significantly fewer hardcodes and workarounds, etc. 

If we talk about developers with a wider technology stack, they are more versatile, but at the same time, their knowledge and skills in each individual technology are less than highly specialized developers. Therefore, the quality of their code and the visual part are often worse; complex tasks take longer to solve or are even rejected; or for some solutions, cumbersome alternatives or third-party libraries are used instead of several lines of correct code, etc. As a result, projects can look worse, work slower, have more different problems, and it’s harder to maintain them. 

Nevertheless, any specialists are in demand now. As for the choice between highly specialized and cross-functional specialists, it depends primarily on the company’s goals, expectations, and quality requirements. 

Does knowing other technologies make you a better web developer?

AM: I think it’s useful to be familiar with other technologies. This can help you better understand all stages of project development, work with other teams more easily, resolve various problems. But it’s important to find the line because spending too much time on other technologies can negatively affect your core skills. In addition, not all technologies might come in handy, so it’s not really good idea to waste your time on them. Everything must be wise. And everything needs a reason. As for me personally, I can spend up to 20 percent of my time studying other technologies that are interesting to me and useful for projects. 

What are your main responsibilities as HTML/CSS lead? 

AM: All my responsibilities can be roughly divided into 3 groups: general, project-related, and intradepartmental.  

The general responsibilities include the development and updating of standards and technical documentation as well as universal modules and libraries; the introduction of new technologies and optimization approaches; the development of trial tasks and evaluation systems; prescreening candidates and holding technical interviews; communicating with other leads and top-management around high-level questions; knowledge sharing between departments; and participation in resource planning and allocation, and so on.  

Project-related responsibilities contain the following: communication with clients and team members, analysis of the project goals and technical expertise, project planning and estimation, support in resource management, work on project architecture and technical solutions (together with other leads), technical documentation, regular code reviews, VQA, development strategy, and refactoring plans.  

I also have intradepartmental responsibilities, which include department development strategy, team expansion planning, technical onboarding and continuous support, integration scheme, mentoring, team documentation, OKR process, inventing and conducting various training events (like code hackathons, workshops, technical meetups, etc.), review and verification of developer skills, supporting materials and learning programs, review of developers seniority level, knowledge sharing, introduction to new technologies, team motivation, resolving various issues, and corporate events. 

What is the prevailing atmosphere in your team?

AM: Actually, I’m very proud of my team. This is the case when the team consists not only of cool developers but also of good sociable people. We have a very friendly and exciting atmosphere. All the guys in the team are very positive, without arrogance and pomposity, they are always ready to help each other, support in any matter. We often hold various events, like to brainstorm and resolve issues together, periodically meet outside of business hours to discuss work and personal issues. Of course, it helps to work better, easier and more fun! 

What technologies have you started using in recent years?

AM: Since we stopped supporting the Internet Explorer on our projects a few years ago, and nothing else holding us back, we have begun to use the full power of modern CSS. We have started using CSS Grids, CSS custom properties, content-based intrinsic sizes and context-based extrinsic sizes, logical properties, new functions, various modern properties and values that were not supported by IE, etc. We also abandoned almost all vendor prefixes, stopped using different fallbacks and polyfills, optimized old mixins, and so on.  

With the start of React projects, we mastered a new javascript library and a number of new knowledge, started using [React UI library] Ant Design, learned styled-components, discovered new auxiliary tools for facilitating our work and automating some processes. There are also many interesting plans for the near future, but it is too early to talk about them. 

How does the HTML/CSS team ensure the best implementation of projects?

AM: We always take care about the quality of our work. Years of experience, responsibility, well-coordinated teamwork and a number of established processes help in this matter.  

So first of all, it is an individual approach. Even at the project planning stage, we carefully review all the requirements for the project and the client’s expectations, thoroughly analyze them and choose the best suitable technologies taking into account possible risks and scalability. 

Secondly, in the process of working on a project, each piece of code goes through several levels of thorough code reviews by different developers. Also we do visual quality assurance, stress-testing, conduct code optimization sessions, and so on. 

Thirdly, we have multi-level testing, which includes both automated testing and manual testing in various conditions at different levels: by developers, tech leads, designers, QA engineers, and managers. 

Fourthly, we periodically conduct global code review sessions between sprints and collectively decide what can be improved. There is always something to cut, optimize, redo or refactor. Thus, the project code is not littered and is always under close scrutiny. 

Finally, we carefully test the project at the stage of completion and put the final touches on it.  

What are you doing to train HTML/CSS developers quickly and effectively? Are there any training activities in the team? 

AM: I think we have succeeded in this direction. In addition to a good mentorship model, OKR process, general development programs and shared training materials, we have a number of training events within the department. Some of them are code hackathons, workshops, technical meetups, master-classes. 

Code Hackathons help developers to improve their practical skills on the top level, better analyze tasks and make the correct decision, look at problems from all angles, think outside the box, improve their ability to work under the pressure and with tight deadlines. And all this without real stressful situations on the project, but in a gambling and interesting way. 

Master-classes help broaden the horizons of developers. At them, we analyze all possible options for solving one problem in different ways, both obvious and very unexpected alternatives, find and discuss the best approaches, share experience and ideas. 

Workshops have many different advantages: learning new technologies and the latest updates in existing ones, consolidating old knowledge, improving teamwork skills, and finding common interests by developers. Fairly often these events take the form of quizzes, mini-games, interactive exercises, collaborative coding, or group discussions. 

As for technical meetups, they can be held by developers on absolutely any topic that is useful to the team. The history of all meetups is archived and available for new developers to study. 

Usually, we have up to ten events per quarter. This is enough to constantly improve the overall technical skills of the team, and at the same time not overload the developers.

What are the career prospects for developers in your specialty? 

AM: Our specialty is a good option if you would like to start your career in web development because HTML and CSS are key technologies in this area. Each web developer, regardless of direction, should know at least the basics of these technologies. After a few years of study and practice, you can choose your future path: Continue to grow and become a great specialist in this direction, or easily switch to Angular or React (for example) or to technical project management, or whatever you like. There are no boundaries here. The main thing is to know exactly what you want and where you would like to go. Any specialists are valuable in the market, but only if they are good. 

What advice would you offer fresh graduates pursuing a career in your profession? 

AM: The most important thing is to be diligent and attentive. Try to spend as much time as possible on learning and practice, at first preferably not only during the day, but also at night. Do not miss the chance to dig deeper, experiment, look for popular solutions to average problems and compare them with your own solutions. Always think and analyze, do not learn automatically.  

In terms of learning itself, it is now much easier because there are guides, videos, and courses available on the internet for any budget. You can experiment with different types of training and understand what you like best and understand better. I would highly recommend taking some interactive courses. I will not advertise any specifically for obvious reasons, but you can easily Google and choose the best ones by rating. 

Interactive courses are a very interesting approach where you learn theory and immediately practice in a playful manner. This causes additional interest and excitement and makes learning not boring at all. In addition, it would be good to find an experienced mentor who will help you with advice, direct you on the true path, and point you in the right direction. A good mentor will shorten your learning time by several times and help you avoid the most common mistakes. 

Finally, could you say a few words about working for the company? 

AM: I’ve worked at Windmill for over 5 years. That already says a lot. We have a good general atmosphere in the company, with many great specialists, interesting complex projects, high team morale, and good career opportunities. What else does a developer need for happiness and self-realization? Of course, there are some challenges that can happen in any work, but they are rare, minimal, and quickly resolved. So in general everything is great! 

Windmill Digital offers high-quality product design services. Our experts are highly skilled in their field and are experienced in creating exceptional products for our broad range of clients. For more information, contact us here. 

Imagine this: You’ve just started your job as a junior UX designer and, like everyone else, you’re looking to climb up the ladder. Meeting your boss’s expectations is not only a must, but it will ensure your success in the job role. But how to achieve this? 

This blog will mention essential factors one must consider to pave their way into leadership roles as a designer. These include working to requirements effectively, encompassing a rounded set of skills, and efficient time management skills.

Working to requirements

The #1 skill a junior designer needs to prove is working to requirements. This means having an in-depth understanding of client needs and then successfully translating those requirements into design.

At the middle designer level, responsibilities shift. Middle designers are responsible for clearly defining and framing requirements.

Meanwhile, senior designers are responsible for major discoveries. When it comes to having a global workflow, they understand the need for more facilitators and coordinators throughout multiple teams. Not only are they more involved in understanding client requirements and seamlessly turning them into design, but they tend to contribute less to the actual design interface and instead focus more on research. The main goal of a senior designer is to discover more options and have maximum engagement with stakeholders. They also start to work with budget clients.

Rounded skill set

For a junior designer, proficiency in a broad range of UX design skills is desirable. Competency in and knowledge of Design Thinking tools; research knowledge; and visual design flair form the foundation of a successful UX designer. UX designers should also have a grounding in: 

  • Prototyping
  • Wireframing
  • Visual design software
  • Research and usability testing
  • Information architecture
  • Application development

As a UX designer takes on more responsibility, skills don’t become less important, but instead, focus shifts. Activities like user research or stakeholder engagement and discovery will begin to occupy more attention than the user interface (UI) itself.

There will come a time to decide whether to follow an expert track or managerial track. The expert track will see you lead in a particular aspect of design that you’re strong in; while the managerial track involves, like it sounds, managing a team.

Time management

UX design leaders tend to have busy agendas packed with client meetings and internal and other team meetings, among other commitments. Having their agenda booked for them can become challenging to manage, making it difficult to take time out for their design work. It’s common for design leaders to reach the end of the day and feel like they still need to do eight hours of their own design work.

This is where their time management skills come into play.

UX design leaders know how to allocate their time in the right places and don’t hesitate in saying no. They prioritize their tasks according to urgent and important assignments, but naturally, they first cater to the urgent ones first.

Concluding thoughts

While there may be no definite path to design leadership, the role entails certain engagements and prioritizing not every designer might be ready for or keen to do. For junior designers looking to enter the world of design leadership, it’s vital to understand what the role may ask of them and how much they will be able to offer it personally.

Find out how Windmill Digital’s digital product design services can accelerate your product strategy, contact us here!

What does it take to put together a world-class design team that can take on any challenge?

Taras Bakusevych has set out to explore that as Principal Designer at Windmill Smart Solutions.

Taras began his professional journey in architecture, studying interior design. He didn’t study product design specifically, but much of his coursework focused on graphic design and digital art, lending perfectly to an eventual career designing digital products.

After spending some time in various startup environments, Taras joined Windmill as a UX/UI Designer. It was a small team back then, so he spent a lot of time working directly with our CEO, Sunny Gambhir. Starting with visual enhancements to some of Sunny’s original designs, Taras eventually moved on to providing structural direction, and today he oversees the design process of every Windmill product.

“From setting the right expectations for clients, to daily operations and project management, there’s a lot going on at any given moment. I’m grateful to have grown to a position where I can help spearhead some of these areas as we work toward the company’s growth” he shares.

Designing the Future

One of the things Taras enjoys most about Windmill is the clients he gets to work with, and the high level of trust placed on his team.

Many of these companies depend on the products we build to propel them into the next phase of their evolution. We’re building the future.

“In order for the company to be successful, we need a dedicated, mature, and diverse design team that works well together,” Taras continues. There’s always a new challenge to tackle, and sometimes it can even feel addictive. Jumping from one task to another keeps Taras engaged in his work, and while he admits that it can become difficult to focus at times, he attributes much of his success to this environment of constant change.

“Sure, you’ll get stuff thrown at you. But if you’re able to take on the challenges presented to you and design creative solutions, there is unmatched reward in the experience. It’s how I learned so much so quickly and continue to learn every day.”

Meaningful Connections and Contributions

It goes much further than designing great products. “It’s like a family here”, shares Taras. “It’s never about the numbers. We don’t grow for the sake of growing. We want to gather a group that genuinely enjoys working together, and we hope that each member of our team always remains connected to the relationships and experiences they build here.”

“You’re very much in control of your path here,” adds Taras. “Our goal is always to align everyone’s individual goals with the overall mission of the company, and we openly encourage freedom of expression. Each person is empowered to share their vision. We want everyone to contribute toward moving the company in the right direction.”

Building a World-Class Team

Windmill is rapidly expanding, with new designers joining the team all over the world. Over the next six months, Taras plans to focus on training his new team members and making sure they gain exposure to varied projects that help develop their skills.

“We have a lot of incoming projects, and we want to make sure our designers are prepared to take them on,” Taras shares.

Looking further toward the future, Taras and the Windmill leadership team are looking to gather the best of the best in design. “We want to build a uniquely talented team, one that has the ability to tackle any design challenge at any scale,” says Taras.

“Design is not just about visuals. It’s deeply embedded in the product development process. It’s a journey we take with our clients. If it’s not enjoyable, what’s the point? We want to take an enjoyable journey altogether, one that benefits the growth and development of all involved” he remarks.

We can’t wait to see what’s ahead for Taras and his team. Follow us on LinkedIn to stay tuned into the latest from our designers and others.

Interested in learning about open roles at Windmill Smart Solutions? Check out our careers page.

Recently, I had a conversation with one of our principals, Miles Hobart, where we discussed the importance of understanding the reasons behind our daily actions. As a company, our purpose and passion will largely influence our direction and accomplishments. In this post, we will explore some of the fundamental principles that guide us at Windmill and enable us to achieve our objectives.

Joy at the Core

At the heart of everything we do, I believe that joy should be the driving force. We aim to establish a work environment where our team can be themselves, enjoy what they do in their roles, and contribute their expertise to enable growth. Our teammates are our partners on this journey, and our objective is to make the journey pleasant for everyone.

Embracing Abundance and Gratitude

Another key principle for me is abundance. By embracing abundance and gratitude, we can approach each challenge with a clear mind and bring our best selves to the table. We are grateful for everything we have, from the designs we create to the people we work with, and we are inspired by the possibilities we have as a company to make a difference.

Fostering Creativity and Craftsmanship

Creativity is another vital concept that I strive to embody. I believe that creativity is not limited to our design teams; it can be expressed in every role, from development to talent acquisition. Creativity is a simple and innate trait among humans, and we can all be craftsmen if we approach anything we do with reverence. By fostering a culture of creativity, we can continuously innovate and find new solutions to complex problems.

Continuous Challenge for Growth and Development

Lastly, I believe in creating a company where everyone is continuously challenged for their growth and development. We understand that our greatest hurdles in life serve to foster the most personal growth. As we work together to achieve our goals, our aim is to create an environment where everyone is motivated to do their part. Growth is about people, and the more we can establish a secure environment where our employees can expand their minds and experiences, the more we can do as a company to enhance the development of our interconnected world.

In conclusion, my purpose and passion are guided by these core principles: joy, abundance, creativity, and growth. We believe that by embodying these principles, we can achieve our goals and make a meaningful impact in the world.

In March, Windmill held its first roundtable in support of International Women’s Day (IWD).  We facilitated conversations with women in tech, design, human resources, and management and found a unified voice that honored the day and the careers development of Women at Windmill. 

With offices in the US, Portugal, the United Kingdom, Ukraine, Switzerland, and India, Windmill’s diversity is one of our key strengths. And as a company with large tech and IT teams, it is Windmill’s responsibility to make sure those career pathways are as open to women as possible.

What does IWD mean to you?

International Women’s Day is a day like any other but also one for remembering that, for the most part, the world is inching closer to gender equality. As a company whose workforce is so internationally diverse, the question of the personal significance of IWD produced a broad range of perspectives. 

Every day is women’s day according to Susana in Portugal, and similarly in Ukraine, where IWD is a National Holiday, Khrystyna feels that a kind of restrictiveness around March 8th, of that being the one day to platform women’s views, has been shrugged off, women’s voices are heard every day.

In contrast, for Luidmyla, IWD is a day to celebrate women in a literal sense – to be waited on and to receive flowers and presents, not even leaving bed to make coffee! A “Queen day” as she calls it! Additionally, Sarika based in India spoke of an office culture at a previous workplace where the men brought in gifts for the women. 

It is great to see the different way IWD is appreciated and regarded around the world, and specifically within Windmill.

Challenging oneself

The theme of this year’s IWD is #ChoosetoChallenge, and challenging oneself was a common theme during the discussion. A point of unity was the importance of determination and belief in yourself in handling difficult situations at work in the face of doubts and fears. Susana was not afraid to share her strategy of having a “little cry” in the restroom to gather herself; while when faced with a difficult task, such as submitting an important application, Khrystyna reminds herself of a Scarlet O’Hara quote, but inverses it: Instead of “thinking about it tomorrow” she acts now and deals later with any negative feelings that arise.

For Christina, visualisation is a powerful tool that should be used from early in one’s career. “If you want something, believe it first then be it, she said. One of the biggest obstacles we face is that we don’t do ourselves justice in imagining success — we do it for others but not ourselves. Moenika, based in London, echoed those thoughts, saying that sometimes the best opportunities are scary and that we are more capable than we know — facing down self-doubt and untrue opinions of yourself is crucial to self-development.

Akshata sees speaking your mind as key to inner peace. For her, it’s important to put your point across even if you think it’s “crappy” as it will put your mind at peace and you won’t be regretful for not having said anything at night. There’s not much to lose, so don’t be afraid to fail.

Challenging externally

The IWD roundtable turned from challenges of the self to to ways women had challenged their external environments. Representation of women in senior and managerial positions was commonly identified as being important to see as well as to become oneself. Sarika was encouraged to become the first woman from her group to leave India for Europe, while Moenika was successful in becoming the president of her university’s computer science club to show that women belong in such professions — in many ways embodying Christina’s mantra of believe it then be it.

Windmill is committed to supporting women in all roles and believes that with this stance, more people will be inspired to excel in their careers without gender stereotypes.

View Windmill’s current vacancies, including design, developer, and engineer roles, on Windmill’s careers page.

Throughout my years working in HR, I’ve had many interesting conversations about the need for continuous learning — keeping our skills sharp, learning new ones, and always staying ahead of curve, no matter our industry our job role.

Most people agree on the importance of continuous learning, but when faced with the realities of our daily and weekly routines, sometimes it feels impossible to step back from the churn and focus on our own development.

Here are some tips to help you prioritize and get in the right attitude to promote learning and growth.

1. Connect the dots to find meaning.

How many times have we gone through the motions of learning something simply because we were forced to, such as in school? How much did we retain from those scenarios? Probably not much, because we were unable to transfer the information from our short-term memory to our long-term memory.

In order to avoid this common pitfall in our careers, it’s important to consistently check in with ourselves to make sure we’re headed in the right direction. Some questions to ask include “why am I learning these new skills?”, “what direction will these skills enable me to take?”, and “how will this be useful to me?”

Connect the dots between your purpose, your vision, and your daily impact and you’ll start to find more ways continuous learning can help you be even more effective, in every aspect of life. Finding these real life connections to our work and understanding how it all fits into the larger picture of our personal and organizational growth is key to successfully learning and retaining knowledge in the long-term.

2. Stop believing in the talent myth.

For decades, I made the mistake of believing that talent is innate — that you either have it or you don’t. Struggling to figure out my own talents, I spent a lot of time asking myself the wrong questions.

I now know that talent is determined less by our genes and far more by our actions. In the science-fiction movie Gattaca, the main character (Vincent Freeman) brilliantly depicts the reality of the situation: despite all that is dealt to him at birth, he proves that through determination and smart choices, we each have the power to realize our dreams just as he does.

While there is always room for improvement, continuous learning starts with the acceptance that you don’t never have to have everything figured out. As long as you’re striving to become better every day, dedication and persistence will always prevail, leading you to success.

3. Learn to learn!

Skip the Laptop:
While an incredibly useful tool, reading from a computer or typing isn’t the best way to learn. Taking notes the old-fashioned way on paper is proven to be a much better way to retain information. Instead of transcribing everything you hear, try to reframe the information in your own words and draw your own connections for better results.

Get Moving:
Physical exercise can help clear your head, putting you in a better mental and physical state to retain information and successfully learn. Rather than wasting your time cramming your mind with more information, take a break for some light physical exercise before getting back to work.

Sound it Out:
It’s scientifically proven that reading something out loud helps with remembering it later on.

Find What Works:
Learning is a journey and not a destination. It’s never too late to identify your own learning style and figure out what works best for you. In order to expand our knowledge, we must first recall how to learn.

4. Learn by Doing.

It’s natural to do some research and brush up on theory before we try to put our knowledge into practice, but at some point, we must get out there and put it into practice. Whether it’s a language, cooking, playing a sport, or setting up a business, the only way to learn is to actually experience it, refine our approach, and continuously improve.

5. Allow yourself to fail.

No one likes to fail, but our risk of mistakes naturally increases as soon as we step out of our comfort zones. Try not to be so hard on yourself as you try new things. Remember that failure is not a negative experience, but rather an integral part of the learning process. It’s from our mistakes that we can learn the most, examine what didn’t work, and try again for better results next time. Flip the narrative in your own head to embrace failure and encourage perseverance.

6. Seek honest feedback. 

Honest, high-quality feedback is a valuable gift for better self awareness and gaining new perspective. Respectful disagreement and opinions that challenge our own perceptions have the power to stimulate intellectual thought and lead both sides toward greater excellence. Reach out to some trustworthy colleagues to see if they have any advice on how you could improve, and incorporate that feedback as you continue to learn more.

7. Keep track of your learning and reward yourself. 

Life itself is a journey, whether we are conscious about it or not. It’s important to take a break and pause for a moment sometimes, and reflect on what you’ve recently learned. How is it impacting your work? How are you implementing this new knowledge and what are your next steps? Regularly checking in with yourself and being proud of the progress you make day by day, or week by week, is key to remaining curious and ready to move toward each new learning experience.

With these tactics in mind, you can get yourself in the right mindset to learn more each and every day. It’s all about the choices we make and the attitude with which we approach each new experience. It’s up to you – what will you choose to learn today?

The capacity to learn is a gift; the ability to learn is a skill; the willingness to learn is a choice. -Brian Herbert

Having spent his entire career in product, including related stints in strategy, partnerships and business development, Miles Hobart — UK Principal here at Windmill Smart Solutions — knows a thing or two about what it takes to deliver digital innovation. For Miles, it’s about the freedom to do it our own way.

Miles spent a lot of time at much larger organizations where the real decision-making is more of a top-down, lengthy process, so he welcomes the shift to something new. “At Windmill, I get a chance to truly sink or swim with my colleagues based on the decisions we make” says Miles.

This kind of symbiotic relationship with his work gives Miles a chance to truly connect with customers and figure out how to best serve their needs – something that’s not always easy to find.

Being part of a large firm feels a bit like being in a cocoon. There is often little direct involvement in strategy or decision-making, and indeed, customers, making it difficult to feel a personal connection to one’s work

That’s not the case at Windmill. 

“Joining Windmill has given me the opportunity to make things a lot more real. I’m able to help make more of an immediate impact on our customers’ success” he says. “I can also see the concrete impact of decisions made across the whole company, the interdependencies between the different functions, and ultimately the business impact on customers and on the satisfaction of our own teams.”

From overseeing the company’s growth in the UK, to helping scale the organization globally and spearheading new business opportunities abroad, Miles is involved in a number of strategic initiatives that are set to determine Windmill’s trajectory over the next few years. 

He is particularly excited by the projects he is leading in 2020 for the Ventures arm of the business in the areas of enterprise collaboration and private banking. 

Miles is currently driving recruitment for several key teams as Windmill continues to bloom year after year.  “A company is only as good as its people, and we’ve got great people” he continues. “We’ve got a lot of creative thinkers and the right mix of talent. We have what it takes to be successful, and we need to continuously build on that with the right people. It is time-consuming but necessary to ensure we get it right.”

This is a fast-paced, dynamic environment. Things are always changing, and there are always new opportunities for anyone who wants to seize them; proactive individuals will thrive.

For Miles, Windmill offers a rewarding mix of product design and delivery, making it possible to see projects through end-to-end. “It’s a much more fulfilling experience for people who have a passion for product,” says Miles. “Ultimately, it’s about building products on our own terms, using our skills to build the best possible products, and taking some risks to see what can succeed in the market. It’s about opportunity and freedom.”

“That said, from a leadership perspective, we have to be continually alert to the danger of taking on too much and spreading ourselves too thin” he cautions. “There is a lot of opportunity out there! We are conscious of this and rigorously prioritize our activities, and challenge each other on this, so we are always adding the most value.”

Windmill presents fantastic opportunities for Miles to personally learn and grow and also to nurture others. He especially enjoys mentoring younger team members, helping to steer them ahead and offering advice on how to evolve throughout their careers. So far, working with such a motivated and inspired team and coaching them toward their own success is one of the best parts of the journey. 

Outside of growing Windmill’s products and services, Miles loves to stay active and spend time in nature. When he’s not working, he’s hiking in the mountains during summer or skiing in the winter as much as possible. Keeping fit and hanging out with family and friends and dog are what help Miles stay grounded and focused. 

As we dive into 2020, Miles is looking forward to ensuring successful delivery on all client engagements and helping propel Windmill’s growth across the board. The new decade is ripe with opportunity for impactful teamwork, personal development, and even greater innovation. If this sounds like something you’d like to be part of, be sure to check out our open roles on our Careers page.

What does it take to build something truly remarkable? That’s a question we ask ourselves every day at Windmill Smart Solutions.

As a company that designs and develops next-generation digital products, we each have a lot of individual experience in building remarkable digital experiences; but collectively, we are more than a group of developers, design thinkers, and agile practitioners – we are a team on a mission to enrich our human experience as well, while making an impact through our work.

Acting with Passion

At the core of passion is love, and here at Windmill, we truly love what we do. We make a great team because we each have an individual personal connection to our work, and collectively, we believe in the power of making a positive impact through design. We have a passion for helping each other, helping our community, and helping make life a little bit easier for our clients and their customers through the innovative digital products we create.

Taking Ownership

There’s a lot of room for confusion out there, so we always take due diligence to be crystal clear on each of our responsibilities. By knowing what is expected of each of us, we’re able to work faster and more effectively toward our goals. Taking ownership helps us minimize inefficiency while maximizing productivity. Ultimately, it makes our team stronger and enables us to provide exceptional client service.

Honesty and Transparency

Open communication and a strong sense of trust enable us to build a sustainable and successful company together. That’s why here at Windmill, we’re always honest about our abilities and intentions, as well as our mistakes. We remain upfront about our emotions and concerns, and we never judge or censure anyone for sharing how they feel.

Mutual Trust and Respect

We are all partners in this journey we call life, and as such we always see each other as fellow human beings first. This small act of compassion makes a big difference in how we relate to each other; ultimately it makes us better designers, innovators, and critical thinkers, and more well-rounded as a whole. We strive to maintain mutual trust and respect so we can all enjoy positive interactions, valuable connections, and a healthy work environment.

Open Mindedness

We live in an age of boundless potential. Keeping up requires agility, and agility begins in the mind. We’re continuously testing our assumptions and sharpening our knowledge – it’s how we stay prepared to face every new challenge. With each iteration comes a chance to improve our ideas, foster greater innovation, and propel ourselves forward toward greater success.

Interested in Joining Our Team? 

Opportunities for innovation in this fantastic digital world of ours are abundant. We’re thankful for a team that makes the journey of discovering them so worthwhile. We’re always looking for like-minded professionals whose values align with our own. If this sounds like something you’d like to be a part of, check out our Careers page to learn about open roles.

Windmill was started with a single goal in mind – designing and delivering impactful experiences. As we are expanding, we are gathering the best talent and a passionate team with great leaders to come and be part of our journey.

We are building a fun team, from design to development to growth and products, I enjoy working with the team and sharing our understanding and experiences as we learn and grow together.

says Sunny.

In his own life, Sunny has experienced all styles of management and it reflects in how he manages as well. He’s grown into his role slowly by looking around and seeing what works in which situation. At Windmill, leadership is a joint effort and the company takes a lean and agile approach to it, appointing a handful of executives to the leadership team and rotating the title of CEO.

We very much believe that there should be no single point of control or failure. I’ve taken the title of CEO because someone has to have it, but it doesn’t mean anyone else in the core leadership team won’t have that title in the future. We share a vision but there is no single right way or person”, Sunny notes. “Having all these different people working together and understanding the vision without ego is how we approach leadership.

Design Thinking + Lean is at the core of Windmill Smart Solutions, and it’s prevalent in every part of the company.

We internally run design thinking workshops to enable better understanding and definition of needs and gaps. We try things, we see what works, we discard what doesn’t work, and we continuously improve what does work.

says Sunny.

The next two years will be crucial to Windmill Smart Solutions as the company looks to launch a wide range of products and projects and grow our teams in various locations. A key to our success is maintaining our continuous focus on quality and happiness at work.

In our leadership meetings, we asked ourselves what we really want to do – what is our focus? Is it revenue, growth, or quality of work? And what we all said is that we want to be selective and maintain the focus on greatness and quality in whatever we do.

The company always aims to work on a manageable number of projects, enabling us to focus and deliver truly great solutions. This allows for a team where each person is a valuable contributor toward success. 

“We’ve been growing, but there’s nothing more we want to do other than build great products, Windmill exists to create great experiences. That’s more than enough”.

says Sunny.

Sunny is proud of this atypical approach. “Everything in my life has been unique and full of great surprises.” he says. “This is reflected in the spirit of Windmill – everything we do is out of the box, we’re never in the box.”