|
cached 40 minutes ago
This is pretty cool. I wish they had reused jQuery where possible, or layered on top of jQuery.
|
|
cached about 5 hours ago
My first internship had 6 of us sitting around a table, churning out code, just after my freshman year. Best thing I've done for my programming, easily. The supervisor did a good job bringing us all up to speed, and we ended up picking up C# and their framework in about a week and a half (they had a huge codebase already), and some of us learned Progress in the same time period (old english-like query & character-UI language). The important parts for us to being up and running quickly, and being productive? Nearly full-time access to one of their main developers for the first two weeks, they knew precisely what was needed (lots of similar code, but not similar enough to DRY up), and we were in the same room. For at least half the summer, we were throwing questions back and forth every couple minutes when we couldn't remember something, and the vast majority of the time one of us would remember. Immediate question & response was absolutely invaluable, and I think was the single most important tool to speed-learning what we needed to know. As time went on our tasks diverged and we knew more, so we didn't need questions answered as often, but it was massively useful at the beginning. Of course, it didn't hurt that they paid quite well. Motivation is always useful. |
|
cached about 6 hours ago
MongoDB (and SQL dbs) does ad-hoc queries quite well as long as your data fits on a single machine. Cassandra does ad-hoc queries quite well if you're willing to use mapreduce. If you have a smaller number of frequently done queries and are willing to use MR for the others maybe that is a happy place for you. |
|
cached about 15 hours ago
Yes, Aaron's post is a very good read. I still went with jQuery nonetheless.
|
|
cached about 6 hours ago
I'm looking pretty seriously at MongoDB and I've heard that Cassandra is worth considering. I do a lot of data warehousing / statistical analytics which generally means some sort of star schema-based reporting with lots of crosstabs, dimensions, etc. If anyone can relate their experience with either of these two platforms, would either be a good choice for live querying for these types of applications? I know you can use MapReduce to eventually get the data you need, but I need to support queries that respond in (well) less than a second, even for very large data sets. |
|
cached about 11 hours ago
For all my tech related queries the answers have been better than Google's. My only problem has been in breaking that mental association of "find an answer" with "type a 'g' ".
|
|
Making a Mosaic Slideshow With jQuery & CSS
(tutorialzine.com)
1 point
by Tutorialzine
1 day
ago
| link
cached about 22 hours ago
|
|
cached about 7 hours ago
What is the reason for it then? Scaling? But you still have to work on those nasty sql queries. Too bad it doesn't support any nosql database.
|
|
cached 1 day ago
I think by and large we agree: It's wrong to expect memorized answers or to ask questions that are so narrow that they only test whether a candidate spent time studying. I'd even go so far as to say that algorithmic questions are probably not good indicators for skill at many kinds of work we would call "programming"---i.e. Programming skill is more heterogeneous than many interviewers admit. We shouldn't expect a jQuery wiz to nail low-level data structure questions, and we shouldn't expect a bit-twiddling video codec developer to really grok method chaining in 30 minutes. The trouble with "Be reasonable" is that's it's the advice equivalent of a tautology. Of course we should be reasonable when interviewing. But I don't think there's widespread agreement about how to operationalize that. I'd be curious for more detail about how you would do it---you seem to have strong, well-informed feelings on this issue. To my knowledge, there's basically no publicly-available research on tech interview factors and how they correlate with on-the-job performance. The good big employers do this research internally and keep it to themselves. The rest of us are stuck with assumptions, intuitions, logic and argument. So unfortunately I don't think we'll be able to get the debate into the realm of interpreting real data anytime soon. |
|
cached about 11 hours ago
A query for "Tiananmen 1989" (in Chinese): h^ttp://www.google.cn/search?hl=zh-CN&source=hp&q=天安门+1989&btnG=Google+搜索&aq=f&oq= "据当地法律法规和政策，部分搜索结果未予显示。" "In accordance with the laws and regulations of your land, certain search results are not displayed." Some of the pages are completely blank. E.g., h^ttp://www.google.cn/search?hl=zh-CN&newwindow=1&q=天安门+1989&start=20&sa=N (Please remove the ^s and paste in links yourself... I didn't really want to send a bunch of referrals from HN to those queries). |
SearchYC.com |
|
| All | Comments | Submissions | Users | Within Results |