Technology Roundtable: Choosing the Right Technology Stack for Your Project
Wonderment Apps is proud to present the Technology Roundtable, our insight series into the technical management and development process. As a group of engineers, we would like to provide some perspective into the technical processes throughout the lifetime of a technology buildout. In this episode of the Technology Roundtable series, we talk about choosing the right technology stack for your project and what factors impact this decision.
How to Choose the Right Technology Stack for Your Project?
Choosing the right technology stack for a digital project has become challenging in the past recent years. This difficulty is mainly due to the number of available options in different parts of the application stack, such as cloud infrastructure, database systems, back-end, and front-end stacks. There are several deciding factors to choose the right technology stack for your project.
Cost of Development
- Some development stacks can be more expensive than the others due to developers’ average cost in a given technology stack. Additionally, the cost of architecture and software license fees can differ from one technology stack to another.
Cost of Infrastructure
- The cost of hosting has been decreasing exponentially over the past few years with the number of available options such as Amazon AWS, Azure, Google Cloud, etc. These costs can play a significant role in selecting the right technology stack for your application.
Scale and Performance
- Some technology stacks are more comfortable to scale, and it’s essential to assess the scalability requirements to pick the right technology stack.
Scope and Requirements
- Every technology stack can serve a particular need and scope well, and it’s essential to assess the requirements to make the right decision.
- Do you just need a proof of concept to test out the user engagement?
- What part of the system needs more engineering attention?
- What third party and available libraries can be utilized to save costs?
- How would the overall code architecture of the system impact cost?
- These are all great questions to ask to pick the right technology stack for your application.
- What needs to get sacrificed to meet a strict deadline (Cost of Development, Quality of Development, Speed of Development)?
- What part of the system needs to be engineered right, and what part of the system can be re-visited later?
- Speed of development can be different in every technology stack, and this is one of the playing factors while deciding the right stack.
Contact us for any web/mobile buildout projects!
Technology Roundtable Transcript
How to Choose the Right Technology Stack for Your Project?
[00:00:09.470] – Ryan Williams
Hello everyone and welcome to the next tech roundtable, hear from Wonderment Apps, and we’re excited to have our awesome tech managers as a part of this conversation today. And we will be talking today about how to choose the right technology stack for your project and thinking about what kind of technology like the foundation you need to work on a project you might be building or planning on or if you’re working on. If you’re a tech person working with the team, how to how to think about most effectively recommending the right kind of technology stack for them to work with, depending on the nature of the project. One of the things that we find working on lots and lots of different projects is that there are different technologies that are best suited for different challenges and different ways of creating great products out there. So today we’re going to look at some of the areas in that and we’re going to talk to our team and get their feedback as they think about when they have to make these recommendations to clients or they have to make these recommendations on projects as to what the best technology is to use. What are some of the areas they’re considering? So, let’s do a very quick introduction to our team. For those of you who joined last time, you might remember them and for those of you that are new, that’s it. We’re glad to have you here. So, let’s go ahead and start with for us, our co-founder and CTO.
[00:01:45.340] – Faraz Tabibian
Hi, my name is Faraz Tabibian one of the co-founders and partners at Wonderment Apps. I have years of experience building and architecting technology solutions in many different verticals such as e-commerce, entertainment, and SaaS businesses. And I’m happy to be here today.
[00:02:04.890] – Ryan Williams
Awesome, thanks Faraz. and Meenakshi?
[00:02:11.910] – Meenakshi Rawat
Hi, everyone, my name is Meenakshi Rawat. I have been working with Wonderment Apps for almost five years and we have developed we have managed a number of small to large-scale applications in our company. We just would love to have new technologies every day. We just don’t know how to find new technology for any product.
[00:02:36.240] – Ryan Williams
Thank you, Tymofii.
[00:02:39.570] – Tymofii Nazar
Hi, my name is Tymoffi Nazar, and I’m leading two teams and in mobile development and web app-based development, so I’m happy to meet you today.
[00:02:51.540] – Ryan Williams
Thanks, Tymofii and Sergei.
[00:02:54.880] – Sergei Shvab
Hi, everyone, my name is Sergei Shvab. I am head of the QA, Quality Assurance department, and same as Meenakshi and I have been working with Wonderment Apps for more than five years already and I am managed and create here and I’m glad to present on this roundtable.
[00:03:12.000] – Ryan Williams
Awesome. Great, thank you. It’s great to have all of you and we’re excited to run through some of these questions with you and learn a little bit about how to pick the right technology stack for a project. So, I wanted to start today by thinking a little bit about the kind of higher-level aspects of looking at these questions, and we’ll dive deeper into some of the kind of core subject areas around it. But really at a high level. I want to talk a little bit about thinking about the cost of development and how to look at the infrastructure and really assessing things from a bird’s eye view. So Faraz, let’s start in this area and talk a little bit about how we kind of look at some of the aspects of the cost of development. Maybe we’ll start talking about, the average cost of talent and resources. Like what? Maybe that’s a good spot to start discussing.
[00:04:08.260] – Faraz Tabibian
Sure. Thank you. So, choosing the right technology stack for your project is a hard topic. If you ask me this question 10 years ago Ryan, it would have been so much easier to answer. But with the number of available technologies, cloud infrastructures that back-end technologies, Front-end technologies, it’s really difficult these days to actually get this right. So, there are many different factors that usually look at when choosing the right technology stack for a project that you’re trying to build. And one of the main factors that people always care about is costs, how much is it going to cost me to build this application. And in order to answer that question, we usually look at four or five different factors. The first one, as Ryan said, is the average cost of talents and resources. So, resource costs can be very different from one technology stack to another. A great example of this in Python. Like Python, developers are just massively more expensive than traditional .Net and Java resources. So really think about, you know, like what technology stack you’re going with and how much that technology stack is going to cost you on average when finding talents and resources.
[00:05:29.340] – Ryan Williams
Why? Why is there such a cost difference between developer types? Like what is the reason for that?
[00:05:37.860] – Faraz Tabibian
Yeah, it usually comes down to a learning curve, Ryan, so the learning curve for Python takes more hours for someone to get more comfortable in a platform like Python versus .Net and also frameworks like .Net or Java, you know, they come with more, there is more available ready to go components in those frameworks versus something like Python. So, it just takes a lot longer for someone in Python to get up to speed and become a senior developer versus something like .Net or Java.
[00:06:23.410] – Ryan Williams
Got it, thank you, but they really all have an underlying architecture, right? They look at that. They have to kind of have to consider some of the cost of the architecture. Correct?
[00:06:33.860] – Faraz Tabibian
Correct. So, yeah, like architecture is always one of the main factors, too. Like some technology stack are really hard to scale. And because they don’t really come up with the structure that you need, and you have to go reinvent the wheel in some of these technology stack. You know, for example, if you are trying to build a scalable application using NodeJS, it’s really difficult to scale NodeJS. And as a result of that the costs of architecture could be massively higher than some of the traditional frameworks. So definitely, you know, like I would look at the cost of architecture day one and making sure that I’m choosing the technology stack that doesn’t have exponential and massive architectural cost against it.
[00:07:31.690] – Ryan Williams
And some of those kinds of traditional technology stack. And I mean a variety. They have licensing fees associated to them as well. Right. So, it’s not as simple as just how much it costs to develop because not everything is open source. Right? So how do the licensing fees play into this?
[00:07:50.080] – Faraz Tabibian
Right. So, yeah, like some licenses can be really expensive, you know, like a great example of this is you’re trying to build a relational database and you’re like, OK, Microsoft SQL Server looks seems to be a great option. Right? And so many tools available on it. And you can easily host that on AWS RDS and your first month AWS Bill comes, and you’re caught off guard. So, it’s mainly because the licensing fee of Microsoft SQL Server is just so much higher than it than other relational databases. So, in those scenarios, I would definitely like comparing it to two other relational databases, systems such as PostgreSQL or other ones, and just make that comparison day one before you choose the right technology stack for your project.
[00:08:46.910] – Ryan Williams
Yeah, and you mentioned thinking about the hosting aspects of it as well. So, it’s not just about the licensing of the hosting, but like really thinking about the total cost of the hosting environment. Correct? What are some of those pieces that we’re thinking about in there?
[00:09:02.400] – Faraz Tabibian
Right. I mean, as you mentioned like cloud infrastructures and hosting environments today, there are so many options available. There is AWS, Microsoft Azure, Google Cloud, and many more. So, it’s really important to do that comparison before choosing the right infrastructure for your application. Like if you’re looking for storage systems, you know, you have videos or images or other content types, you know, like make that comparison and see what bandwidth you need, how much storage you need on how much it’s going to cost you, like on each of the cloud infrastructures and make the comparison really early on.
[00:09:43.270] – Ryan Williams
Yeah. And there are people who work with these host environments. There are some formulas they can use that give you a relative accurate projection of roughly what you think. But you also have to look at kind of the usage and the overall traffic on the website and things like that. Right?
[00:10:01.740] – Faraz Tabibian
Exactly. So, traffic and bandwidth and basically the volume of your storage, these are the three parameters that you have to plug into those formulas before you can get the cost out.
[00:10:16.500] – Ryan Williams
Awesome thanks, I want to talk about another one that we’re thinking about a little bit as well when we’re trying to pick the right technology stack for our project. Kind of in line with some of the Hosting, but a bit a little bit different, maybe more on the development side and thinking about if your technology and product can actually scale. So, we’re thinking about the scale and performance of the actual product and Meenakshi, maybe I’ll have you dig into this a little bit with me. So, tell us a little bit about how you think about scale and performance as we go and as we talk about the right technology stack?
[00:11:00.060] – Meenakshi Rawat
That’s a very good question and the most important thing that we should consider while designing or building a new application, so generally, when we start working on an application, it might not be that big, right? Someone is asking us to build an application. They have a few thoughts, but they are not very aware that exactly how much it might be small. But they have some bigger plans coming up in six months, upcoming in one year. So, these applications might grow to an extent that they will decide in architecture if it is not scalable. Right? If it is not such a big design or the infrastructure we have chosen, that it’s not easy either to scale it either horizontally scaling the kind of there’s a lot of features as added or the vertical scaling the number of users is increasing day by day of trying to get these the same application of different devices on a different side of things. So in that case, you have to be very much aware that what we are building, what it will look like in some of the coming months, and depending on that, we have to look at that kind of technology stack and the technology stack is not only hosting infrastructure, but all the kind of the language is kind of same looks like we are using. And one other example that we have been dealing with, we have been facing very formally, but the very dynamically changing in the world today. Something is required in the model, something as is required, very, very difficult to project something. And then it is changing overnight. Then how do we scale our applications for those requirements? How do we and similarly, the model decide to hold this application in new countries? And how do we measure the performance and how do we make sure that the performance will be the same?
[00:12:52.130] – Ryan Williams
So, what I hear is like not kind of thinking about this one specific moment that we’re building it, but really thinking about flexibility, where it where it’s the plan to go. And if you don’t think about that, you might miss things like expanding based on device expanding based on region traffic and audience growth. So, it seems to me like a phased approach kind of makes sense. Right. So, you’re thinking about an early-stage phase and maybe later. How do some of that play into it?
[00:13:24.760] – Meenakshi Rawat
Yes, yes. It’s very important that we connect with a client, connect the parts, what the projections are for this application, and once we have those funds, we invest in all those aspects that will come up with the right technology stack.
[00:13:39.540] – Ryan Williams
Awesome and what if when you start you have a different budget than you might? I mean, how do you look at how do you think about the amount of money you have right now versus later? And how do you suggest planning that?
[00:13:54.340] – Meenakshi Rawat
Yeah, yeah, yeah, so generally when we start, there’s a limited budget or when we’re developing, there’s a kind of budget which is allocated, but then once an application is built, it’s always generally the client says no, we don’t have that kind of budget, but we want to still feel a lot of features. So, depending on the final budget we have, we have to all kinds of resources we have depending on those resources and the kind of technology stack that we are using. So, we might think about the first step or these other things, these kinds of features of these kinds of scalability that will be required in the future. So, to that right technology stack, which will require less the development of effort this stuff in hosting it can be scale easily.
[00:14:41.870] – Ryan Williams
Great. Thank you. Appreciate it. One of the other areas I wanted to talk a little bit about is the process of thinking about these things before we go into a project. So, you know, when we start a project, we might know that the expectation based on marketing needs or based on sales teams, things like that, they may cause it to expand in the future. So really thinking through what the scope and requirements are in at the moment, but also thinking about what they might be in the future affects the moment, kind of like we’re talking about. So, Tymofii, maybe you could take this one. Like what? What do you think about like that, that around scope requirements and maybe thinking about how to start small versus jumping right into something big?
[00:15:32.840] – Tymofii Nazar
[00:16:54.740] – Ryan Williams
Right. And it makes sense. And it helps you also kind of pinpoint which part of the application or which part of the product actually needs the most engineering focus. Right. How do we consider that when we’re scoping?
[00:17:10.600] – Tymofii Nazar
Yeah, so let’s imagine a video service like YouTube, right there is a lot of different parts of logic there. You have a login screen; you have like categories and all of that stuff. But ultimately, the most complex thing behind the scenes is how the videos are being processed and then optimized for different audiences and then distributed. Right. So rather than finding a lot of time on this like things that these like relatively simple, we would plan most of the efforts to properly design and architect and to drive stack that will allow us to do this efficiently and cheap without reinventing the wheel. So maybe we can leverage something that’s already on the market.
[00:18:03.930] – Ryan Williams
Right, something that’s already on the market, thinking about some of those third-party tools. Correct. Like what? Actually, not built from scratch. That’s a part of that, right exactly, great. And how do you like how to do you start like how do you start and think about something that is potentially a really robust piece of technology? You start at the architectural level. Like what? What like how do you dive into something of the scale?
[00:18:35.750] – Tymofii Nazar
Well, of course, you can take a look at how the house is behind this technology, right? So, it’s a major factor. For instance, .Net and C# is supported by Microsoft, like Swift is supported by Apple. So, and they are not holders or owners of the plot of distribution platforms. So, it is definitely will be kept there for the time being.
So, they are analyzing who is behind the technology, how much easier they are on the market. Right. How many questions are posted to stack overflow related to that technology? That’s also a good indicator of whether the technology is alive, whether the community is alive and supportive, because it’s like at the end of the day, a lot of developers will go there and look for a solution so that they should be there in place.
[00:19:28.210] – Ryan Williams
Great. Yeah, another part of the overall development or creation process of a piece of technology comes after the actual building part of it and is actually doing the reviewing and looking at quality assurance processes and thinking about how we make sure what we built functions correctly. Sergei, maybe you could talk a little bit about when we’re trying to choose the right piece or the right technology to use for quality assurance testing and making sure it’s the right fit. Can you tell us a little bit about how we think about the cost of testing and how we can tell which tools are right?
[00:20:14.080] – Sergei Shvab
Yeah, right. Thanks for this question. Of course, this question is a really important part of the whole cost of any project. And have you ever wondered how much software this could cost for an average tech company? And I’ve already reviewed it long ago. And according to different open-source of the total annual spent on testing for in global and exceeds 300 billion dollars and using the software system, that takes up to 25 or up to 40 percent of the total budget for any I.T. project. And of course, when we are receiving requirements for any project, we should definitely think about this strategy. And based on the budget, which we have, for example, for this project, we should think about what types of testing, for example, we can implement for this project. We should discuss and think about the right balance, for example, between automation testing and manual testing. And, of course, a measure of the cost of testing for any project is really important before justifying any tests in any state.
[00:21:48.670] – Ryan Williams
I have a question for you. So, I know when we’re thinking about the right stack to use one of the things it’s like for quality assurance, which tools are most effective. So, we have somewhat are some examples of some manual testing tools that you guys might think about?
[00:22:06.770] – Sergei Shvab
Yeah, it completely depends on the exact project that we should use, for example, with tools, but of course, we should definitely think about test management tools, for example, be pretty open using testrail. Also, there are a lot of different analytics or face tools, but we should think about all advantages that they can give, for example, integration with Jira and some other tools. And for me, it is one of the best that we can use for any type of test and for the manual tool.
[00:22:44.600] – Ryan Williams
So, yes, it’s Testrail, is the one that I know we primarily use here on the automated side. There’s a lot of different scripting tools to be handled. What are some of the ones about it?
[00:22:57.980] – Sergei Shvab
[00:24:14.520] – Ryan Williams
OK, great, thank you. Yeah, I mean, Faraz coming back to you, I think we think a lot about the there’s a lot of pieces in this, right. So, there’s a lot of areas within the whole life of the project that you have to think about which tools and picking the right technology stack for product functionality, things like that. So, it really is kind of a big picture to think about. How do we also look at the big picture in terms of thinking about project timelines and actually getting somebody from beginning to end on a project?
[00:24:53.650] – Faraz Tabibian
Yeah, so, Ryan, like as we know, every tech project has a timeline and a deadline, and it usually comes down to three important factors. So, costs of development, quality of development, and the speed of developments, you’re always up against these three factors. So usually the question that we ask ourselves is what needs to get sacrificed in order to make its a deadline? So, and it’s not easy. It’s not easy to get it right. And usually, the way that we look at it is that, OK, so what part of this system needs to be engineered? Right. And what part of the system can be revisited later at a later time? So, for example, if you’re building a video streaming application, it makes more sense for you to maybe build the video streaming part of it right. and engineer that rights day one, and maybe revisit the rest of the application later. So, you make it to the deadline and then you can revisit the rest of the application. So really like thinking about what part of the application needs to be is going to be up against some traffic and you have some scale against that part of the application. So, you pay attention to those pieces first because, you know, you have to have the scale and you have traffic against those components. And the other pieces can be always revisited later. And you can always you know, there is always tech that there is always refactoring that needs to happen as part of any technology project. But making sure that you are sacrificing the right things when you are up against a deadline.
[00:26:45.710] – Ryan Williams
So, the actual deadline itself can influence like what technologies do you want to structure into this? Because I have an interesting question related to this. Do you find sometimes that you start like, let’s say, a startup, you start with one type of technology and you end up maybe hitting the end you chose that because you have some kind of a financial or some kind of a business deadline that you had to hit because you were trying to do it for speed. And then, later on, you realize, like, this thing isn’t going to scale. This doesn’t work. Do you have done we run into those kinds of problems?
[00:27:20.180] – Faraz Tabibian
Yes, all the time. And it’s as you said, it’s very common with startups that just because of cost on a deadline, they go with a technology stack that feels comfortable to them. They have available bandwidth; they have available resources. They pick a technology, they pick a technology stack because they have available bandwidth, they have available resources, or one piece of technology feels comfortable to them. And then later on a year, two years later, they’re like, oh, wow, like we are up against some serious traffic and continuing with this technology stack is going to be really difficult. So, it’s very common. And they pick one technology stack and then two years down the line, they have to switch over or switch off of it. And it happens with like big companies like Facebook and Microsoft and like even them like Facebook has been engineered their API layers, you know, like four or five times throughout the course of time because, you know, they keep receiving new requirements with traffic. So, it’s very common. And as I said, it comes down to the cost of development, quality of development, and speed of development. And looking at these three factors, you basically do your best to choose the best technology stack at the time. But five years later, there could be better technologies available. And this is just the game that we are in, in technology that was always better. Technology is available at a later time.
[00:29:33.960] – Ryan Williams
I have a related question and actually, it’s for maybe you and Meenakshi are the best to answer this. But what? And we kind of talked a little bit about this earlier when we were talking about the cost of resources. But there’s this other interesting factor in selecting a technology stack, which is how many available resources are there for that particular stack of technology. Right. Because you might find like if you take like the Microsoft stack, there’s a pretty robust set of developers that are out there. So, it gives you the ability to find more developers versus picking up a newer technology, which lets people know. And you might have somebody who has become an expert in it. How important is the availability of resources in choosing a technology stack? If you’re thinking about the big picture of it.
[00:30:29.570] – Faraz Tabibian
Yeah so, it’s like the rule of thumb is that you always go with what you know and that’s what I always recommend to all the companies that look like if one technology stack feels comfortable to you. Like, try to utilize that technology stack as much as possible because you have a lot of domain knowledge in your company in that technology stack. Your managers know. That’s exactly. Well, your resources know that technology stack. And if all of a sudden, you’re like a new piece of technology looks hot to you and you’re like, oh, no, I definitely want to use it. Like, just be aware that you’re going to pay a lot of big cost for just the main knowledge and the cost of functional management. So, like going with what you know and looking at what bandwidth you have available on the bench for the technology stack that you go with is definitely a huge, huge factor.
[00:31:32.970] – Ryan Williams
Yeah, and like the total available resources in your region for that technology, because there may be a limited amount of people who actually develop as well. So, if you have to change people out, it can be a problem
[00:31:48.300] – Faraz Tabibian
As you said, every region can be specialized in one technology stack and like working in this industry for a long time, you know, we kind of know the secret sauces and the formulas that look this region knows this piece of technology really well. And this region is good at mobile development versus this region is really good at automation QA, quality assurance. So, picking the right region for the right technology is also extremely important.
[00:32:18.550] – Ryan Williams
And tymofii I think you want to comment on this.
[00:32:22.960] – Tymofii Nazar
[00:33:22.130] – Ryan Williams
Thank you. Meenakshi I was wondering also about security and thinking about, like how we pick the right kind of security technology solutions, maybe you want to talk a little bit about that is about the right technology stack.
[00:33:39.380] – Meenakshi Rawat
So, as we all know our security privacy is very much needed across all the applications, it’s something an end-user is looking for whenever they are coming on an application because they want to make sure whatever they are doing is secure. The information they’re giving is describing cannot view. It’s not going into something wrong hands, wrong hands. So, it’s become very important for what is the application building and what kind of security we need. What other data we are getting from the user. What are the sensitive data that we are collecting? So, our capability is capable enough to get that data secure. So, depending on the next few, if it’s not only the technology stack, the way we are designing the architecture, it becomes very important what kind of architecture we are designing. Is that architecture possible in that the kind of next step we are expecting? So that makes one of the reasons the technology stack we are using is this are these security features we’re going to be able to achieve or not. And the second is the technology stack for the infrastructure becomes very important, at which level security will be declining. So, what are the infrastructure that we are designing? Our infrastructure will have that security are completely locked up, that no one is able to get our privacy or something.
[00:35:02.730] – Ryan Williams
So, when thinking about working with a product like a product manager or like an entrepreneur or somebody like that, making sure that you understand the level of security that’s going to happen and the end product or in the application supporting the right in those layers. And so, I know an application layer is really important. And also, how do you think about protecting the overall infrastructure and thinking about those kinds of security solutions. How do you think about protecting the overall infrastructure and kind of some of the security decisions in the technology stack there?
[00:35:47.020] – Meenakshi Rawat
OK, yeah, so there are a lot of aspects of security. One is the security obvious security guards use us. Then there’s a lack of security that we are storing the security. What is the data which we are exposing to the users is the right information? So, first of all. So, when it comes to what kind of application it is, if it is, they kind of get there we have some kind of e-commerce site where the user can purchase and is giving us a credit card information on design information. Security is the first thing that comes to mind. So, in those cases, we will show them what kind of authentication authorization techniques we are using, are we using some standard building services or are we designing our own services? Are they good enough to hold services while we are hosting our data and then hosting add up? They don’t want the cloud server. I’d be managing the user access is the permissions in the right way that they are not exposed to anyone and very much benefit of using across everywhere. You’re trying to do this and enabling are multiple-factor authentication that everyone who is accessing sensitive information as to establish some kind of authentication. And there comes a lot of aspects into that.
[00:37:07.350] – Tymofii Nazar
I want to add one more sentence regarding the integration. So, I think when you because the security question is so complex and different in different aspects, you might more and more companies starting to leverage tools like OCTA. The solutions allow you to quickly integrate into no matter what technology stack they have, plugins or SD case for different technology stack. So, but if you want to go with something cheaper, last may be popular. You want to ensure that this, like a security solution, has the right SD case for your technology stack. And it will also, like, affect the decisions.
[00:37:47.570] – Ryan Williams
Great. Thank you. Yeah, the last question on this particular subject, maybe Sergei do we also need to think about testing certain secondary aspects of the system, like security or elements that are not just in the product itself. Correct. These are other considerations for testing.
[00:38:10.070] – Sergei Shvab
Yes, definitely. Ryan, as I wanted to mention to you when we have prepared their strategy for any project, we should definitely think about different types of projects. It should be definitely including security testing. And there are a lot of different aspects which can be done from your perspective and from the automation side. And this is one of the most important features, not features, maybe a part of a testing strategy that should be definitely well thought before we will move to test of the already prepared projects.
[00:38:59.230] – Ryan Williams
Great, thank you. OK, so I really appreciate it. I think we’re going to kind of wrap things up here. I have one last question for each of you that we can go around and you can give your best answer. I know you don’t know what I’m going to ask but give your best answer. So, my question for you that you can share with our audience, can you think of one really important tip that they should keep in mind when selecting a technology stack? Just if you can think of one very important tip if you could recommend it. So, I’ll give you guys a second to think about that. And whoever would like to go first, they can raise. Just one tip.
[00:39:45.500] – Faraz Tabibian
Yeah, I can go first. So did the most important tip that I have for everyone is go with what you know, go with what you know best. And, you know, like there are always better technologies out there, like. Two years down the line, three years down the line, no matter what technology you choose, that technology stack could be obsolete. So, I always make my biggest recommendation to everyone is go with what you know versus what looks hot on the market.
[00:40:21.140] – Ryan Williams
Awesome. I love that.
[00:40:24.110] – Meenakshi Rawat
From my end, I’ll say always look at the big picture. Don’t just go with the written requirements. Ask hundreds of questions from the concerned people. Make sure that you have all the answers and then come up with the technology stack.
[00:40:41.230] – Ryan Williams
Great, I love it. It’s excellent. And tymofii
[00:40:46.110] – Tymofii Nazar
I got something like not to say, like if you don’t feel like, you know, any of the technology stack in the manager, ask somebody who was building at the solutions in the different technology stack that can compare and say something about the real-life experience, working in different options.
[00:41:01.900] – Ryan Williams
Great so getting feedback from people who are deep experts in the areas. Sergei did you want to add anything here.
[00:41:10.420] – Sergei Shvab
Yes, maybe I do have maybe one particular person, but I agree with all people who have previously mentioned this, that we should definitely come by in all aspects. For example, the budget, target audience for your future project, and many other aspects. Only after comparing all of them after a deep discussion of them, you can select a really appropriate test. It should be definitely well thought out before starting to implement it.
[00:41:52.160] – Ryan Williams
All right. Well, I want to thank everybody for joining us today and giving some really, really good thoughts and opinions on selecting a technology stack. It’s a huge decision for anyone who’s building the product. And this team has faced a lot of those decisions. So, they think about this question over and over again. We hope some of the tips in here are useful for you and help you think about it. You can always learn more or come ask us questions. You can visit our website www.wondermentapps.com you can find us at Wonderment Apps on LinkedIn. You can also find us Wonderment_apps on Instagram. So please feel free to come to ask questions, engage with us and we’d love to help you if anything comes up. So, thank you all for joining today and has a great roundtable. Thanks for the tech insights.