skysight-inc/HackerNews huggingface dataset:
This. Although I'm less civil about it - I'll start giving people shit for rubber stamping my code reviews.

"Why are you letting me ship this terrible code I wrote? Do you want us to end up in a death spiral of technical debt and crunch? Don't be an asshole, critique my shit! We all need a second set of eyes - I'm no exception!"

...okay, I'm maybe a little more civil than that. But I'm not above leaving some mistakes unfixed to call them out on.
Is this new or only if you own a Watch? Because if I'm on my MacBook and an iMessage comes though, I get it on all five devices (computer, iPhone, iPad, and the two other iPhones in our family that use the same account).
The first thing that strikes me about this story are the parallels to the Wen Ho Lee case in 1999.

From Wikipedia:

[A] Taiwanese American scientist who worked for the University of California at the Los Alamos National Laboratory. He created simulations of nuclear explosions for the purposes of scientific inquiry, as well as for improving the safety and reliability of the U. S. nuclear arsenal. A federal grand jury indicted him of stealing secrets about the U. S. nuclear arsenal for the People's Republic of China (PRC) in December 1999.

https://en.wikipedia.org/wiki/Wen_Ho_Lee

The charges agains Wen were ultimately dropped, and $1.6 million paid from the US Government and media organizations, though his reputation continued to suffer. He's now retired.

The second thing that strikes me is to never talk to law enforcement. The lying to Federal agents charge came from Chen's describing a trip as occurring in 2011 rather than 2012.
This is a video about the South African mining strike (which I agree was a clusterfuck). The conversation was about oil exploitation in Iraq. How can I take your position seriously when you just move the goalposts around like that?

My basic point is not that corporate investments are necessarily fairly run or favorable to poor people in a developing country. They're not, and if you read my posts here regularly you'll see I'm actually quite skeptical of corporate governance and market idealism.

On the other hand, one has to recognize that it takes two to tango; corporations buy things like mineral exploitation rights from governments, and ultimately the government of a nation has to be responsive to its population, notwithstanding the fact that many governments are despotic. This being the case, it behooves new governments reviewing unfavorable deals to renegotiate terms like royalty rates or lease terms (both of which happen all the time), whereas unilateral expropriation should be a last resort because it signals to any and all investors that the country in question is an unreliable place to invest, so you scare away ethical investors as well as greedy ones.
Semantic hashing by similarity is one way to create more
sensible representations (Re: Proposition 2): http://www.cs.toronto.edu/~rsalakhu/papers/semantic_final.pd...

This would also fit well into memory networks: http://arxiv.org/abs/1410.3916, SDM: http://en.wikipedia.org/wiki/Sparse_distributed_memory
or global workspace model: http://en.wikipedia.org/wiki/Global_Workspace_Theory
Yes. Of course. But you you will be more valuable to potential employers if you learn objective C.
I've been an iOS guy for 6 years now; recently, I've had to pick up swift to adapt with the market and the many readily available resources being in swift. I say this because the advice I'll give you is based on what I've seen in the Bay Area, larger companies, and even from a personal learning experience. If you can build an app from scratch in Swift and publish it to the App Store, then you're golden in the job market. It's always the apps you have in the App Store that will bring out your resume when companies look to bring you in for interviews. With that being said, here are some pieces of advice I have for Swift vs. Objective-C:
- Learn Swift through the iTunes U Standford course and master it
- Stay upto date with the NSHipster blog for many of the ins and outs of Swift, Obj-C, and the iOS framework
- Be sure to learn some of the Objective-C concepts that aren't that common in Swift (contact me for more details)
- Research the common iOS interview questions as many of them still pertain to Objective-C
- Understand your basic CS theory: Data Structures, Algorithms & their complexities, OOP, System programming
- Integrate libraries that are written in Objective-C into one of your Swift apps and be sure to know how to incorporate it correctly

Currently, I'm working with a team of iOS engineers to build out our SDK for our service. One of the issues we've come up with over the past year was Swift vs. Objective-C. We made the decision to continue development and refactoring in Swift while maintaining our well written Objective-C code base. So, anyone coming on to our team would need Swift experience and be able to understand some details in Objective-C.

If you have any questions about what I mentioned, you can email me: aqadan@gmail.com
One thing I found that works.. When it doubt kiss the girl [1]

[1] Happly Married for 8 Years Now.
Your second point is analogous to companies asking for X years of experience in a language that has only been out for y years, where y < X
Do you have any evidence that, say, NAFTA was secret before the vote? I don't recall any of that from the time. I also don't recall this level of secrecy around climate negotiations.
Rawhide?
'Structured knowledgebase' is a completely ridiculous and inaccurate way to characterize probabalistic logic networks and the OpenCog component architecture.
I do understand. Going through Hired is a dramatically accelerated process of the regular interview cycle. So while you might get those annoying interviews, you won't have time to dwell on them because you'll also get some great interviews and it is all packed into a week or two instead of dragging on for months on end.

