I'm glad to see that Meteor is appearing in these listings however!
723 karma · joined September 10, 2007
I'm glad to see that Meteor is appearing in these listings however!
Oddly enough, chrome didn't want to auto-update to this, it was "up-to-date" at 38.x, even quitting and relaunching applied no change. Downloading a fresh `dmg` archive from https://www.google.com/chrome/browser/ applied the 64-bit update.
https://www.youtube.com/playlist?list=PL006xsVEsbKjSKBmLu1cl...
http://www.reddit.com/r/reconstructcavestory/
Cheers
I have no problem with others looking at this, I think it's probably great, but for me this is where I nope out.
I'm kind of bummed out from that one.
But yes, I agree, it's not ideal until a SQL adapter is available.
It's a bit light on details. I wouldn't say Meteor is 1.0 yet, but preparing for it. Also Worldwide Meteor day is Nov 6th, I anticipate a more formal announcement then.
Consider using different/manifests layouts if you're concern is client-side. If it's compiling assets I think your concern is misplaced.
> admin panels tend to use large amounts of RAM etc
I don't think this is the case, or a huge concern depending on you're environment. Further, you could separate the apps into engines, they're great for this. TaskRabbit did a write up on this: http://tech.taskrabbit.com/blog/2014/02/11/rails-4-engines/
Personally however, I've normally roll out the app as one piece with active-admin, generically speaking most apps have little admin-specific logic to them, for example, it's normally something like: "Do <x> for user(s)", "Approve <x> content", the type of operations you do can easily fit under the simplistic nature of what active-admin offers. This isn't a catch all however, some applications require more of an integrative approach, in which case it's development as normal, bits of functionality injected here and there so-to-speak.
https://www.youtube.com/watch?v=1Y1ya-yF35g&list=UU3XTzVzaHQ...
http://www.reddit.com/r/television/comments/2bxfzq/john_oliv...
It's pretty frakked up.
Edit: Oh, and the cold war is heating up: http://www.reddit.com/r/worldnews/comments/2c1emy/russia_may...
None of this is settling.
I do this for many reasons, one of which, is they obviously weren't interested enough in my talents to throughly research me before the interview to assess my skill-set, which means, they weren't that interested in hiring me to begin with. I don't want to work for someone who is just slamming through interviews for talent; I'll bow out. I want to work for someone who is specifically interested in working with me and understands my skill-set before hand. The second reason, I don't deal with these questions is that I don't like to be put on the spot without my normal working environment, I feel at a disadvantage and uncomfortable. Keep in mind most developers are introverts.
I consider a good interview to be about people; not technicals, which can be referenced/refered or looked up; they should provide a medium to see if the employee is a comfortable fit. If goals and motives align. To talk history and such.