Killswitch

Problem with them open sourcing their platform is that the platform base is used in enterprise and how the bulk of their revenue is made... Who wants to buy milk when the cow is being given away?

Bower doesn't do anything npm doesn't already do, except horrible version management.

    bower install lodash => bower_components/lodash/dist/lodash.min.js

     npm install lodash => node_modules/lodash/dist/lodash.min.js

Only difference there is you use `node_modules` instead of `bower_components` for root directory.

The article states that it will soon be able to come pick you up from long distances and even stop and charge itself. I'm pretty sure you wouldn't have to do that stuff.

To be completely honest with you, Heroku isn't your problem, yeah SSL is pretty high, but that's okay... The fonts is your killer.

Nice write up, Justin! I was one of the first engineers at a competitor of TeeSpring's, and we tackled the same problems. We used Fabric.js in our second iteration (first was jQuery).

I really dig the idea behind the site. I am not a UX developer, but I am improving and the service would be invaluable. What can we do to help get the iteration back in place?

I assume the reason for not going with DO, Linode or AWS was you're not a devOps guy, which is understandable. We can help you with that.

Also skin it to look like an editor, and then have the user go full screen, because who codes in a browser window?

Great response. Too many people criticize someone's work comparing it to similar stuff that's been around since just before the dinosaurs went extinct with responses like "what makes yours better?"

It doesn't. It's just something you made. Use it or not. Nobody cares.

So what you're saying is if I don't go to the doctor for 10 years, but pay $350/mo over the course of that 10 years for an insurance plan, the insurance company uses the money to fund college education for nurses and doctors?

Doubt it.

Dokku is great if you want to host all apps on a single server. I had used it for a while.

Switched to using github to push to, which fires off a build on a ci server, which fires off a push to docker registry and my server pulls that and rolls the versions.

This setup allows me to have everything on a single server until an app starts needing it's own, then I deploy a new CoreOS server and transfer the fire system to that one.

I'm 30 years old and haven't been to a doctor in about 10 years outside of simple things that I paid out of my own pocket. Nothing that a year of healthcare would cover, and considerably lower than it'd cost.

I'd have paid in tens of thousands of dollars over the course of that time, and for what? What ifs?

> Once I fire off a contract, I’ll post a comment on our internal hiring P2 to give HR a heads up that a trial contract will be incoming shortly.

> NOTE: P2 is a WordPress theme that makes threaded discussions incredibly simple. We use P2 for a large portion of our internal communication.

> I’ll then create a new private WordPress.com blog and invite the applicant to be an editor. This is where I’ll post the project brief. This is also where I’ll move the conversation for the remainder of the trial.

I understand WordPress is their business, but I feel that using WordPress for internal chat and interview board is kind of weird.

While I can understand the want for that, there's too much issues. The only reason npm does it this way is because the module that depends on B v1.3 and a module that depends on B v2.1 could be introducing some really bad bugs or breakage if you force all modules to use B v2.1.

That's one of the reason bower is losing out.

If depend on A and B and both A and B depend on the same version range as C, C is now a top-level dependency.

Your node_modules will look like this:

    - Package_A
    - Package_B
    - Package_C

It's only when A and B depend on different versions of C that cannot be resolved via semver as safe.

    - Package_A
    -- node_modules
    --- Package_C
    - Package_B
    -- node_modules
    --- Package_C

I am pretty certain that monkey patching your dependencies is frowned upon in the Node world. It's best to fork the repo make your changes, and then depend on that.