Perhaps in other words, you are guaranteed a few bad interviews. Interviewing is very random. I have sat on both sides of the table. I have sighed when other interviewers have bought up minor quibbles about otherwise excellent candidates. There are a lot of really bad interviewers. Getting interviews at a bunch of places that really desire to hire you somewhat lowers the crappy interview percentage.

Yet another way to put it is you are practically guaranteed a bad interview. It is best to accept that and move on. I had what started out as a really great interview process go bad when I went on-site. It happens. The randomness of the interview process and the fact we're all human/fallible practically guarantees at least one bad experience. My bad experience really bruised my ego but ultimately, I realized it was a good experience too when I framed it in the context of the overall experience.
That is the general procedure for any function of course. The problem usually lies in implementing these steps, which requires an expert.
I feel like I'm starting the transition from stage 1 into stage 2. I just completed calculus 3 and introduction to discrete mathematics (which I realize is still VERY early into math education), but I'm starting to be able to read proofs and be able to utilize concepts without needing to be able to strictly have any concrete applications for those concepts.

It's very exciting, I feel like I'm finally able to play by the rules of math, and I'm looking forward to the places this newfound knowledge can take me.
Excellent feedback! I've updated the code to randomly generate the key during bootstrap.
Ah... I'd forgotten about that. I owned an Apple //. I should know better.
Mods, Please mark this as 2009.
for what it worth - tried to find story about lawsuit you mentioned, when stumbled upon this - http://www.stellaawards.com/bogus.html :)
Part of raising money from (most) LPs requires a bit of showmanship akin to that of Lawyers and Investment Bankers. This goes beyond the taking a "client" out to dinner. It's the expectation of living a specific lifestyle and the perceptions the wealthy have of those asking for money. Also, consider the amount raised (typically XX million+). That usually allows you to pay $200-300k salaries (though whether that's right / justified is a different conversation).

As wealth changes hands over time, this expectation may change.
I'm pretty sure i'm not world class.

That said, twice in the past few years I've been in the situation where the interviewer was wrong (recently like over a dozen times in the interview on different topics!). Most of the time I just brush it off, but I'm not the type to let things slide on technical issues with black and white answers.

So sometimes if pushed i will try to gently backup my statement with concrete examples (goggleable if you will). But, still if you piss someone off by telling them to google it, you definitely get the "culture fit" answer.

So, i'm not sure how to crack that nut.

Maybe the best answer is you probably are not going to fit in, and terminating it early is a good idea. Its like the crazy member of the opposite sex who breaks up with you, and all you feel is relief.

BTW: When I got the culture fit answer recently, I almost sent the hiring manager the "your techie is presenting himself as an expert in the following areas critical to your success but he thinks a,b,c,d. These aren't even areas subject to disagreement by knowledgeable people. Here are the actual answers complete with hard references you can verify." But when I cooled down, I figured the best response was the pleasant thank you for your time answer.
I agree -- the interview process is a direct reflection of the organization you are interviewing for and you should judge your potential employer on how they interview you.
A thought provoking older article by Steve Yegge that many I talk to haven't seen. It discusses styles of programming from the perspective of memory allocation.
I really don't see how it was replaced. Now we just have three or more smaller products that some people use.

many people still use XMPP and magnitudes more use XMPP and don't even know it.
Glad to hear that the project helps!
Earth's orbital velocity is 29.78 km/s, and the escape velocity from the Solar System, at Earth's distance, is 42.1 km/s.

Of you want to get rid of something, it would be energy-wise cheaper to shoot it out of the solar system, than to slow it down completely so that it would drop into the Sun.
This is not what an interview at Disqus is like. We interview you like we work. This means you are going to code and you are going to lead a design discussion.

Coding is done on a computer you bring with your tools in a language you know. You get to use the Internet to looks stuff up, you know, just like you can when you are really doing your job. And the questions we ask are problems we have had to solve at work.

The design discussion is collaborative, the interviewer is an active part of the discussion playing a sort of devil's advocate.

If this seems like a process you would like, we have a bunch of python positions open right now, check them out here: http://grnh.se/vj71bo
That was very helpful. Thanks.
Those metal beams are called aluminum extrusions and are sometimes referred to by the brand name "80/20".

They're super fun and useful in prototyping - kind of like an erector set for adults.
Django 1.8 and Python 3: Complex app tutorial, end-to-end
Fortunately for us all, precious few of those places are in the Bay. The vast majority of San Francisco can't even be reasonably called mid-rise neighborhoods.

