Next time you gear up for a major upgrade, try less time blogging for HN, more time talking to your users about the features they care about.
The all-new Basecamp is live
81–90 of 156 posts
Re: The all-new Basecamp is live
#82I'm surprised to see people complain about the copy. Is "The majority of our design and development efforts moving forward will be focused on the all new Basecamp, but we'll continue to support Classic" really that hard to understand, let alone disingenuous? Is it, despite it being mentioned a zillion times in the FAQ, so tough to understand that they've cut some features and that therefore the upgrade won't make sense for everyone?
Re: The all-new Basecamp is live
#83I'm a bit behind the curve here - but now that I'm caught up, I'm concerned. When I saw the title of this article, I immediately logged into my Basecamp. Hmm, it looked the same. So I went and found their upgrade instructions. Then I learned that it's not a straight 1:1 upgrade, it's a different product. And they've dropped support for some quite important features, like, time-tracking. My work runs on Basecamp. We c…
We're launching with a great set of features we could do in a reasonable amount of time. If we had tried to reimplement every single Basecamp Classic feature in Basecamp Next before we launched, it would have taken a very long time.
Basecamp Classic originally launched without even file uploads!
We'll be busy bees making Basecamp Next fill in gaps all over the place in the coming months. Looking into how we can solve people's time tracking needs with a great workflow in Basecamp Next is high on that list!
Re: The all-new Basecamp is live
#84It's fun to poke around under the hood a little bit, and look at parts of the internal API: > Object.keys(bcx.models) ["PersonOrGroup", "Bucket", "BucketAccess", "Calendar", "CalendarEvent", "Project", "Person", "CalendarDisplay", "Todo"] > Object.keys(bcx.models.Todo.prototype) ["constructor", "isAllDay", "isTimed", "urlRoot", "getBucketPath", "showPath", "bucket", "doesOccurOn", "doesOccurOnOrAfter", "doesOccurBetw…
This isn't reddit, but I'll still take a chance! Hi Jeremy, My name is Jeff Morse. I'm a Recruiter at a super-charged start-up called Mixbook www.mixbook.com I came across your profile on hacker news and have a full-time Jr. Backbone developer opening working onsite in our Palo Alto, California office that is a great match for your background/experience. Would you be ready to make the move to Silicon Valley, the most…
So everyone knows, this is a reference to David Hansson receiving a recruiter pitch from someone who didn't bother to research him. https://twitter.com/#!/dhh/statuses/175658131429400576
I'm just explaining it. I don't think that posting it as humor out of context is good posting on Hacker News.
Re: The all-new Basecamp is live
#85Earlier quoted context omitted.
For a company that goes on about transparency and clear speaking etc., the answer to the second question you've quoted is appalling. It doesn't answer the question at all. It should be: Will you continue to improve Classic? No. We will fix any bugs or other problems that stop our customers using Basecamp Classic but we will not be developing new features. Our focus now is on improving Basecamp Next so that Classic cu…
What's appalling about it? It's not necessarily true that we won't add new features. This is day one right now. We don't know how things will pan out. It's disingenuous to say we won't do something that we might do. As stated, the majority of our resources will go towards the new Basecamp. That's honest and as clear we can be without misleading anyone.
I just felt that the answer dodged the question. Your response to me answers the question i.e. you don't know if you will improve Classic. By saying the majority of design and development efforts will be focused on Next and then saying that you'll continue to support Classic implies by omission that no further improvements will be made.
Edit: To be clear, I'm not criticising the position of you not knowing - it's a fair position given this is launch day. I'm criticising the fact that the answer to the question didn't say we don't know.
Re: The all-new Basecamp is live
#86Earlier quoted context omitted.
This isn't reddit, but I'll still take a chance! Hi Jeremy, My name is Jeff Morse. I'm a Recruiter at a super-charged start-up called Mixbook www.mixbook.com I came across your profile on hacker news and have a full-time Jr. Backbone developer opening working onsite in our Palo Alto, California office that is a great match for your background/experience. Would you be ready to make the move to Silicon Valley, the most…
What is this all about then? A new kind of recruiter spam?
I don't get it. According to his profile, the guy is not a recruiter and his name is not Jeremy. I'm confused.
Re: The all-new Basecamp is live
#87I'm a bit behind the curve here - but now that I'm caught up, I'm concerned. When I saw the title of this article, I immediately logged into my Basecamp. Hmm, it looked the same. So I went and found their upgrade instructions. Then I learned that it's not a straight 1:1 upgrade, it's a different product. And they've dropped support for some quite important features, like, time-tracking. My work runs on Basecamp. We c…
I agree 100%. Without time tracking Basecamp Next is useless to us too. Migrating Classic to Next and losing our tracked time is no option.
We mainly use To-Do lists and time tracking. Time tracking as it only is available in the 49$/month price plan was the single reason we upgraded.
I'm a bit disappointed now as i was looking forward to Basecamp Next.
Re: The all-new Basecamp is live
#88http://basecamp.com/transition I want to migrate, but... > Basecamp Classic and the new Basecamp don't offer the same features, so some data in Classic won't make it into the new Basecamp. So maybe I'll stay. But wait... > Will you continue to improve Classic? The majority of our design and development efforts moving forward will be focused on the all new Basecamp, but we'll continue to support Classic as long as cus…
For a company that goes on about transparency and clear speaking etc., the answer to the second question you've quoted is appalling. It doesn't answer the question at all. It should be: Will you continue to improve Classic? No. We will fix any bugs or other problems that stop our customers using Basecamp Classic but we will not be developing new features. Our focus now is on improving Basecamp Next so that Classic cu…
Sorry, but this is exactly what continue supporting in context of software means for everyone. This is a standard term, there's nothing disingenuous. You don't expect new features in your old Red Hat Enterprise Linux installation without upgrading to a new version, do you? But you can expect bug fixes as long as it's supported.
Re: The all-new Basecamp is live
#89Next time you gear up for a major upgrade, try less time blogging for HN, more time talking to your users about the features they care about.
Why ask when they've got the usage data? I'd presume canned features are the ones least used across all users.
Re: The all-new Basecamp is live
#90Earlier quoted context omitted.
This isn't reddit, but I'll still take a chance! Hi Jeremy, My name is Jeff Morse. I'm a Recruiter at a super-charged start-up called Mixbook www.mixbook.com I came across your profile on hacker news and have a full-time Jr. Backbone developer opening working onsite in our Palo Alto, California office that is a great match for your background/experience. Would you be ready to make the move to Silicon Valley, the most…
What is this all about then? A new kind of recruiter spam?
This is an Old joke (see above)