11 ms·
I want to underline this bit: > they hired a team of developers without having a technical person on staff to vet them For any non-technical entrepreneurs rea
by wpietri 8y ago
I want to underline this bit:
> they hired a team of developers without having a technical person on staff to vet them
For any non-technical entrepreneurs reading this: please don't do this. If you aren't competent to hire developers, please borrow or rent a few trusted technical experts and use them as a hiring committee. Otherwise you are less likely to hire the best technologist, and more likely to get the most glib and appealing technologist.
Over the years I have met far too many smooth-talking consultants and would-be employees. And I've seen them cause enormous garbage fires when managers hire beyond their ability to evaluate. The size of these garbage fires are a direct result of what got them hired: if someone is good at telling managers what they want to hear, they can go a very long time saying, "Yup, we're building it and it will be great! Just you wait and see!"
And then, no matter who you hire, demand a "ship early and often" schedule. Ship to internal users. Ship to alpha users. Ship to external testers. Heck, ship to just person for just one narrow use case. The earlier you can start seeing real-world success or failure, the earlier you can course correct.
- brianpan 8y agoAnd how do you find the trusted technical experts? By using your trusted technical expert expert?
- hyperpape 8y agoBy not going in to a business that requires development unless you are one, or know one. I wouldn't assume I could start a restaurant or run a medical practice, why do so many people with no technical background assume that they can start a business centering around software?
- jasonlotito 8y agoBecause lots of people that haven't run a restaurant have successfully started a restaurant, and people who were in the restaurant business started a restaurant, but failed to keep it going. History is littered with people who ignored your rule here and have been successful. I guess we can flip that around: why do so many people with no business background assume that they can start a business?
- Memosyne 8y agoI believe you've made a false equivalence when comparing software development to the management of a restaurant. Most people have basic knowledge of food preparation and distribution. They do not, however, have an understanding of the software development cycle.
- Moru 8y agoThere are a big difference between having limited knowledge of food preparation and actually running a restaurant without giving your customers food poisoning. The comparison is sound. Maybe even perfect, proven by your comment. Know enough to be humble or enough to be dangerous? How long can I keep that rice pudding on the buffé table before I have to throw it away? How do you make sure the food is actually kept fresh in the cooler overnight? The inspection protocolls makes for interesting reading. Especially for new restaurants.
- Memosyne 8y agoPrior to the FSMA (Food Safety Modernization Act) [1] there used to be very little regulation in terms of food safety in the US. Since the comment was suggesting that throughout history people have successfully opened restaurants without any related experience, I find it relevant to note that selling food was not always so difficult: if someone had the wealth, they could hire some chefs and wait for customers. Nowadays, though, there are dozens of different dynamics involved in the management of restaurants. As such, it is very difficult for someone who has both a culinary and business background to open a successful food shop. To believe that someone who does not possess such an expertise could do well in this arena is foolish. Managing restaurants has always been difficult, but it is becoming harder with each passing year. Nobody in their right mind would recommend a complete amateur to open one of these shops given the current economy. They would need some sort of experience in the food industry before even attempting the feat. [1] - https://en.wikipedia.org/wiki/FDA_Food_Safety_Modernization_Act https://en.wikipedia.org/wiki/FDA_Food_Safety_Modernization_...
- stickfigure 8y agowhy do so many people with no business background assume that they can start a business? Because starting a business, in and of itself, is trivial. Children do it with lemonade stands. It's "the thing that the business does" that is hard.
- richardun 8y agoI get joke, but possibly to others wondering... Everyone knows someone more technical, they can keep asking. Also, a lot of entrepreneurs know other entrepreneurs that might help with this. Either way, they can find technical websites to help, founderdating.com, etc.
- Vinnl 8y agoI know people who are considered technical by shared non-technical friends - and I think they even are, to some extent. Still, some of those are still very inexperienced and I certainly wouldn't trust them to be able to properly vet new developers yet on their own. I think to some extent, it's a matter of being lucky picking the right person to vet, since you can't vet that person yourself.
- krab 8y agoIn my experience, it's quite common to have longer standing connections or friendships with people who won't be willing to join a particular startup but who might help with specific issues.
- crispyambulance 8y agoBy trial and error. Seriously.
- cecilpl2 8y agoTalk to the most technical person you know. Ask them for an intro to people they would most want to work with. Repeat this process several times until you have someone who will interview for you.
- unscaled 8y agoThis is not a chicken and egg problem. At least not for large organizations. If you read this line: The department that built the product had recently come into existence, and they hired a team of developers without having a technical person on staff to vet them. This is clearly a management failure. If you start a new department you should at least try to seed it with experienced employees from other parts of your company, even if they're on a loan.
- true_tuna 8y agoIt’s super easy to get experts to vet candidates. Then again it’s also super easy to take a used car to get it checked out, but nobody does that either.
- gshulegaard 8y ago> Then again it’s also super easy to take a used car to get it checked out, but nobody does that either. I did that...
- turtlecloud 8y agoWow. Awesome. Thanks for showing that you are smarter than the majority of people who don’t. Have some empathy for the normies out there.
- mmt 8y ago> Then again it’s also super easy to take a used car to get it checked out, but nobody does that either. Neither of these assertions is true. The second one is easily falsified (even not being pedantic about "nobody"), as evidenced by the existence of "used car inspection" on the price lists of at least some mechanics, if anecdata is not compelling [1]. The first assertion is, in its falsity, makes for an excellent analogy to the topic at hand, which is evaluating developers. Even a legitimately trustworthy, expert evaluator will not be albe to provide an evaluation that will reliably predict real-world performance over the next several years. This is true for interviewing candidates and for used cars. What one hopes for from the evaluation, is to significantly reduce risk by filtering out obvious (for ones definition) dealbreakers. [1] Personally, I only buy used cars (and typically 8+ years 75k+ miles). The logistics of getting them to my mechanic for an inspection is the least easy part of the process, when it's a non-dealer seller.
- user5994461 8y agoI am surprised. Is it hard to get a car inspected in the US? In France, every used car sale must be accompanied by a recent inspection certificate. Go to any inspection center and they will do it easily for a fixed fee. Note that inspection centers can only offer inspections, no repair of any sort, to avoid the obvious conflict of interest.
- gshulegaard 8y agoI couldn’t agree more. I just wanted to also add that this is something that you have to always keep in mind for every growing org, not just new ones. I’ve seen situations where Management has decided to pursue new product directions by hiring a whole new team, but without looping in their existing tech teams. It unfortunately had the same expected result.
- ChuckMcM 8y agoI was going to call out this quote : If you read this far hoping for an answer, then I’m sorry: I don’t have a simple one. This is a difficult problem to solve. And yet there is an answer, it is hire an experienced engineer. And the author glosses over the problem by not realizing they "solved" the problem by hiring him. It is the bad calculus where one "experienced" engineer is going to cost you maybe $150K - $200K and yet you could get anywhere from 3 to 10 junior engineers for that depending on how far out you go. It would be awesome of there were some sort of certification for "experience" sort of equivalent to the guild master status, it isn't an education thing it is a "oh yeah I've seen that before, lets not do that here's why" kind of thing.
- yen223 8y agoIf you aren't technical yourself, how do you separate an experienced engineer from one who, well, isn't? This was the fundamental problem that the company failed to solve, and frankly I don't think there's any easy solution around it.
- deleted 8y ago[deleted]
- memset 8y agoAgree with this. Same applies to any expert: how do you identify an experienced marketer? Or accountant?
- yen223 8y ago... or climate change scientist? Or economist? Or president? The problem of separating experts vs non-experts might be the single biggest problem society faces right now.
- gameswithgo 8y agoassuming you have a generally good education and brain to start with, a lot of hard work can usually accomplish it. Think Elon Musk learning about rockets, back before he lost his mind. I did it once for climate change, took a couple months, some math. Got there though.
- duxup 8y agoAs an inexperienced developer I'd just like to add that if you're going to have inexperienced developers.... JUST hiring an experienced developer is not an automatic solution. You need someone who can bring other developers along, teach with purpose, and etc. Experience developing alone does NOT automatically provide that. There are experienced developers who are ok, some are amazing, and some who for all their skills straight up can't lead / help other developers for any number of reasons. For those who can't / don't want to that doesn't make them bad or anything, just not suited for helping others.
- ntnn 8y ago> You need someone who can bring other developers along, teach with purpose, and etc. Experience developing alone does NOT automatically provide that. And the bloke needs time to train. If the developer is getting chased from dumpster to forest fire and back he won't be able to pass on knowledge and best practices.
- megaremote 8y ago> You need someone who can bring other developers along, teach with purpose, and etc. Experience developing alone does NOT automatically provide that. Not to solve this problem they don't.
- dlhavema 8y agoI'm a good example of that. I've been in software for about 12 years now and am only just getting started in the mentoring/training type roles. And that's only because I super had to... How do you deal with someone who gets to a problem and cant figure it out and then just drops it without telling anyone or saying anything, and you dont figure it out for days or weeks?
- itronitron 8y agoYou'll want to find out what they are stuck on and help or show them how to remove the initial impediment (they might be waiting on someone else or having trouble breaking down the problem into smaller workable chunks.)
- FollowSteph3 8y agoFrom a higher level maybe don’t start a software company. Just because I have an idea say on how to make a better oven I should not open one until I at least have some industry experience and knowledge first. In other words if your whole business model depends on a specific set of skills then you should at least have some knowledge or expert on your team as a starting point. If you start a plumbing business you don’t just open it up with zero plumbers on staff and no experience in plumbing. But for some reason this is fairly common in software...
- BurningFrog 8y agoYeah, there is some "law" here that I can't quite formulate about how developers can't recognize skills above their own level. This makes it impossible for someone with skill N to hire people with skill N+1, other than by dumb luck.
- mmt 8y ago> there is some "law" here that I can't quite formulate about how developers can't recognize skills above their own level. Perhaps you're trying to reformulate/restate the "Blub paradox" [1]? [1] http://www.paulgraham.com/avg.html http://www.paulgraham.com/avg.html
- Aeolun 8y agoI don’t know. Is that really a law? I feel like I’m relatively confidently able to pick out people above and below my level by now.
- jedharris 8y agoI think people can recognize those at level N+1, but not (reliably) level N+2 and beyond. In fact they are likely to think that people much above level N+1 are "crazy". Current political discourse contains lots of examples of people at level N+1 (or emulating that) convincing lots of people at level N that all the people at level N+k, k>1 are dumb, crazy or evil.
- BurningFrog 8y agoI like this quite a lot!
- YinglingLight 8y agoPolitical discourse has very little to do with IQ and very much to do with Persuasion and hallucination bubbles.
- jedharris 8y agoYes but... the level you are at is not just or mainly a function of IQ. I cannot evaluate the quality of a structural engineer who is much more skilled than me. Their cool new structural ideas could be brilliant or just terrible; I can't tell. A key issue here is how one responds to not knowing how good those ideas are. Dangerous responses: "I can't tell so they must be crazy" or "I can't tell so they must be brilliant." Accepting that one doesn't know mitigates the risk.
- JimDabell 8y agoI doubt that strategy would have been of interest to this organisation, due to this part: > they had never released a production application before. It's entirely understandable to end up with a poor-performing team if you start out without any in-house technical knowledge. But how did they end up with a team comprised entirely of people without any experience at all? That to me indicates that, rather than being unable to identify good candidates, they intentionally tried to cut corners. Telling an organisation like this how to identify better candidates isn't going to make a blind bit of difference because they aren't interested in better, they are interested in cheaper.
- rahimnathwani 8y ago"they aren't interested in better, they are interested in cheaper" Or maybe they suck at sourcing candidates, but don't know it. So they hired the top 1% of their candidate pool, without knowing what good looks like.
- JimDabell 8y agoEven people with zero technical knowledge aren't likely to hire a team of people with zero experience accidentally.
- remoteorbust 8y agoI once worked at a company with no product management experience. Because of this they hired a string of toxic Steve Jobs wannabees because they simply didn't know what they didn't know. They lacked experience in many areas. Ironically they ended up firing their only experienced executive (CTO). It's too bad, they had passionate engineers who could have built some amazing things (as evidenced imo by the amazing things they later built for Netflix/Google/Facebook/Amazon/etc) but they were stuck at a company that sort of wanted to be a tech company but didn't want any of those annoying "IT people" involved in decisions.
- jedharris 8y agoYour last phrase is key: They really didn't want the experts, they just wanted the results. No one can hire good people if they think they already know better. Good people got good by picking good learning situations, and avoiding tarpits.
- chris_wot 8y agoThe CEO of one of the companies I worked for hired without any consultation with technical folks. The company barely exists, and he is no longer the CEO.
- bryanrasmussen 8y agothe thing is you also need a technical person on staff who is good at vetting. I consult and am starting a new place in a week, I expect it will be fine, but the interview was a hr person and two techies, the hr person asked some questions and then asked if the techies had questions - no he seems fine. Which of course I am but still, having trusted techies is not the same as having trusted techies that are good at determining who not to trust.
- sureaboutthis 8y agoI once read, and have found to be true, that one can only train someone else to be 80%, or whatever, as good as you. If you let that person train someone else, then they will be worse than that.
- hutzlibu 8y agoTeaching someone to only 80% might be true on average, but the remaining parts they have to figure out on their own. But if you have 20 years experience you surely will never train a newbie to that level in a short time and expect him to train others to your level. For certain skills it works, but you just need experience and that happens over time and willingnes to learn.
- arikrak 8y agoI don't fully understand why there isn't a standard test or the like for vetting programmers. Most companies ask similar types of interview questions, so it seems one place could do it for a job seeker and give them a grade.
- ekovarski 8y agoIn short, don't let your ego overrule your logic. Too often I also see people who consciously or perhaps subconsciously prefer to hire folks who are either less knowledgeable than them or who agree with them on everything. It makes them feel more at ease but the project will suffer for it. I do like your idea of shipping early and often so you can see the progress and actual results. If I had a dollar for every "we completed 80%" but not being able to demo the product excuse, I'd be so rich that I'd be buying Jeff and Bill dinners. :)