bobbywilson0

I don't think your problem is as complex as you think.

You have two sites right, a marketing site and an application. If it is just this I would keep both sites under the same domain and deploy your application to a sensible sub-directory. Alternatively you can make a sub-domain for the app, but this is just slightly more work since you will have to take care of this in your DNS settings.

However, if you are planning on giving your users each sub-domains then you are talking about something way more involved.

Clarify your question, and I think you will get better help.

Looks like is still trucking, albeit quite slow... http://github.com/ccgus/letters

I like the concept behind this app, and would definitely switch to it from mailplane if a few things were ironed out.

Here is my feedback thus far.

- I think this is a very nice editing of gmails features, I prefer it to the wrapping of gmail's interface that mailplane does

- The interface feels very "Tweetie"-ish, which I think is a good thing

- The tooltips feel really out of place and are obtrusive and unexpected

- I need inline spellcheck for composing messages

- I don't mind the menuling, but either it is showing something other than unread messages or calculating them wrong, also I would like some options off the menuling like compose, or mailplanes fancy do not disturb feature

1. I think that it would be more interesting instead of just testing if a applicant can do a specific task, let them try and fix it if they failed. After all, it isn't such a problem in real life if someone doesn't get something right.

2. What about having them refactor some messy code?

3. Exercises where they write tests for untested code.

warehouse makes a nice front-end to your personal git server http://github.com/drcapulet/warehouse "Re-Written from the ground-up for use with Git"

This is a nice public service announcement. It does make me think that these guidelines should be linked to more prominently somewhere, maybe on submit page?

If you are using git-flow, this should probably be done in a hotfix branch, so that when you are done, finishing your hotfix merges directly to master and develop. Without a hotfix you would have to manually merge master back into develop.

Master exists as a pristine releasable code base. Develop is the main branch for working on things, and branching usually happens from there. Having master and develop lets you keep developing on your project while having a frozen deployable branch master in this case.

If you are doing this style exactly without git flow, you don't gain a whole lot. It is great if you are working with a team then it forces everyone to work the same way and is very clear what you do in each situation. One of my favorite features of git-flow is housekeeping, for features when you close them it merges to develop and destroys the branch, when you do a hotfix it merges to master and develop and destroys the branch. When you release it creates a tag with whatever version you specify, and you can work on that until you are happy with the state of release, then when you push tags you will have a nice snapshot of your last deploy.

tl;dr: good for teams, and housekeeping

Our team uses this with great success. To take this a step further we name our features in conjunction with features in our project management tool. git flow feature start visitor_can_sign_in_812381 This gives us a nice mapping of feature branches to actual features. The one thing to be aware of with git flow is that the author is more on the merge side than on the rebase side. So closing features just involves merging on top of the develop branch. This hasn't raised many problems for our team though.

This certainly is an interesting idea. It seems to me though that all of your application logic is jammed into a single file at the presentation layer. This might suffice for very small apps, and that's fine if it is your goal. I can't imagine that you just define all of your logic in one file.

How would you go about reusing code? Could you potentially separate out logic from your template?

I would also like to see how this could be done more unobtrusively. It would also be good to show what the output html looks like after it is compiled to html.

$10 seems reasonable for paperback bound

direct pdf link: http://www.lukew.com/resources/articles/InputBeyondForms_071...

1.) good point, I need to have a redirect for a get reqeuest on api.maskedmail.net. Right now it only accepts posts to test the service.

2.) thanks for noticing I will change that.

3.) I am going to provide sign ups with an API key to with a few more features. If you do want to give it a shot now just send a post request with a JSON body of the email address you want to test.

4.) Rolling your own has more to do with setting up a mail server than writing any code. The example is in ruby but it is just an example of consuming the service. Rolling your own at this point might be fine for you, I think the value is the convenience of not configuring a mail server, or if you don't have a mail server as part of your hosting (like heroku).

The critical review is definitely helpful. I appreciate you taking the time to give such thorough feedback.

This idea was originally geared towards people building applications that would provide users of their site with an anonymous alias. So that you can get anonymously contacted, and then depending on how it is configured trash the alias. I guess it could potentially work for personal use too.

Yeah, I do realize that this would be ideal for people. It would be possible to point an mx record at me, and I could add your custom domain. So you could point your app.yourdomain.com MX record to my IP. I would know that based on your api key that requests coming from you should be created with the 'app.yourdomain.com' address and not maskedmail.net. That capability is actually built into how I have it set up now. If you are interested I would be happy to talk more about how we could get that set up.

Thanks for the feedback

I thought similar, that this would be useful for community type sites where you need someone to contact you but don't want to share your email address.

Thanks for the feedback

Looking for honest feedback if this is useful to anyone or not.

I am not trying to troll Linux. My apologies. I really want Linux to be successful for consumers. I just feel like they are jumping the gun saying the latest Ubuntu release will be the release that changes consumers. I think there are still big issues with Linux in general that makes it unsuitable for everyday consumers.

What about apps? A few of the apps they are used to will be cross-platform. Most will have a linux-y replacement, but some commercial software they were using on Windows or OS X just won't be available for Linux.

Even today I am wrestling with getting the right video driver that doesn't break hdmi audio, and fix the overscan on my hdtv. I know that bugs are an inherent problem with software, it breaks that's all there is to it.

If you want to think of it like that sure, they are running a small biz around their software. I don't see it like a regular business where you are developing your software based solely on the customers needs, the devs needs will come first. I see it more like structured donations around user requests.

I don't think you will get customers to ditch the competitors product they are already using for yours unless these extra features are a game changer for the customer. If you cut features and just work on what you need to be on par with the competitor you will just be a little later to market, and you can continue working on the remaining features. If you wait to finish your extra features, the competition will already be picking up those customers you could of had if you released early. Ultimately it depends on if those features are something you consider to be at the core of your business, if they are then maybe you are right.

"we can't really cut scope now"

Why not?

This actually makes me like North Face a lot less if anything.