Oompa

Why not just use GitHub? What format are your models in? GitHub supports STL viewing in browser. While STLs don't carry as much data as you may want, that may be a start.

That's fucking sick. Nice work man.

Woops! Small issue. Should be fixed now :)

It's more organic than you think. Employees want to see something, so they sell others on and work on it themselves if they can. If they can sell others to help, eventually it can ship. If not, then it atrophies and gets killed before it makes it out to the public.

How does it contradict revision control? You can make a change and add a commit message all in 1 fell swoop. Then the next time you `git pull` that commit will be pulled down, just like any other.

As others have said, it's amazingly useful for quick and small changes. I don't see how that means someone's IDE sucks. I work on many projects and don't have all of them open in my IDE with the latest code always on my machine. This totally beats opening that project, running a `git pull` (which may take a while on an active project which I haven't visited in a bit), making the change, then committing and pushing.

On top of this, it's useful for non-technical people using these tools. Not everyone can move around through multiple repositories and pull down updates as easily as you or I. However, now they can easily help keep documentation up to date without leaving their browser.

If you download the mark, it's a .zip including some smaller versions without suckers on the tentacle.

GitHub has always been capital G capital H. The logo just did not communicate it

It was a stock image that started on the 404 page. People loved it, so the octocat started showing up in more and more places and then grew to become the logo.

The error here is the blob is too big, so GitHub isn't serving it. If you try to view the raw blob, you'll hit the issue: https://raw.github.com/tibbon/my-3d-models/master/me-in-3d.s...

A better error message would go a long way here :)

I can't help but think of Kyle Neath's blog post about this in 2010: http://warpspire.com/posts/url-design/

I am so incredibly sad TinkerCAD is closing. It has been my introduction to CAD and it has been phenomenally useful. I'm trying out Autodesk Inventor Fusion, but it's so much more complex, so it'll take a while before I feel comfortable in that.

I added this to Homebrew years ago, for those OS X users.

Just because a bounty policy isn't disclosed doesn't mean it doesn't exist.

A raspberry pi wouldn't be a bad idea! We'd need to hook up some web cams though and print an enclosure for it :)

At this point, might as well use a competitor. Then you can have 2 different clients installed.

What's sad is that the Dropbox desktop client doesn't support multiple accounts easily, so then you might as well use a different service, so you can have 2 clients installed that sync automatically.

This is how Dropbox supports teams. It's absolutely awful, and I hope more people are made aware of it, because they really need to fix it.

What Octocat? Do you mean the Facebook, Twitter, and Microsoft logos? http://cl.ly/image/1R2h2B3Z2m3x/poop.jpg

I looked at Plunker, and then I got sperm on my screen.

I think Foursquare has been a Yelp competitor since they launched the Explore feature. I've been using it to find good stuff that my friends have been to. I'm likely to check out a place if a good friend of mine has been there several times than if a few strangers have given it 5/5 stars.

But GitHub's enterprise application is something enterprises can host themselves, inside their firewall. https://enterprise.github.com/

The overall comparison ends up being: Command-T is more of a pain to get setup, but is faster. CtrlP is easier to get setup, but is slower.

Link to the actual Github repo: https://github.com/michael/github

No one. That's how much faith I had in that test.

Then they need to be moved to a different place, at least. Tell your CI server to use them, but more them out of the way for normal developers.

Nope! You should be writing your tests along with your code. Not "keep it in mind" actually write them. My first step in a new project is `mkdir spec`.

I do strict TDD when I can, and I consider spiking out things part of the process. If I need to approach a problem that I don't know how I'd solve just yet, I create some sample code I later trash and do a lot of work in the Ruby console.

Then, once I've gotten an idea of the problem, I can start writing out some pending tests that help me figure out structure, and then I'll start into the strict TDD loop of write a bit of test, watch it fail, make it pass, write more test, etc.

I'm pretty far into the extremist side of TDD, and I'll say that there is a thing as TOO many tests. Your test suite needs to run fast to be really useful.

If you have thousands of full stack integration tests that takes an hour to run, you're not going to run them as often as you should be, if at all, ad might as well delete them.

Testing with front end javascript is more difficult due to different interpreters, much more variation in environment, etc. That doesn't mean you can't have tests for your core business logic at least in something like Vows or Mocha.

Then you didn't write good enough tests. I have deployed code that thousands of customers see without manually testing it. If my tests are green, I'm confident in deploying my code.