Loading...
Answers
MenuHow do I know if a developer is good?
I'm looking for a developer who can develop for mobile, iOS, I found some on odesk that look impressive and I would like to hire them. Still, I'm not a developer and I'm trying to avoid dealing with someone who isn't as good. Is there a test/s that's recommended I can ask from a developer to see how good they are, or any questions that might help me know if they're good?
Answers
You've received good advice. I'd just add one thing. We recently interviewed dozens of developers. After narrowing it down to a handful of individuals that had personalities and resumes we liked, we paid a developer friend of ours a few hundred bucks to interview the developers and thoroughly vet them from a technical standpoint. It was well worth the money to have someone more technically skilled than us contribute to our due diligence on the candidates.
Obviously checking their example work is important, but in addition I like to ask them how they built the app they're showing as an example. If they can answer confidently and clearly then they probably did build it.
Great developers are concise and logical. Bad developers are disorganized and illogical.
You can't really tell a good developer from Kait talking to them though. I would recommend breaking the project down into 5-10 "sprints" where they have something to show you at each step. Ask them to set the time frame for each sprint and if they meet each sprint deadline on time and have the majority of the work to show at each milestone point then you're good to go.
Test whatever you can each step of the way so that you can get what you need functionally.
For me a good developer is someone that will deliver a mobile app that achieves your goals. That means :
- he can help you to define/refine your goals with mookups, iterative and agile developments, you should take a little time to understand what your role as "product owner" is (http://www.romanpichler.com/blog/one-page-product-owner/)
- he will deliver the mobile app on the app store : he has already done that, he is aware of what is possible or not according to Apple's rules, ask him to show you working examples of available apps, did he deploy on all iOS versions or on iOS7 only, which model of iPhone/iPad does he have for his tests ....
- he can give you some advices if you need to deliver your app on another mobile platform (Android at least, WindowsPhone) because Apple does not catch all the market, if you really need a native app or if you can deal with a web app.
You can also book a pair programmer to review his code during the iterations, check the QA (quality assurance) and test the app as a user, have a look at www.airpair.com.
Don't hesitate to have a call with an expert on Clarity if you need help.
While definitions of 'good developer' do vary, the ultimate proof is delivery of "good software" (possibly within time or budget constraints). Figuring that out without working with someone is hard. Most technology companies put a lot of work into that and still make mistakes from time to time, hiring someone who ends up not living up to their recruiting evaluation.
Even if you could accurately measure 'good developer', someone who meets that definition might not be available, and deciding if anyone who is available is 'good enough' can also be tricky.
That said, I think the foundations of the solution have already been posted here, so I'll summarize some of that and add to it:
- Accept that it's hard, and that you may make mistakes.
- Use any connections you have to get someone technical involved with the selection if you can.
- For this kind of work, also make sure they can explain software development and its challenges to you clearly -- you're going to need someone who can do that with you about your software.
- Choose an iterative process for software delivery so that you can see the progress as it happens and evaluate success.
- Make sure that if you're not happy, you can move on. Be prepared to do so.
To know if a developer is good keep the following in mind:
1: Master the Phrasebook
The hard truth is if you are hiring someone to code for you, you should learn at least a little bit of code. That takes time, and some effort, but it’s worth it for a couple of reasons. The first is that you need to know what you’re talking about, at least at the surface level, because that’s going to inspire confidence and trust in your developer that they’re working for someone who knows what they’re doing; that they’re working for someone who values their contribution.
2: Check The Portfolio
It’s not your job to know everything, however. The best lens into a developer’s skills and experience is through a portfolio of their work. Whether it is just screenshots or whether they are able to bring in an application they worked on, actually being able to see examples of their work can give you a sense of what they’re capable of. But you cannot just look at webpage. You need to be strategic in how you are asking a potential developer to describe their experience, and drill down on their portfolios. Find out what their personal contributions were.
3: Ask for Recommendations — From the Candidate
The other way to get a thorough, but thoroughly non-technical, sense of a good developer is to ask for recommendations. Before you make a call or shoot off an email, ask the candidate what they think their references are going to say. Before you call and contact the references, ask the candidate what they think their references will say. This will tell you a lot. Again, pay attention to the language they use — whether they are hesitant or dismissive or eager to talk about their old team. Do not worry about the imagined imposition of reaching out to someone who is worked with a candidate. It is not one. Talking to someone on that person’s team can give you a whole other window into not only what that person’s skills are, but how effective they are in accomplishing projects and collaborating. Whatever you need a developer for, you are going to need them to keep you in the loop. So, just keep the “no jerks” rule in mind. No jerks. Do not do it. You want someone on your team to be on your team. There are a few additional ways to judge a developer. A trial period or beginning a working relationship with someone on a project basis, is almost never a bad idea. It gives you a chance to test their ability to contribute effectively to your team — and see the progress they make with their code — without the full commitment of a salary and benefits.
Besides if you do have any questions give me a call: https://clarity.fm/joy-brotonath
Related Questions
-
What would be a good approach for marketing a software development businesses?
For software development business LinkedIn ads, content marketing and Google Adwords don't work well. The best and most cost effective method is email outreach. Try to find the contacts of key decision makers in Bay Area from your target companies. You want to present yourselves as custom mobile and web development specialists and highlight your core competencies to get an initial call to discuss their mobile strategy or software development needs. Attaching your case studies how you helped other similar businesses and your portfolio can be extremely helpful as well. Try to always focus on the benefits in you pitch that they can get by working with you and point their missed opportunities of not having certain types of software or apps for their business. Clients love that software development companies have not only strong execution but also ideation skills. Hope this helps. If you have any questions I am also available on call for your convenience.AA
-
I have a great app idea, and I need help bringing it to life.
I'm not sure if this is how you imagine this world to work, but at least according to the order you wrote it "raising funds" was first. In reality it should actually be one of your final steps of the stage you are at right now. It may even come after a year or two! So you have this great app idea, and you're looking for a place to start... Don't! Don't start yet before you decide whether you have what it takes to get into a roller coaster that can ruin your life and make you miserable! Not trying to scare you but I think most people only hear about these great success stories. They have this dream of maybe, possibly, becoming the next big thing... Because they have the best idea for an app... You don't hear about the failures so often. And even if you do, you don't hear about what the founders of these failing startups had to go through. Truth is you are most likely gonna fail. And I'm saying that without even knowing what your idea is. There are so many barriers on your way that even a great product with a great team is likely to fail. Some people would say "I'm not afraid of failing", "It's good to fail cause you learn", "Failing will make me stronger for the next startup". That's somewhat true but it doesn't mean that failing is easy. As oppose to what people sometimes say - you do not want to fail! It's very painful!!! You have to understand what failing in a startup means. You can work your a$s for 2-3 years, have little to no salary, waste other people's money (most likely your friends and family first), lose friends, fight with your partners, your family, your spouse, devote 20 hours a day for your startup all this time, forget about the little and big things you used to enjoy in life, and only then, after debating 100 times whether you should quit or not, you finally decide that it's not gonna work and you've failed. Disappointing your family, your investors, yourself. Trust me it is painful. Are you sure you wanna do this to yourself? If yes, give me a call. I have the experience you need! From idea stage, to proof of concept, to running beta tests, getting millions of millions of users in ways you can't even imagine, creating features and experience that will make these millions of users completely addicted and viral, raise money in a smart way, hire the right people, find a great co-founder, succeed, fail, be persistent, and enjoy the ride! Good luck, RoyRM
-
How should the dynamic between a ux designer and a developer who are working together look like?
It depends a lot of in the skill sets and experience of both people but in most cases the ux designer should be controlling the developer pretty heavily in order to make sure his ideas come through properly. The UX designer may just need to work on his approach so people don't feel bossed around and more like they are working together. In an ideal world, there would be a project manager who makes sure everything is communicated well and keeps the dynamic feeling great.JM
-
Which is the best hosted free bug tracking tool for a team size of up to 10 members?
Being a freelance developer for the last 10 years or so, I have seen and used almost every project management software you can think of, open-source and closed, and I have found that the "best bug tracking tool" completely depends on your process. I employ and direct teams in an Agile process that involves loose story-based requirements with point-based estimates, two-week cycles of iterative development, planning and retrospective sessions, and look-ahead and show-and-tell meetings with the stakeholders. It's important to me, then, that my tools have a method of capturing all those pieces with as much detail as I need but no more. On projects, I've successfully used Pivotal Tracker, Unfuddle, Redmine, Codebase HQ, Basecamp, Trello, and many others. I usually recommend people to Trello for light, agile management; it's essentially a digitized version of sticky notes and swim lanes. If your team actually needs a full-featured ticketing system, see Redmine (Rails), Trac (Python), or Mantis (PHP), depending on your language preference. Hosting a version of these yourself is fairly trivial, and numerous options exist for cheap or free hosted versions. For something in the middle, Github Issues is a good fit and the open-source clone GitLab.org replicates most of those features nicely. However, if you're looking for a hosted version, you're probably looking to offload that tricky "backup" thingy, and in that case, how important is your data? How proprietary? What's your business model? If you're working on an open-source project, Github will give your team a free account with private repos, issues, wikis, and the like. If you're okay with your project being "readable by all", public projects on Pivotal are still free. I'm mostly a consultant these days, leading small groups of junior or intermediate developers into a more productive, more mature, fully operational teams of senior software developers. One of the first things I teach folks is how to use a project management system... and why! It'll save your bacon if it's simple, effective, and reliable. With a few minutes of discussion about your project, I can probably help you select the right tool and service for your team. Let me know if I can help with that. Best of luck!DR
-
What day and time is best to release an app for best exposure?
The best day to launch your app is either Wednesday night or Thursday, because the iOS App Store changes features every Thursday and you may get featured that day as "New games..." "New app..." etc. Ideally all your marketing/PR/advertising efforts should start that day (Thursday) because Apple likes it when an app is being privately promoted at the same time it's being featured. Yes AdMob could work for you but please know that there are many other ad placement companies similar to AdMob that can work for you too. You need to see what kind of clients they have, if they match with your niche, etc. Usually this is a trial and error process, you start with several ads and you see which works and which doesn't, you improve, you cut them. etc. Good luckEN
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.