If you're responsible for a software's architecture you should not object to being called a "Software Architect". #archflamebait
2
1
1
Let's tweet some potentially controversial statements about software architects and see whether they *are* controversial. #archflamebait
3
1
1
@mirko_novakovic I can imagine that could be a logistical problem, but we're open to discussions … probably better by mail
1
I love Adobe's free Source Code Pro font: blogs.adobe.com/typblography…
5
12
@phaus an app that expects an HTTP header *is* self-contained. In fact it's much simpler if it just relies on the username
@phaus I don't see doing auth in a frontend web server as not compliant to this rule, BTW. On the contrary, in fact.
2
+1 :-) @mnot: @vambenepe Congratulations! I'm sure you'll make us all proud.”
I find that pseudo-interview with Linus Torvalds astonishingly dumb and not funny at all. Must be a different kind of humor
1
@thejayfields Got one too, but I'm still wondering. Worth it because of …?
2
@thejayfields I never used Google Reader (except for backend synching) - I still use NetNewsWire w/ tons of public and private feeds
1
@phaus That's the difference between authentication and authorization. I'd never try to do the latter outside of the app
1
@phaus That means your app needs to change when your auth requirements change. I prefer clearer separation of concerns, and multiple apps
2
Very interesting: “The twelve-factor app is a methodology for building software-as-a-service apps” 12factor.net (via @phaus)
4
6
@phaus Fire up your own server that just has the auth part, and proxy traffic through to your app. Still preferable IMO.
1
@phaus All of these are infrastructure issues, not application issues - not at all related to business functionality
2