brownBananas
A little more info for those interested:
University of Waterloo has the generic Computer Science program as part of the Math faculty, as well as an another Software Engineering program as a joint program between the Math and Engineering faculties. Both programs offer co-op all year around. For more information, check out: https://uwaterloo.ca/jobmine/employers
How do the drones deliver to apartment buildings or any address that does not have a lawn?
Would return service work the same way?
I love the product, but a little disappointed by the limited FAQ section.
The problem I have with this article and your comment, is the generalization of the term "hackers". Is anyone that codes in their free time, a "hacker"? Is a software engineer that works full time at a company, a "hacker"? What about UI designers that write CSS? What about business guys who throw something together in HTML and jQuery? Are they hackers as well? Different people have different goals for what they are building or hacking on. I really don't understand how we are still throwing such vague terms around like we all fit in this one category of people, and we all want to achieve the same things.
Read more at: http://phys.org/news/2013-09-world-solar-cell-efficiency.htm...
Also a TED Talk by the same guy: http://www.ted.com/talks/derek_sivers_keep_your_goals_to_you...
Read-ony makes sense, and something like Cloud9 makes sense. But just editing a few files? You might have to help me out here. Genuinely requesting.
If anyone is looking for a front-end job, look in the right place. Look in the source.
This is very intriguing. Although I have some idea of what you mean, I would love it if you could elaborate on this.
* Which web[sites/apps/companies] still value SEO so much?
* Out of those, how many absolutely require a JavaScript Framework that generates majority of the "content" on the page?
* Doesn't Google (perhaps other engines as well) crawl and store dynamically generated content anyways?
* Is there really any optimization needed?
* Create private repos for all the participants well in advanced, and ask them to commit their changes to their designated repo.
* At the time of the deadline, all pushes will be blocked, and/or the current version will be pulled down to a "demo" machine.
* Participants must provide a make file (or something similar) to automate the building on all projects.
* When their time for demo comes, they will only get to demo whatever that has been compiled on the "demo" machine.
* The "demo" machine would be hooked up to the projector, and will be the only machine used for demo-ing purposes. This also saves the time spent in hooking up their laptops to the projector.
That's all. Sounds academical, but it's a really good way of monitoring cheating (provided you have an audit team as well).
What we are seeing here is an attempt to solve the same problem, but by doing all the work by using JavaScript. Cool. But not impressed.
That being said, this library does try to solve a problem, it's not useless. In my opinion, it's just not the right tool.. yet.
Other folks here have mention the separation of concerns. Is there something that you can say related to that? Loved your summary of benefits and trade-offs, but can you please address MarkHarmon's comments? Thanks.
Edit: Price difference - I see.