But let's not get caught up in that yet. In what way would density "objectively and significantly decrease the quality of life of all existing residents"? From your phrasing, you clearly have solid evidence and objective metrics for your rather strong claim about both significance and universality.
Because as much as spending 4 hours doing unpaid work may seem to suck. (Which let's face it, I do at least 8 hours of unpaid development a week on side projects.) It's a better and more accurate test of your abilities than doing what can only be compared to that of a trivia based game show.

Option A) Spend anywhere from 2 to 12 hours interviewing for a position with little to no break. While being asked to solve problems, that may very well actually be unsolvable, under the pressure of rotating team of people. And for bonus if you suffer from any sort of test taking anxiety in school you'll get to feel the blood drain from your prefrontal cortex, as your fight or flight instincts kick just enough to make sure that doing high cognitive work like programming is next to impossible.

Option B) Spend a few hours solving a hopefully interesting programming challenge at home where you're probably not wearing pants.
To train a cluster of clusters of neural networks (which is the basis of associative, verbal mind) some "primitive" machinery is required. This is what we call "awareness" or pre-processing (pattern matching) of sensory input, which is prior to the intellect, which is based on a language and related mental concepts, which are socially and culturally conditioned and mostly wrong.)
Strangely enough, glass lasts a very long time in terms of actual time from the perspective of geologic longevity. Pieces of glass will tell humanity's story long after buildings and roads crumble to dust. I understand that shards resting peacefully and a pathway that is used constantly are very different things, but I never cease to be amazed at the strength of glass and how much it has strengthened in my own life time. Just a thought.
Maybe I am in the minority here, but I thought the interview process was super fun! I enjoyed solving puzzles on the whiteboard and the courting process. "Forced to write whiteboard code" ... is that really how you feel about it? In some ways solving well-specified problems (often a few carefully-crafted gems) with a captive audience is a special treat. And then you typically have the opportunity to turn the tables and ask questions about their business and engineering challenges. Maybe just relax a little and try to have fun with it? (I know, easier said than done when your career is on the line.)
There is something of a difference between a neighborhood having a say in its future and a neighborhood having a dictatorial stranglehold on all changes within its bounds. Does the rest of the city have no say? The county? The state? The country?

Would you be OK with this principle if a white neighborhood wanted to enforce a "no black or brown people" rule? How about a "straight people only" rule? How about "no poor people"? This isn't a purely abstract question, but an actual question that has arisen repeatedly in the history of the US. Sunset Towns have been real things.
How does your plan address the problem that there isn't enough housing here for all the people who work here to live here? Are you assuming that if there are living wages all around, that there will be enough construction?

Or do you expect people to just live somewhere else nearby?
"would sell their girlfriend"

Really not appropriate here.
> Also, the focus is often on how you approach the problem, not if you write up a perfect solution or not.

This is a common misconception. Unfortunately, most (read 99%) interviewers expect you to come up with exactly the same solution they have in mind (or in paper/screen in front of them). Even if your solution is correct but different, as soon as you start to diverge from their solution, you're red-flagged.
I find that companies don't know how to interview, and therefore the individuals doing the interviews have no clue what they are supposed to be interviewing a candidate for.

If teams would prepare ahead of time, they would create a schedule for the process with specific steps for specific areas of interest: personality and fit, general algorithms, design approach experience, domain expertise If core to the role, ability to work well with others, general approach to the craft, approach to quality, money expectations, check for previous projects, references, etc. I have been in interviews where 8 people try to compete to see who asks the most bad axx question with no flow whatsoever. Or other times is the "big shot" with experience on the latest framework of the day who has no experience in other things at all. What a waste of time.

My approach sometimes, particularly with the younger interviewers, is to pause the interview, ask them what they are interested in knowing, and then give them some hints, through comments, about the questions they should be asking me.

For "how many balloons fit in this building" question, I ask what is the purpose of the question. Sometimes they don't know! Then I say "let's figure this out together." And then have a little fun together while showing estimation skillS or asking clarifying questions: is it regular children balloons or hot air ones?

For coding questions: pull out the laptop and show them.

People: prepare your interviews.

Candidates: take control of the interview if the company didn't. You already invested the time so might as well help turn it around.
I agree 100% with the "don't be a blocker." I personally look for about 80-90% yes and if it meets that criteria with no errors, I thumb it up. If I can't thumb it up, I try to put a "thumbs up with commented items fixed". I try to not block -- comment for bad issues, sometimes sigh but agree when it's a 10% disagreement and go forward. Life is a series of iterations. That 10% will be addressed in a future iteration.

And I never close another persons PR.
What do you mean the computational part isn't new, who has done it before?

I would guess the part that would be commonly done is the texture mapping and the print out of some kind of simple projection

It looks like they have added, crucially, the math to account for the topology of the dipping process.
Well, so is OS X. It runs on Mac Mini, no :)
We do the bulk of our reviews at the pull request stage, as line comments on commits (we use Github). These are visible to all team members. This form allows developers to take the time to phrase the feedback diplomatically.

