176 karma · joined May 1, 2013
Best advice I would give:
Implement features for paying or potential paying customers first. They already love the service and this will boost word of mouth reputation in a SaaS segment.
Full disclosure: I am the founder
At the company I work, we have an app for a customer where you can purchase things on their site. For a long while you could sign up in the app until one day where apple literally said (on a super minor bugfix upgrade): "If you are signing up users in your app, we are contributing to your revenue. We do not want to do that, unless you are using in app purchases".
This particular app could not use IAP for technical reasons, so we had to remove sign up from the app.
That is how the rule works
edit: Although, your point about the case by case basis could apply here, although this is not on a spotify scale, I assure you :)
Just wanted to tip you off to what I assume is a typo:
But lack of automated regression testing would have caught this issue.
I understand what you mean, but if you mean that literally then that is indeed a new and interesting paradigm in software testing :) - Activism? When faced with the backlash from "I have nothing to hide....you must have something to hide," most people don't know how to respond to this logical fallacy
I like the Snowden argument[0] about this one, and try to say it to people as often as possible. So I am going to repeat it here as well. Maybe then can we teach people who "don't know how to respond" how to respond:> Arguing that you don’t care about the right to privacy because you have nothing to hide is no different than saying you don’t care about free speech because you have nothing to say.
[0]: https://www.reddit.com/r/IAmA/comments/36ru89/just_days_left...
alias ffs=sudo
example usage:
$ grep 'something' some.conf
grep: some.conf: Permission denied
$ ffs !!
Password:`So to answers OPs question. Yes, I find the title strange (it is pretty controversial). But also, the title is descriptive and relevant (my opinion).
Full disclosure: I am huge fan of Knausgård :)
Your sign-up page[0] not only resembles the one of Basecamp[1], but you chose to actually copy (not like copy from it, but _copy_) the graphics from it? And the graphics features a dude wearing a Basecamp sweater?
I can see why you want to find design inspiration in Basecamp, but for me that stuff is just too close to the original ;)
As I said. Just a friendly pointer. You might want to change that. Other than that I wish you the best of luck, and this looks like a great start and an interesting idea!
"All we need to do is attach this usb stick and we can download all the files from their computer"
Well, almost, at least.
Sorry about that
Also, there are some other more style related rules that does not exist in jshint. Like requiring `typeof variable` over `typeof(variable)`.
Lastly, their webpage does a great job in explaining each rule, why they put it in there and what you can expect if you ignore them.
Just off the top of my head, that is.
(wonder if anyone from the HN crowd has ever heard of them).
Other than that, interesting project!
If I have a webpage that only does one thing, it executes
alert('Hello world');
Then the headless solution would have to be able to check that the alert fired. If your testing framework does not execute the JavaScript on the page (i.e just fetching the resources) then you are back to square one.
I have no idea if Mechanize executes page JavaScript, but SlimerJS (and PhantomJS) does. Which is the difference here.
* execute alert will probably for most use cases be bootstrapping some MVC and setting properties, doing navigation and so on.
./node_modules/istanbul/lib/cli.js cover -- ./node_modules/mocha/bin/_mocha -R spec
Always in my Makefile as make test-cov
Eh, update. After looking back in my terminal window when I wrote that sentence, it seems this is already done. All I can say is: :o
Advancing through versions from the early days back in 1.2 this has of course been one annoyance. Just want to say to the team: awesome job!
Thanks again
Thanks again for your awesome work, guys!
- I have started to always open source everything I do. It's the same as the gameification aspect, I just need to get another spot on that graph.
- I immidiately try to fix/report issues I encounter with other projects, even if they are minor (instead of just being a little annoyed about it). Also, opening issues counts towards the streak!
- I force myself to learn new things, all the time. Finished with a small project? Time to learn a new language and push the project to github.
So I'll recommend the "code every day" or "100 days of github" to anyone interested in learning new things or contributing more back to open source.
That website could have been stitched better together.
No offence intended (some pun intended).
I have used rethinkDB in production since may (and obviously in dev - about since v 1.1). It's kick ass. The things you immediately fall in love with is the awesome admin dashboard, data explorer, and of course the very beautiful query language.
Full disclosure: I am not employed by RethinkDB, I am just a fanboy and user :)
Thanks again Rethink!