onebot

And here you are on HN. It is hard to buy this argument. Instead of reading HN for a week, hack out a little app and toss it up on GitHub. I am almost certain that is more valuable for you than opining here.

I do the same as well, I think it is a great approach. It is just a paring exercise, the language of their choice, their equipment, full internet access. We just build something like a calculator or pig latin translator. Something that you build up in layers. I usually read off the test cases one step at a time, in hopes that they write their own tests along the way.

But hiring good people is very time consuming. The reason GitHub as a portfolio makes sense, is that it helps compare potential candidates--that I know nothing about--faster. Biased or not, I have had the best experience with people that are very active publicly. From Battlebots competitors, book authors, to startup founders, etc.

Ivy League Colleges, VCs, even Y-Combinator works very much the same way--trying to make an assessment based on past accomplishments. The more visible, the better. With the caveat being a strong direct reference.

I am sure we all have extra circular activities besides coding, but depending on how strong your experience or professional network is, really depends on how much you need in a portfolio. I have been coding since I was nine and have decades of experience, I still have stuff I hack on that is public, from SlackBots that control GPIO pins to Sonos controllers, etc. I would think the more experience you have, the better chances you would have more stuff you can add to your GitHub (portfolio).

At the end of the day, as a someone hiring, I am going to gravitate to engineers that have more and better examples of their work ability and output vs where they worked on their Resume. Not to say that we should ignore anyone that doesn't have public projects--but they are certainly at a disadvantage against someone that has.

What should be the Dribbble equivalent for software engineers then? All I hear these days is, whiteboards for hiring is bad, asking to do a sample project for hiring is bad, now GitHub is bad. I don't know when software engineers became such "I don't want to show my work" industry.

Having a portfolio to show what your capable of is a great way to set yourself apart. I don't think anyone is expecting you to have developed Linux from scratch. But something is better than nothing. Which do you think is more likely to get an interview, someone with several source GitHub projects or someone that says "all my work was closed sourced" and has nothing to show.

Having founded three startups now (2x acquired), most of the best engineers I have ever worked with have a noticeably more active Github/Bitbucket/Gitlab portfolio than the average. In my experience, great engineers have public proof (open source, a self produced product, book, etc) of their craft vs nothing at all.

Now to be clear, just because someone has an active Github, or a book, or whatever doesn't mean you should hire on the spot. But should be someone you'd prioritize over someone that is seemingly too lazy to do any related extra circular activity.

Wasn't about the author--I totally agree with author. I was replying to the top commenter, who seemingly is a software engineer and disagrees with the author. I think if anyone has read the history of Carmack, Carmack would agree that productivity is all about incredible focus and his amount and quality of code he output would be his measure of success.

No offense, but compare your GitHub profile to someone who "grinds" like https://github.com/bketelsen. There is far too much confirmation bias in regards to work-life balance and ability to actually produce. As far as clichés go, I believe that "if you do what you love, then you don't work a day in your life" == productivity.

Don't you want people that care about your product instead of the technology behind it? I do. Because there may come a time when another technology is a better fit for your product and ultimately your customer's experiences. Then what? Now your not using elm and your team leaves or is disgruntled. I hire on passion for what we are trying to accomplish, not the technology stack.

People still use Rails?

I also believe it was the correct move. But not because he wrote it, but because what he actually said in it. He made many generalizations that contribute to gender inequality and never backed any of those statements up with any scientific data. Thus, it could be reasoned that he clearly displayed his own biases and showed that he is a contributor to gender inequality.

Furthermore, the PR backlash against his firing is far more news worthy if it was "wrongful" and he has gone on a media tour acting as the "victim". I am not sure news outlets would approach the firing objectively.

Are you guys hiring? ;)

Nonsense from a "Javascript" developer.

Sorry DigitalOcean. Unsubscribe.

This is not uncommon. The deal will have an escrow where money is held for a time period to protect against such claims.

Unbelievable. An experienced & successful entrepreneur would take on an unknown cofounder without any kind of vesting schedule + cliff. Doesn't make any sense to me. I am not buying Jeremy's side at all.

You shouldn't have thrown up in that Uber car. :p

This is the best resource on the subject, written by the designer of the protocol. The author is, surprisingly, a pretty good writer. This not only gives you everything you need to know (without grokking the spec), but also talks a lot about why they made the decisions they did.

Highly recommend... http://www.amazon.com/Bluetooth-Low-Energy-Developers-ebook/...

Sadly, just seems like the author was never really even punk rock to begin with.

Thanks for the candidness and honesty. It is really refreshing to hear the details--mistakes and all!

The whole "co-founder" is more of an egocentric term in this case. In the end, does it make your product better or worse if they are founders? It seems like a waste of focus to even worry about it. But if you must, I would consider the fact that being considered a co-founder might give them a lot more mental ownership and extra motivation when the times are tough.

FWIW - Glancing at your website, I am not immediately sure what it means to Push Objective-C to the cloud? More specifically, what is the pain point you are solving for me?

"GitHub hit one of the great gushers of the last decade (and let's face it, they mainly hit it for reasons that had little do with, um, their actions)"

Really? If they didn't do anything why would you even be paying them your $100 to begin with. They essentially built a social network around version control with an amazing user experience. Do you remember Sourceforge? Which would you rather use?

It isn't fair to discount the value of GitHub or the effort they put into building a great product just because it costs more than you want to pay.

Did anyone else feel like they were being trolled by some kind of Steve Jobs joke during the video or lifestream?

This is awesome, thanks. I would love to see an equivalent using C so that one could learn to make a more portable OS for other ARM chips.