Industry: Software Development
JetBrains products used: WebStorm, IntelliJ IDEA, GoLand, PhpStorm, PyCharm, DataGrip, TeamCity
Organization Size: 100-250
Country: Poland, United States, United Kingdom, Germany, Austria, Switzerland, Belgium, Netherlands, Luxembourg, Denmark, Norway, Sweden
Miquido
Miquido is a product strategy consulting company that assists clients with the development of digital products – from ideation through to their arrival at a market-ready stage. Headquartered in Kraków, Poland, Miquido operates globally, with a particular focus on the US, UK, Benelux, DACH, and Scandinavian markets. It employs 220 people, 120 of them developers.
“We’ve chosen JetBrains for three reasons: convenience of use, configurability, and the easy availability of plugins.”
— Piotr Polus, Frontend Tech Lead, Miquido
What does your company do? What are its main offerings?
Our cross-functional team of experts supports companies at every stage of development for their digital products. Aside from design and development, we offer our clients a complementary set of services that includes:
- Shaping the product vision
- Competitive analysis
- Business and market insights
- Roadmap recommendations
- Product strategy development
- Defining the minimum viable product
- Prototyping
- Product scalability
Which industries is your company primarily involved in?
We excel at delivering digital solutions for FinTech, entertainment, travel, and e-commerce.
What JetBrains products do you use in your work processes?
On a daily basis, the Miquido team uses WebStorm, IntelliJ IDEA, AppCode, GoLand, PhpStorm, PyCharm, DataGrip, and TeamCity.
What led you to look for JetBrains products or alternative solutions, and what other solutions did you consider?
A few years back when we were a growing software company, we were searching for a partner that would help us:
- Scale and unify all the tech processes in the company.
- Offer the best possible experience for developers.
JetBrains solutions helped Miquido grow from 50+ to 200+ team members. All throughout this time, we used TeamCity and Upsource to support our processes. JetBrains IDEs became the default tools for four Miquido dev teams: Android, Frontend, Node JS, and PHP.
We’ve chosen JetBrains for three reasons: convenience of use, configurability, and the easy availability of plugins. And what are our conclusions? To quote our Android team:
“There is no better alternative to JetBrains tools when it comes to Android development. None of our developers are considering (or have ever considered) a change of tools.”
— Jan Hudzik, Android Tech Lead, Miquido
What challenges have you faced while adopting JetBrains tools?
Initially, TeamCity had a fairly high entry threshold for developers with less work experience.
On the one hand, its configurability gave us a lot of options for adjusting the CI / CD. On the other hand, developers often felt overwhelmed the first time they used the tool.
Please describe any particular issues or tasks that JetBrains tools have helped you address or even resolve entirely.
At Miquido, we take on a lot of different projects at the same time, and the variability of these projects is very high. For example, the pipeline of an iOS mobile application requires a completely different approach than a microservice backend or a static web frontend.
“Over the years, TeamCity’s flexibility has allowed us to keep 100% of the CI / CD process in one tool. Its flexibility meant that we built all our solutions in one place, and the knowledge about the subject was concentrated in one single space.”
— Piotr Polus, Frontend Tech Lead, Miquido
What goals are you striving toward, and how do you plan to use JetBrains tools to achieve them?
We’re currently planning to use Code with Me for sharing code during team and pair programming. As we’ve turned to remote work in the time of the pandemic, it seems like a great tool to test and introduce into our daily workflow.
Also, we can’t wait for the new JetBrains tool – Fleet!
Do you have any tips or advice you’d like to share with our readers?
Well, we actually have two suggestions:
- Check out the IDE plugins. They will surely help you organize the exchange of knowledge between your DevOps team and developers.
- TeamCity is not such a difficult tool. In fact, it lets developers take over some responsibilities related to CI / CD.
Similar Customer Stories
OpenStack
Swapnil Kulkarni, Active Technology Contributor, OpenStack
PyCharm has tons of advantages when compared to text editors in terms of supported functionality. With respect to Python development, PyCharm definitely stands out with features like remote debugging, code quality checks, and integrations with third-party software like Docker and Kubernetes.
IT Manufactory
Varij Kapil, Software Developer, IT Manufactory
We are still in a phase where we are building new features and functionalities on top of our main product, and sometimes a lot of things change in a lot of places. Breaking changes and refactoring need to happen in multiple Java modules and React components. Making such huge changes would not have been possible without JetBrains products.
The Ensign Services
Joshua Bigoss, Director of Data Services, Ensign Services
My team could not have responded to the needs of our organization during the pandemic without the agility and precision that Space made possible. In 2020 my team and I had a lot of 12 hour days and 7 day work weeks. There were months of being woken up at 3 am by anxiety, stress, or fear for our residents and caregivers and the ever-changing needs of our organization. But I never once had to think about effective communication, collaboration, or availability and was grateful to have this tool.