Kaggle is best known as a platform for machine learning competitions. We have a community of over 650K data scientists. Now also building a sharing-and-collaboration platform (closest analogy is Github for data science: https://www.kaggle.com/kernels)
Particularly interesting opportunity for software engineers looking for exposure to data science/machine learning. Three of our engineers have come via HN posts, so we take HN referrals very seriously.
I'm interested because it seems that lower-level systems programming at Microsoft put braces at the end (early .NET BCL, maybe even the first C# compiler's C++ code, TypeScript compiler source, etc), but that Microsoft documentation tended to put braces on their own line and then that became the more de-facto style that shows up in their open source code.
Do you remember any details from Cutler Normal Form? I'd love to learn more about this.
From a quick search I see that it uses braces at the end. I'd be curious if CNF encouraged subsystem prefixes (e.g. the "Ke" in "KeBugCheck").
I wonder if CNF had any influence on "Systems Hungarian" (e.g. "dwCreationFlags") that dominates the Win32 API or if that came as an accidental offshoot of Simonyi's "Application Hungarian"
Dave Cutler is a legend, but he keeps a relatively low profile, so it was nice to watch the rare new video interview with him at the bottom. I especially liked what he said at the end:
"I have this little saying that the successful people in the world are the people that do the things that the unsuccessful ones won't. So I've always been this person that, you know.. I will build the system, I will fix the bugs, I will fix other people's bugs, I will fix build breaks. It's all part of getting the job done."
When I was a kid, I enjoyed reading "Show Stopper! The Breakneck Race to Create Windows NT and the Next Generation at Microsoft" that chronicled his move from DEC to build NT. Jeff Atwood has a quick review of it at http://blog.codinghorror.com/showstopper/
It's nice to see Microsoft supporting this now that they've committed to Git in TFS/VSO. It's also good to have the latest version of Git.
Git on Windows has been stuck at 1.9.* for awhile and always in "preview" because it was never really meant for production usage since the main contributor wasn't able to spend much time on it (and even then, he didn't primarily use Windows): http://episodes.gitminutes.com/2014/04/gitminutes-28-johanne...
I applaud the work that Johannes Schindelin (and others) did to get Git on Windows for these past years of increasing usage and look forward to this project taking it to the next level.
It's nice to hear of other people with a similar stack on HN (Azure, PowerShell, TeamCity, HipChat, and presumably C#/.NET)! It's working well for us too.
In addition, we're increasingly doing more with ChatOps with mmbot (as an Azure Web Job): https://github.com/mmbot/mmbot
One nice thing about mmbot is that if you use the DLL mode instead of the CSX mode, you get a great IDE debugging experience which makes it even faster to create meaningful ChatOps extensions. I've found it to be a more pleasant development experience that Hubot with CoffeeScript.
The best way to learn is to try to apply techniques on problems that are interesting to you.
Random Forest is a very powerful technique these days that's usually pretty good as a first-pass. Using it with permutation importance usually helps you identify important variables.
When I saw Jerad's post on Hacker News, he looked like a good fit for a developer role at Kaggle. Our team interviewed him remotely and I met him in person and verified that he has the talent, curiosity, and life-long interest in software development that'll make him a great addition. We're really excited to bring him aboard.
Thanks HN for helping us make a rare find!
P.S. If you're into machine learning and/or have an interest in developing a great site for a community (like Jerad), we're always looking for more to join us: http://www.kaggle.com/careers
Yeah, a simple check to see what nameservers the domain is currently using and then warning about the possible downtime and offering to switch ahead of the transfer would have been a huge win.
Agreed, it was a dumb mistake. I just wanted to let others know so they don't have to suffer the consequences as well of multiple hours of downtime waiting for things to finalize before you can change it.