Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Leaderboard


Popular Content

Showing content with the highest reputation since 06/07/2020 in all areas

  1. 1 point
    Magento is one of the most popular e-commerce platforms that are out there, famed for providing no limits when it comes to customizing your online store. Whether you’ve decided to build your store from scratch, wish to optimize or migrate the one that you have, you won’t make it without some professional help of specialists. In this article, we give you tips on how to hire expert Magento developers and which questions to ask them. Tips on Hiring Magento Developers Before stepping to the questions, it’ll be helpful to know a couple of things about the process. There are many specialists all around the globe, and you need to know who you’re looking for as the developer services can differ based on what you need: migrating the store, building it, optimizing it, etc. Having a clear vision of what you need specifically makes up almost half of the deal. Make emphasis on experience with similar projects to the one that you’re planning, this can eliminate some unneeded questions or blind spots. Keep in mind the time-lag if you’re hiring someone on the other side of the world. Which Questions to Ask a Magento Developer Now that we’ve given some general recommendations of where to look for Magento developers and what to keep in mind as you’re searching, let’s move on to the actual questions you can ask and why you should do so. 1. How many years of working with Magento do you have? Speaking about Magento development, the experience of actual work on the platform is the key factor to pay attention to. Because Magento isn’t easy to get in the hang of, it can be challenging to understand and master even to those who have many years of general development behind their shoulders or to those who are good at PHP. The more years of hands-on work that the developer (or team) has with Magento the better. The reasons for that include the quality of code that is produced as well as the wider range of tasks and issues that could be taken care of. Importantly, make sure those who you’re considering to hire have plenty of experience with the Magento 2 platform, as Magento 1 (the previous version) differs from it big time. That said, you’d surely want your developer to know how to sidestep a problem, avoiding it before it even arises, as well as to have the necessary knowledge to fix things quickly and efficiently in case something goes wrong. 2. Are you Magento certified? To be fair, having Magento certification is not an obligatory requirement. Yes, on the whole, certification is a big plus since it somewhat proves that the candidate has the needed knowledge, and that he/she took the time to confirm having it. Nevertheless, although there are many types of Magento certificates out there, some of the questions that the tests include to get the certificate are outdated and don’t cover the recent turns such as PWAs (Progressive web applications). So, if the person in front of you is officially Magento certified, that’s wonderful. If not, that shouldn’t become a ground-breaking reason not to consider them for the job, especially if they could boast having plenty of Magento 2 experience under their belt. 3. How well do you know Magento 2 architecture? As mentioned earlier, Magento isn’t a piece of cake. This question is especially relevant if you don’t understand which Magento (1 or 2) the person who’s before you has worked with. Magento 1is becoming outdated, and everyone is either making the move to Magento 2 or building ground-up on it. Consequently, it is vital to dot the “I’s” regarding where the candidate stands in terms of Magento 2 architecture knowledge. Like already stated, Magento 2 architecture is radically different from Magento 1. It’s quite hard and time-consuming to figure it out too if you’re just getting acquainted with it (roughly, you need about a year to hold up well). This is why you should definitely be on the lookout regarding this. 4. Have you ever migrated a Magento 1 store to Magento 2? As you’ve probably guessed by now, moving a store that was created on Magento 1 to Magento 2 is a very complicated problem to solve. The thing is that in order to cope with the task successfully and within adequate time frames, the developer (or team of developers) should be equally witty in both of the platforms. They need to know M1 and M2 like the back of their hands, keeping in mind all the features and elements that the two differ in. They have to be able to carry out loss-free data moves, come up with custom solutions, deal with the compatibility of modules, among other things. Thus, if the candidate has migrated Magento previously, that could be a good sign. You may ask about what was challenging, how long the process took, and look at the website. 5. Which progressive JavaScript frameworks do you know? What’s for progressive JavaScript frameworks, knowing React.js or Vue.js, for example, is noteworthy. Having such skills, developers are able to make UI components that’ll be reusable for sites and applications. 6. Do you have experience with Magento’s PWA Studio? Progressive web applications are a highly popular and promising trend in e-commerce. Because the solution offers an affordable replacement for native apps and allows your website to work like an app (even offline), at the same time being fast, responsive, and accessible by search engines, it’s a solution that many store owners want to get ahold of. Ask your developer whether they’ve built PWAs and their thoughts on the subject. 7. Which of your former Magento projects was the toughest/are you most proud of? Browsing real examples of work is yet another great option. CVs and portfolios might be packed with information, so fishing out some specific highlights can do you good. You can ask which aims were set, how were they handled. Pay additional attention to the points that are connected with custom solutions and configuration. On another note, make certain that the portfolio in front of you actually reflects the work of the specific candidate and that it’s authentic, you don’t want to waste your time on something that’s claimed to be theirs but really isn’t. You can attempt in contacting the company and ask them a few questions. 8. If you were to give advice on Magento optimization what would it be? Let’s face it, if you’re running a business in the sphere of e-commerce, you want your online store to be performing at its best. Time is moving forward, technology is evolving, new trends are established. This means that you’ll need optimization so that your store is viable, fast, findable via search engines, provides a great user experience, etc. Some replies that can count here would surely include recommendations on optimizing website speed, improving the product search, and reworking the checkout. At times just several touch-ups can already make a change for the better. 9. Do you provide support after the site’s release? Knowing that your developers will have your back after the release also helps. After all, if there will be a situation when you’ll need urgent assistance, having a service level agreement with your developers wouldn’t hurt. For this reason, settling from the very start the “what happens after the release” matter is in your interests. 10. Do you mind preparing a test assignment? It is considered good practice to offer a test task to the specialist who you’re planning to hire. After all, it’s your chance to see the person in action. One of the ways to do that is to request to solve an actual issue that you have or to turn to specialized platforms that were created for test assignment purposes, for example, Devskiller. All in all, approaching the matter of hiring a Magento specialist for your project is very important. Ultimately, these people will be entrusted to deliver a product that’ll influence your business. We hope that this guide will help you when searching for your perfect match!
  2. 1 point
  3. 1 point
    Yes Jimi, Sandbox is yet to be rolled out. I am waiting to try it out as I am not sure how Atlassian will handle 3rd party Apps in that instance.
  4. 1 point
    The requests to get Portfolio for Jira for Cloud users have been loud and finally Atlassian released a Cloud version. They also made a very odd choice to rename Portfolio for Jira to Advanced Roadmaps and place it behind the Cloud Premium barrier. Portfolio for Jira has long been the better choice for Jira Server and Jira DC users. The features have been perfectly suited for managers to keep an overview over large programs and initiatives with relative ease. As such it has been the envy of Cloud users for years and it comes as no surprise that Atlassian would port this to Cloud given their focus on the cloud platform lately. Renaming Portfolio for Jira is also no surprise as it confuse managers with two portfolio products where the high level Portfolio tool Jira Align is the product Atlassian seem to want to focus on. Renaming it to Advanced Roadmaps is however a very strange choice as it is not a simple roadmap tool. It also make the naming confusion shift from Portfolio to Roadmaps as Cloud users have been using the limited Roadmaps feature for quite some time. The new Advanced Roadmaps is only available for Cloud Premium users. This makes sense as Atlassian want to push users into their new price model. Currently there is not much that would warrant double the price for Cloud Premium so Atlassian need something that is enticing enough for users to make the shift. Advanced Roadmaps could be one of those features, but they need more as Advanced Roadmaps cost $2.3/user and month at it's lowest level and Cloud Premium cost an additional $7/user and month. Feature wise Advanced Roadmaps is still great with the two main selling points of great overview and the ability to scale the issues with more levels. Here are some of the selling points from Atlassian: With the changes coming to Roadmaps where all projects will get them, and not just Next-Gen projects, combined with the promise that Advanced Roadmaps will somehow be connected to a more comprehensive whole this could be a pretty good thing for Cloud Premium users. Adding Advanced Roadmaps to Cloud Premium will now add the ability to scale issue types beyond the standard 3 levels, which is something people have asked for for a very long time. Will it be enough to warrant the high price tag for Cloud Premium? I doubt that as Advanced Roadmaps is only really useful when you pass a certain number of teams. Doubling the price tag will probably discourage most low to mid-range clients. The fact that you can only have a 7 day test version and that you need to setup a new cloud instance to even test this if you are on a regular cloud plan is also a problem. With more features added into Cloud Premium however I think more and more will make the shift over to that. Overall this is a good new addition and package it with the Cloud Premium offer will make it more accessible and therefore used, which is a good thing. It's a bit sad to see Atlassian being so aggressive in their way of forcing cloud users into their Premium tier that is making some old customers a bit annoyed, but I think it will be good in the long run.
  5. 1 point
    Hi Jimi we have just released a new functionality with fast filters. I know this is one of the things you missed. Another one is coming!
  6. 1 point
    Cloud premium also includes codeless automation! Also only premium cloud offers 99.9% availability, 24/7 priority support queue. These are some selling points I guess.
×
×
  • Create New...