4 ms·
You've got to know if the other person can code. Lots of people can talk a mean game and make nothing and few people can spot them. That's the thing, though. I
by renewiltord 7y ago
You've got to know if the other person can code. Lots of people can talk a mean game and make nothing and few people can spot them.
That's the thing, though. If you make a reputation as the kind of guy who can near 100% spot the good engineers, you will make boatloads of money. An employer will pay you more than $30k if you only do great hires. You do 10 of them with your conversation out to lunch and you've made $300k. That's the low-end.
But no one can do that and the few with high hit-rates act as executive-search agencies where they make a lot more.
But I think I would never interview anyone I've worked with. That just seems like a waste. I already either know that they can or can't do things.
- lumost 7y agoIt's worthwhile to interview the people you've worked with as they change over time, usually for the better with Junior Engineers becoming Senior or Principal Engineers, DBAs becoming engineers etc. But sometimes a long stint in management or getting stuck in KTLO hell for a few years can dull technical skills.
- renewiltord 7y agoThat's a fair point. Perhaps this is what people are talking about the conversations over lunch. I find it hard to believe that someone who wants to work as an IC and knows you would try to do that knowing their skills had dulled. The shame of failing someone who trusted you to deliver would be too much!
- redis_mlc 7y ago> DBAs becoming engineers Excuse me. Most of the top DBAs in Silicon Valley are former C programmers who probably are better programmers than you. I wish programmers would get over themselves. I've met CTOs who didn't know EXPLAIN. So who's the real engineer?
- google234123 7y agoWhat is EXPLAIN?
- rsynnott 7y agoSQL command to show how a database engine will execute a given query. I wouldn't necessarily expect a CTO to know about it, to be honest, unless their background was somewhat database-y.
- teddyh 7y agoIt’s not in standard SQL, but is present in most SQL implementations: https://www.postgresql.org/docs/current/sql-explain.html https://www.postgresql.org/docs/current/sql-explain.html https://www.sqlite.org/lang_explain.html https://www.sqlite.org/lang_explain.html https://mariadb.com/kb/en/explain/ https://mariadb.com/kb/en/explain/
- shagie 7y agoA tool for looking at how a query is run and where it may be slow. https://docs.oracle.com/cd/B19306_01/server.102/b14211/ex_plan.htm#i3305 https://docs.oracle.com/cd/B19306_01/server.102/b14211/ex_pl... https://dev.mysql.com/doc/refman/5.7/en/explain.html https://dev.mysql.com/doc/refman/5.7/en/explain.html https://www.postgresql.org/docs/current/sql-explain.html https://www.postgresql.org/docs/current/sql-explain.html https://docs.microsoft.com/en-us/sql/t-sql/queries/explain-transact-sql?view=azure-sqldw-latest https://docs.microsoft.com/en-us/sql/t-sql/queries/explain-t...
- dvt 7y ago> You've got to know if the other person can code. Lots of people can talk a mean game and make nothing and few people can spot them. If only this were true. I've co-authored a (technical) book, edited another, have dozens of OSS contributions, and GitHub projects with hundreds of stars. Everyone still tries to whiteboard interview me. Usually I tell them to screw off, but still. My theory is that (a) people are too lazy to come up with better hiring processes and (b) there's a prevalent "if it ain't broke" mentality so there's little motivation to do anything about it.
- jariel 7y agoNobody should be either afraid or unwilling to do 'whiteboarding', rather, it should be an opportunity. It's not perfect, but reasonably structured it's a good thing. Academic credentials are not necessarily conducive to great dev talent ... OSS with lots of stars is a much better measure, but even then, it's not a guarantee of anything. Companies have to be responsible about their due diligence.
- dvt 7y agoI personally suck at whiteboarding, even though I'd say I'm pretty good at actual coding. I'd rather not put myself at a disadvantage, so that's why I avoid whiteboarding interviews.
- yahyaheee 7y agoYea this is the thing, I’m terrible at white boarding but I have an amazing github that can show what I’ve done. An amazing github presence should far exceed any whiteboarding
- renewiltord 7y agoWe found a guy whose Github had solid Rust code and then he walked us through it and it was great how he could explain it. Maybe we were lucky there but he's turned out to also be generally awesome or perhaps that's a good sign. It certainly looks to me like you have the pedigree to be able to select which employers you'd like anyway, so the loss of the whiteboard thing is probably not a big deal to you.
- dheera 7y agoThat's true, but engineers don't code whiteboards or codepens. If they want to know if I can code, I'm happy to point them to several git repos that I wrote >95% of, and send code samples of non-public code that I wrote. I can make real tasks happen, like make a robot navigate a room autonomously, but I suck at remembering how to write quicksort or write a parser for some weird interview-specific language or all of the insane number of C++20 features. At most whiteboard interviews at large companies, I was asked to code things I have never done for work and will probably never do for work. Machine learning interviews frequently asked me to implement NMS or gradient descent. Fine, I can do that, and fumble a bit in the process (and probably get docked points for fumbling), but NO machine learning engineer on the planet needs to do these things because there are excellent libraries that do them for you and it isn't the job of the ML engineer to re-invent them.