Ah ok yeah that makes sense. Pre-generate a signed token and post it along with the form. I guess in that case you wouldn't even need the jS-SDK since you can just do a normal POST/PUT to the s3 bucket with those credentials. I guess I got excited only to realize nothing would change ;)
How does this generate security credentials for a user client side? It mentions Identity Federation[1], but it looks like that links with Google , Facebook, or Login with Amazon. Is there a way to to authenticate a user without a 3rd-party login service?
> Working with isolate scope and transclusion is tough, and Angular’s documentation on the subject doesn’t make it easier. We found that before jumping into writing an ambitious directive, it’s best to start by not writing a directive — just using normal templates and controllers — and then roll that code into a directive once you really figure out what your requirements are, or once you start repeating yourself..
Directives are, IMO, the most powerful parts of angular. They're also the most confusing. OP makes a great suggestion here that I'd recommend as well: Start with a normal template & controller then refactor into a directive later. In my experience, I've found that it's been useful to focus less on the DOM manipulation that needs to take place and more on the where the data collected needs to flow. In this way the directive just becomes the "glue" between a tiny area of the DOM and a parent controller and/or scope.
I guess you could liken them to the behavior/logic you'd have in a backbone view? That may be a stretch though. Powerful nonetheless.
I second this. The videos are really great and are delivered in a way (short, to the point) that really helped me connect the dots in the areas where the Angular documentation wasn't sufficient. Especially the directive api, John does a great job there explaining isolate scope which was confusing to me for a while. Once you get it down you begin to realize how powerful Angular is.
It's also important to note how important positive behavior is on those around you. One thing I've learned since programming professionally is that it's a team sport -- doesn't have to be, but in most cases you'll develop along with others. When you develops habits of cynicism and negativity it spreads. To those junior, to your direct peers, and especially to non-technical teammates.
I've found that by setting a positive tone, especially in somewhat negative situations, speaks volumes. Cynicism is easy. Pushing those feelings aside and remaining stoic in tough times helps tremendously.
Depends on the product I think, however I do enjoy apps that I can "tour" without signing up. Especially if the sign-up isn't quick.
If you can build value in your product without forcing me to login, I'm more likely to want your product more because I've been sold on it. I think thats important, I should want to sign-up. This could be via a product tour, guest account, even a demo video. Ultimately I'm window shopping so give me a reason to come inside.
No matter what though whether you allow anonymous users or require a sign-up, measure the funnel between guest-user and registration. Find out where your users are bouncing and where you could improve the onboarding. Is the homepage persuasive enough? Is the sign-up page itself losing users? Measure, iterate, and repeat. I'm sure there's quite a bit to learn.
Yeah, I've heard some great episodes of WTF. It's one of the few I listened to this past year as well. Its interesting hearing a more serious side of comedy, the guests he has on are pretty well-known too.
Thanks for your help!