jakejake

Providing an option to install with npm simply makes it more convenient for those devs who already use it - which surely is not an insignificant number. Nothing is requiring you to work that way or stopping you from downloading the files manually.

I just started to use npm (and indeed package managers in general) for my work recently and it's opened my eyes. It makes sense to me that this will be the preferred way of working for every dev/designer. Just as we mostly all use git now. It's hard to imagine that time when we just shared files via FTP and didnt use version control. I'd encourage anybody like me who was resistant, or working on a large code base that doesn't use those tools - give it a fair try on a side project.

You're right, typo in the title!

I personally find it odd to create every component as a jquery plugin. To me, it makes more sense to write a plugin only when you're extending jquery core functionality itself in some way.

As far as "extending" goes though, it's not always clear. Is a date picker extending jquery's core? I personally think not, but there has evolved an expectation that every web component must be initialized like so:

$('#container').doSomething();

So I suppose a lot of people do it that way just to have a familiar look to their API, or even just to show up in listing as a jquery plugin.

I agree about the quality of those few pitches I watched. But if you notice the red vs green monetary amount next to each video - all of them except one were rejected. So you can skip and watch only the green ones, I'd assume, to see the decent pitches.

I rather thought the videos were examples of what not to do, along with constructive criticism explaining why.

I think that most wars are are just based on the wealthy and powerful retaining or increasing their wealth and power. Average citizens generally don't have problems with each other. Excepting whatever propaganda we've been fed.

I found the videos really interesting to watch because we see lots of polished pitches here on HN, but here we're seeing everything. These are mostly just going to a VC with a hand out - asking for money. But, that's what pitching a company is. I think a lot of people who haven't done it imagine a slick deck presentation in a boardroom. The reality is that you have to be able to sit down in a coffee shop and sell your idea to someone who has more money than you.

As far as the terms - I didn't look it over closely to see if it's a fair or predatory deal. Anybody know if it's a fair deal?

The word "trained" does seem dubious as if the bees were taught to obey commands!

More likely the bees were "persuaded" to use cannabis by either proximity of the plants and/or treating the plants in some way to attract the bees.

Same here. Not having multiple projects open is a total deal breaker for us. We have a couple of shared libs that go with our projects and not being able to have them all open together is painful.

I can't seem to get into the game of fully automated deployments to production. It definitely interests me but a few things always hold me back.

The first issue is that I've probably set up 10 or 15 app development and deployment "systems" if you will. I've found that it's very beneficial to automate the simple stuff but it quickly reaches a point of diminishing returns. A super-custom system always works great for a while until some big change or library upgrade or refactor or whatever comes down the pipe. Then we spend a ton of time resetting up everything. We have to keep the build system components up to date so it doesn't turn into an ancient mystery box. Sometimes an upgrade breaks the whole thing and then we're on stack exchange all day debugging a parser library or some other thing that we don't care about. Basically spending hours and days and weeks on the build system so we can have that sweet one-click (or fully automated) deploy.

The other thing is that we release frequently but we tend to double check everything before it goes to production. Our staging server is auto-deployed except DB changes which we do manually. Right now it's about 2-3 clicks for us to deploy to production and it works fine. We still do DB changes manually though. It takes a minute or two to deploy. I feel like the process encourages that final check that everything is cool.

I guess I'm nervous to set up something that deploys to production simply by adding a tag to a slack message or the git commit message. Should I get over myself? If I change my thinking is it possible that deployment to prod could be a non-event?

That is true, and to make matters worse it's probably near impossible to figure the right amount out when you've just started the company. You don't always know how people will wind up using your app.

This is possibly the most interesting fumblebrag that I've read in a while. It has a few issues which have been hot on HN recently as well as some age-old problems.

The dependence on third-party services like maps, messaging, flight data, etc. is an interesting topic. Services that help you to get up and running in a couple of clicks are awesome at first. But they can become a burden when your usage goes up beyond a trivial amount. This is a great lesson about thinking ahead when choosing third-party providers - either by passing the expense along to your customers or having a roadmap to phase them out when you hit a certain volume.

Another point is the one-time pricing which, in my mind, is somewhat of a ponzi scheme for a business model. I always cringe a little when I see a cool new app with a "one time payment for life!" pricing. You just can't support customers forever with a single lifetime payment unless you are earning revenue in some other way (i.e. advertising). It's easy to think that you'll continue to gain more customers forever, but you're setting yourself up to be crushed by your own success. Unless you're planning on regularly releasing new apps and/or in-app purchases for your customers to purchase, it's not a long-term business model.

Sorry to see the Just Landed go - it looked like a cool app. I think there is a lot to learn from this post so thanks to the author for posting.

That's pretty much exactly what my perception is. Add to that, you're account gets shut down and/or frozen without warning and only a kafka-esque system to find out why you were shut down.

It makes sense that isn't true but I have to admit it is what comes to mind.

I's say it would be more like comparing a male who rapes a female with a male who watches that rape.

Regardless, though, the term "pedophile" by definition is someone who is sexually attracted to children. There is no distinction about whether or not they actually committed a sexual act with a child. A person who commits a sexual act with a child is by definition a pedophile and a rapist, since children cannot legally give sexual consent.

In other words... Art.