CS/CoE Researcher (Dr. Beard), US Army Vet (Captain Beard), Hacker, Techie, Runner. interested in HPC, Bioinformatics/Comp Bio,ML,robotics,CSED, Opinions mine., Also @jonathan_beard or see me at http://jonathanbeard.io my pet project: http://raftlib.io
With its built in thread-thread FIFO support, something like RaftLib (http://www.raftlib.io) would likely rock on this. Almost have it working on Parallella, initial results are pretty decent. Seems far better than TLB/DRAM/potential page fault for every thread-thread FIFO access.
Ha, I just wrote a comment along these same lines. Given that many of the slide decks I had as a grad student had extensive genealogies at the start indicating where they evolved from I suspect that this is very much the case....despite it being a very young field.
It's also about familial/class privilege. Once you get in with a good mentor (for academics that means advisor)...it sets you up for life. Getting into a good lab (train under uber mentor X or Y), no matter if your work is crap or not (definitely not implying elite lab work is poo, simply emphasizing to make a point) will gain you citations and socialization that a lesser one would not. Want to find good work from university of Smallville USA (or equiv int'l uni)...it exists, you just wouldn't know it from the hype. It's nobodies fault really (except our own), just the way the system is setup. To break out takes extreme amounts of work, and likely can't happen. So you end up with entrenched "genealogies" like the one for mathematics. I'd suspect you could find the same in computer science (despite it being a rather young field) and computer engineering. Things like double blind conference submissions help, but even there there is trendiness to consider as a limiting factor. Going further, breaking out of this rut requires us to disseminate how to get ahead more than anything else. Who should people talk to? Where should they apply? What programs are available? What are the best conferences/journals to submit to? These are all things people in these elite circles have (even if they don't have the $$ background) which provide them a leg up over everyone else. How we even the playing field, no idea...it's a monumental task. I for one start by not caring where somebody went to school, what they look like, what their gender is, nor how they pronounce things. Can we all do that? I certainly hope so.
In summary, number of co-founders doesn't necessarily matter. What does is (in no real order): the ability to raise cash, the ability to produce something that has value, and the ability of however many co-founders you have to get along.
Could have been a much shorter article since the data are so full of confounding factors as to be meaningless. It does make for a nice headline though.
I'm glad I'm not the only one who was googling for that. I remember two different popular science or mechanics article with that headline. One that had something to do with plasma cloaking, and the other was using plasma for a heat shield...similar to the actuator concept. Again, seems my google-foo has failed...
Me to, in which case I explain the situation...I apologize to the candidate, and we move on. Last minute scheduling accidents happen, it's how you recover from them that counts. Openness seems to improve the impression of the company. Trying to hide the truth from the candidate signals an issue, if you're a candidate...run away.
This should always freaking be the case. You, the interviewer, are there to decide if you want to work with this person in the future. You're not going to learn that by making an adversary. You're not going to learn that by making it super easy either. If you're worth your salt (as an interviewer, and you should be given that you're now part of the hiring process), you should be able to go through an open ended problem (it's what I do). This open ended problem should have increasingly difficult sub-tasks and of course be related to what you intend the person your interviewing to do. One of my worst experiences interviewing was with a company that clearly didn't give a rats rear end (at one location). Interviewers were constantly late, didn't know what I'd applied for, or even at times my name. Same company, different location...totally different story. Your most valuable resource as a company is your people, treat them as such from start to finish. Needless to say, I chose where I'm at because of the people. I'm glad to see others sharing this attitude as well.
If you use grep in OS X, and you use it a lot (even called through other programs/libraries) it pays in time to install GNU grep vs. the default OS X provided one. It's several times faster. Ran into this when benchmarking grep + GNU Parallel on OS X vs. Linux in my thesis (raftlib modeling) work. Results on my small MacPro cluster didn't match those on Linux. The OS X runs were orders of magnitude slower despite almost identical hardware configurations. The culprit as it turned out was largely the implementation of grep. I compiled with the GNU version, re-ran and the rest of the mis-match was simply due to the lack of POSIX features like thread pinning, and NUMA control.
<stepping up to soap box/> So yeah...as usual, algorithm matters. Implementation matters, and well....knowledge of the architecture/data-movement matter. These days the architecture/data-movement knowledge matters almost as much or more than the algorithm. Picking an algorithmically faster implementation that moves data more (e.g., tree traversals usually have poor cache behavior, more bursts required, etc.) is often the case b/c programmers don't really understand how the computer works, but are great at coding O(n logn) algorithms. We shouldn't stop teaching algorithms, but data-movement/access likely needs to be emphasized along with the understanding of algorithms.
>which leads to the situation where poor people who desperately >need health care and can't afford it still oppose single-payer >even though they stand to gain the most from it.
I'd think education is the way around this. Start off with a "whats the worst case that could happen" then move to "whats the best that could happen." To me, you can convince people as long as you explain that their not going over a cliff. To me, this argument was never made. All I heard on the news was "it's socialism" or "it's good" but no selling the public on why it was in fact good. In this case, our leaders who were the proponents of single payer failed us. Single payer will happen, it'll just take a bit longer. The commercial healthcare industry is on a path to failure....there is no fixing it for the US. Eventually we'll end up with a system, that likely looks like what Germany/UK have (some mix of public/private).
The government, led by the people, has an ethical obligation to extend rights to parents...to include longer maternity and paternity leave for all gendered categories of parents.
I never understood why maternity + paternity leave isn't longer. Current corporate policy in America is insane for working parents. Especially when the US DoD gives 12 weeks maternity leave (http://www.defense.gov/News/Article/Article/645958/carter-an...). As a dad who had to take care of his little one for the first 60 days of his life, I can say that paternity leave should be there as well for awhile. I found myself (as a DoD employee) in the precarious situation of working when my son was asleep, and early morning/late at night. Thankfully I was the boss so I could do that (and you know, anybody that worked for me got the same privilege). It's not easy. Moms are in no shape to go back after 1/2/3 weeks, heck not even 1 month. Moms need time to heal + time with the baby. Dads can help out with that process a lot! Unfortunately, most in the US view dads as not really essential to the parenting process. This is reflected in the DoD paternity leave policy which only grants 14 days. I think valuing the fathers input would likely enhance the stability of families (see Nordic countries quest for equal gender rights (https://www.nav.no/en/Home/Benefits+and+services/Relatert+in...). I wonder how Nvidia handles parents who don't fall into the "mother"/"father" categories. That's always a huge hole in some of these plans.
You could always make it a live-in vocational school :). I thought they had more people..you're totally right, population of around 2k. Total county population might, but would be a long commute.
Hmm, maybe we should have gone with something more useful...like a free vocational school w/on-site free/low cost daycare and perhaps a primary school? I'm finding the biggest issue with people changing careers is doing so while taking care of kids. Enough free space, and it'd seem like something society would go for...then again, say "tax" and 1/2 the population turns off instantly.
Totally agree that this distracts from the real issue, and there are many here. Stop distracting folks Apple/Microsoft and chip away at the harder stuff!
Ha, that's exactly what I had in mind. I'd really love an i8, but you know what...I'm cheap, practical, and I'd rather spend the money on something that has a return on investment. If I ever find myself in a position where image matters, and it has to be flashy...perhaps an i8 will be in order. Till then, I'll keep the next gen i3 on my wish list.
I totally agree. The only problem is that when we innovate, sometimes parts of society fall behind. The real turning point to bring about what you speak of is how to enable all of society to reap the benefits of innovation. If you have a way to do that, and gain buy-in from the entirety of the third rock, then we can make some real progress :).
Probably the most important bit of the entire article, which you can probably get from many self help career books (applies to all, not just programmers):
"Ask others to explain why they do things, but don't just accept dogmatic reasoning. Demand examples and inquire about context, so that you can try to imagine what it is like to be in their shoes. Doing this is tremendously valuable because it allows you to see the strengths and weaknesses of ideas in their natural habitats."
One thing I can add is always question. There's a reason kids ask tons of questions, they want to know. Asking questions not only increases your own knowledge, and that of the person answering, but it also creates a culture where complacency is extinct. The one thing I hate more than people that litter are people that say "oh, well, that's the way I've always done it." There's lots more I dislike above that, but...complacency is the death of innovation. Then again, sometimes things just work....but that shouldn't stop you from trying to improve it.
So why not something like Iron Dome? I mean, even a basic old school phalanx system could "shotgun" a drone out of the sky. I'm guessing a generic RF jamming system likely would work well too here. So then there's the hacking potential....does the pentagon want to get these drones in tact? Or do they really just want them knocked out, b/c knocking out could take a myriad of far more primitive (kinetic) solutions than hacking.
Ok, so from the command line....you might try sips:
$> sips --resampleHeightWidth <height in pixels> <width in pixels>
Sips works for most raster image formats. Guess I need to update and re-post my OS X utility help page. There are a lot of tools buried in OS X that are quite useful.
So there I was. In the Army now. As a young adult I loved watching Stripes...the real US Army is nothing like that. In Stripes Bill Murray just got orders. In real life, you get orders and a commander's intent. When it came my turn to give orders, I learned that intent and vision were what people followed (assuming your troops have reason at all to follow the leader). Orders/plans are great, but people do best when they have something to rally around and fall back to for direction when everything else goes belly up (was going to use Aussie version, but not appropriate). Mottoes from a company mean almost nothing if they're not backed up by people who can grasp and believe in them. It's all about the leadership and the people who follow the leader, not the motto. Note: there are all kinds of leaders...don't always picture General Patton or Steve Jobs.
This article is a reminder to me that people are bloody critical of things that they don't really understand. Many products are killed, many research ideas never take off even if they're proven to work well. Ideas/products are often killed, not because they weren't great, but for a litany of other reasons having nothing to do with the awesomeness or usefulness of the idea. Products are killed b/c of politics, lack of a massive market, and most importantly poor execution. Even when things fail (research, products, otherwise), they often have a huge impact on the ecosystem. The product might fail (in this case, it really didn't), but the ideas will live on.
WAIT, my Model M blasts Slayer at every keystroke. Doesn't yours? It also has Metallica's Kill 'Em All pre-loaded in ROM. I heard if you achieve a fast enough rate it'll go straight to Seek & Destroy :).
Seriously though, these keyboards are LOUD. Most of the folks at my office use very loud keyboards, but we don't mind. We all know that we type faster with them, and we all have noise canceling headphones.
morphology I'm not so sure. looking at the evolution of keywords seems to suggest that the morphology is there. phonology, I'd have agreed with you a few years ago after I finished a minor in slavic linquistics, but now after seeing how people verbally communicate programming concepts over the last decade and how that communication has impacted language design itself...I'm not so sure. In either event, the structure of the english language has heavily impacted the design of languages used to program computers. Not so drastic a difference as whale to fish, more whale to dolphin.
How about all computer languages? They're largely subject to grammar constraints (e.g. LR, etc.), but they're quite subject to creolization and almost all the widely used ones are derived from english, nerd slang, slang tech terms, short tech terms, and shit that early programmers made up to express themselves. I've been wanting to do a study on the evolution, understanding, and psychology of programming languages (even wrote a blog post awhile back about it) but i haven't gotten around to it.