105 karma · joined July 27, 2010
These are all great points, especially regarding the signup process and and permissions. I think you have validated some of the concerns that I have had regarding these issues.
I do have delete and rename, but maybe I should pop up a quick intro screen for first-time users to get acquainted with the functionality.
Thanks again and all the best to you.
I hope you don't mind temporarily shelling out $6, but I would really appreciate it if you could sign up for the service and answer a few questions:
- Is it clear how to sign up for the service on the home page?
- Does the signup/payment workflow feel straightforward?
- Is it clear how to get a refund? Is the process straightforward?
- Does the app feel fast or slow?
Thanks! Very very much appreciated. The site is https://www.textdropapp.com
Node Streams really help performance in my application where I am proxying API calls from the browser to the Dropbox API. It's much faster to stream the response from Dropbox through to the client rather than request, wait for entire response, then send.
Also it's a much better way of organizing your DOM structure than a bunch of loose jQuery calls.
1. backlog.txt - a list of all potential ideas and tasks
2. changelog.txt - a list of iterations/versions/milestones
Whenever I have an idea or bug, I add it as a line in backlog.txt When I want to actually work on code, I pick 3-4 tasks that I want to complete and move them to changelog.txt. The number of tasks depends on how much I can do in one or two sittings.
backlog.txt is in a format like this:
* Fix IE9 compatibility
* Refactor CSS
* ... etc
changelog.txt looks like this:
1.1.0 - next release
--------------------
* Fixed IE8 thingy
* SSL encryption enabled
1.0.9 - March 10, 2012
--------------------
* Fixed null-pointer crash
* Catch exception in sendmail.java
* Enabled websockets transport
Keeping everything in plain text helps me from fiddling around too much with the tool, which I am very prone to do. (Meta-bonus, my product is a text editor so I can organize my product with itself.)
http://dl.dropbox.com/u/222781/HTTP%20Status%20Code%20Defini...
e^iπ + 1 = 0
Update: according to 11 USC Section 507, wages fall in 3rd place. I am not a lawyer so I may be reading this all wrong, but it goes "administrative expenses", "unsecured claims", then wages up to $4000 (about half of what I'm owed) and earned within 90 days of the bankruptcy filing. It's been about a year since I quit the company, and the wage claim through the labor board has a 3-year statute of limitations. I wonder what would happen if I filed a wage claim on a bankrupt company...
1. Character - how do I carry myself with justice, mercy, and compassion, yet not get pushed around and maintain self-respect? 2. Social - how do I maintain relationships? 3. Financial - how do I get my money?
You are right, I did assume risk in joining the startup. That was not apparent to me at the time because it was not really communicated, but now I know. Looking back, I see a lot of "I should have known" moments. The lesson is that one should not look to the leaders of the company to look out for their interest.
What do you mean when you say you have diversified?
Our CEO would come into our office and say, "I just had a meeting with a potential investor and he's committed $25k!" He always had our hopes up, but our CFO would paint a different picture. Even our president told me he was starting to pick up work on the side.
I think it would be a weak move to avoid it completely, but maybe not weak to at least confront them and then show mercy.
But I think you're absolutely right, nobody here can really decide for me.
What you described about kicking off the bankruptcy process is pretty much how I pictured it. They have implicitly made me an interest-free lender.
One of the hard lessons of life here for me is that I am really hesitant to trust any people in business now. I now understand why unions exist.
While I was still getting paid, I didn't want to quit until I had secured a new job. When they were 1 month late with pay, that pretty much drew the line for me so I gave them 1 month notice at that point.
And yes, now I'm regularly updating my resume and keeping my eyes and ears open for other opportunities.
But I guess my gut reaction — which you can take with many grains of salt because I don't do any work in a collaborative music composition situation — is that of "Geez...it's hard enough to get technical people to jump into my version control workflow, how could I get musicians in on this?" (Which I think you already addressed in another comment that your target audience is maybe the overlap of developers/composers.)
I'm reading through your Introducing SolidComposer page and I think it would be helpful if you could condense that down and put it somewhere more accessible (maybe on the front page). I find myself not really wanting to spend time figuring out how the app will help me.
Also, the How Does It Work? section actually does not seem appealing. The first situation seems simple and straightforward, whereas when you talk about SolidComposer complaining about missing dependencies, that starts makes me feel uncomfortable.
Anyways, I hope this is helpful and good luck with the project.
Side note: I recently started playing in a band and one thing I notice is that whenever we get together to practice a particular song, we are always reinventing the song and it never really seems to gel. It's always "How does that part go again? How many measures were we supposed to play that riff?" Could SolidComposer help in that situation?