I've also set the tone early on in my own comments (I run the development division) and I've encouraged the more experienced and talented members of the team to review my own pull requests. When they spot a problem in my code, I always make it a point to praise them (if, of course, the problem is valid). This seems to have worked.
Working in industry it IS straight Verilog directly. No macro language in Perl or anything else.

Maybe people use emacs to help make stuff neat but that's it.
Qualcomm has their own tool that created register files for sub modules from a MSWord table and it sucked big time.

Parametrizing is just via `defines.

On the verification side, it is System Verilog or something similar. On top of that is a pile of crap called UVM.

For an engineer it does not matter about the language that describes the circuit. It does not matter how many lines it takes to add a pipeline stage. The effort is in creating the design itself, not how it is represented in text files.

Typical engineers write hundreds of lines every day when they feel like it. Think of the complexity of an SoC in a mobile device. There are millions of lines of Verilog for the design and the same or more lines of System Verilog to do the verification. Typing it in is the easiest part.

The real work is simulation of the design under test running millions of cycles. Say we are verifying the wifi, we have to simulate traffic of transactions to and from the device. Millions of transactions while the design is running at various clock speeds with other modules also creating traffic on the buses etc.

Waveforms and log files is the majority of the work.

These languages from academia don't fix anything I care about.
I wish this crowd could recognize a constructive comment. Nim is a legitimate alternative to trying to shim Go and Rust together.

I still think it's cool that the OP tool exists, that's not my point.
Have you considered going out to lunch with them or grabbing a coffee and bringing it up? If you're in an organization where you wouldn't be comfortable with that, maybe talk to your manager and ask them about it? Basically, we all have to toughen up a little bit when getting reviewed and it is for the good of the project/team. So getting someone who is uncomfortable past that is a win-win for everyone.
I don't think you understand. Or if you do, we have very different ideas about what's important.

He was my direct manager, but we were literally a team of two, working on a project together.

He was unabashedly wrong - not slightly wrong, not a bit confused, not misinterpreted - just flat out wrong.

When I told him, I didn't make a fuss, I didn't make a big deal, I just told him calmly "no, that's wrong, X because Y".

Literally my only other option was to say nothing, and let the project waste time because of his incorrect assumptions/ideas.
I was recently at the edge of the Tenderloin, in Union Square, when out of nowhere when a man walked up behind me, drunk or high or crazy (or some combination of the above), hands covered in blood, and a trail of blood behind him. Before I even noticed him, he casually wiped his bloodied hands on my shoulder, and slurred some loud but incomprehensible statement at me. Not really sure how to react, I briskly walked away, and kept an eye on him doing much the same thing to other people as I did my best to simply keep my distance. Perhaps I should have called the cops, perhaps even an ambulance given the state of his hands, but in all honesty I just wanted to keep my distance and not get even more covered in blood, or assaulted in some even worse way.

I'm not trying to make any particular point with this story, just adding my contribution of an event that happened in the area.
Looking at elasticsearch, the first thing I see is a pom.xml. Seems sketchy. ;)

Seriously though, none of my servers have a JVM installed. Most of them have nginx and ruby on them. And all of them talk to a handful of postgres servers. If a client wants to add some kind of full-text search to an app, this is a great approach to doing it in a cost-effective way. I don't particularly want to have to add more infrastructure just to be able to search through data. That's an additional monthly cost, along with a new environment to monitor for critical security updates etc.

If someone needs high performance search, sure, I'd cost out elasticsearch or solr. If they just need something basic, postgres full-text looks like the perfect low-effort solution.
>>the math to account for the topology

Looks brute force to me as it is base only on the forward problem.
I'm not sure how you can be so certain? (99% of interviewers..?)

I interviewed a bunch, but not for a few years. More recently, I've been on the other side of things. In all my experience: yes, some people expect a very specific answer from you, but not most.

Most people look at how you approach the problem, how you solve it, and what questions you ask about it if you need any clarifications. You can often tell someone is a good programmer even if they don't fully solve a problem, or if they happen to pick an approach that doesn't work out.

Again, that's my personal experience and knowledge, so I can't be sure how common it is.
Twitter had revenues of $1.4b in 2014 - for a tech company (i.e. low marginal cost of delivery), I would say that's enough to support a $24b valuation.
In interpreted environments, registers are stored in memory anyways, so the advantage of simulating them isn't as great

...unless the interpreter maps VM registers directly onto machine registers. With some VMs it's possible, and then you can get very good performance.
Also can we have support for Rpy2 or some kind of python -r ffi please????
> Without revealing my own secret interviewing sauce

Why is it a secret?
https://github.com/disavow/below-repository looks like they have that too