skysight-inc/HackerNews huggingface dataset:
Algorithm Desgin textbook vs. Programming Interview book for tech interview prep
I am graduating college in May with only 2 years of computer science education(switched major in my junior year and the course requirements are not too strict in my school), and I have about 2~3 months for my job search.
I'm just a mediocre problem solver, and I suck at technical interviews.

I want to become a great problem solver, and I am considering two options for the 2~3 months that I have for interview prep:

1. studying Algorithm Design by Jon Kleinberg and some problems in the recommended problem set (20~50 out of 300 problems) in Elements of Programming Interviews(EPI).

2. studying Elements of Programming Interviews.

I have studied about half of Algorithm Design in an Algorithm class 1.5 years ago, and I loved the book because it helped me learn how to approach problems. I also liked the rigorous proofs and the way it explained the problem and solution.

However, as I took technical interviews, I felt that the problems asked are mostly well-known problems and that the interviewers cared more whether I knew the well-known algorithms for the problems, than how I approach the problem (and it was very hard to demonstrate a good approach the problem in 30~50 minutes if I did not know the problem.)

Therefore, I thought that maybe trying to get familiar with as many problems and working code solutions to them as possible would be the best strategy.

Algorithm Design covers a number of different realms of algorithm, but only covers a small set of problems for each chapter. Also, it only has pseudo-codes, so I cannot learn the C++ codes for the algorithm(although this can be complemented by Elements of Programming Interviews and Hackerrank)

I cannot decide. I get interview requests from my dream companies because my resume is good, but I have been delaying the interviews for almost a year and still am nowhere near being prepared.
Clouds reflect light. Arcing can be extremely bright to night-adjusted eyes.
Forbes 'Thought of the Day' hijacked to distribute malware
The Muslims of Early America
That essay seems far too hardlined.
"Reading is nothing more than a substitute for thought of one’s own." -S

Really? I'm going to agree that your "consuming content" fits this bill (in all mediums mind you. Mindlessly doing anything fits this bill), but I've taken to reading used books with red pen, and scarring the pages with excerpts, thoughts, counterpoints, interpretations, etc. I view that as an absolutely critical part of reading now.

"and it may sometimes happen that he could have found it [some great truth] all ready to hand in a book and spared himself the trouble." -S

You don't FIND these truths in books. The books bring out and expose the truths that lie in your experience. Take, for example, reading the classics in high school (Heart of Darkness, Gatsby, Crime and Punishment, etc). Those books meant notheng to me. My experiential quorum was unmet. I couldn't even vote on whether these topics were relevant (let alone true). It was only after I experienced, felt, lived. Only after being could the books show themselves. The authors feel the same way you feel, they just put it better. More succinctly. We all have the ingredients, they just know how to simmer things.

Compare Schopenhauer with Hemingway (Death in the Afternoon)

"People in a novel, not skillfully constructed characters, must be projected from the writer’s assimilated experience, from his knowledge, from his head, from his heart and from all there is of him. If he ever has luck as well as seriousness and gets them out entire they will have more than one dimension and they will last a long time. A good writer should know as near everything as possible. Naturally he will not. A great enough writer seems to be born with knowledge. But he really is not; he has only been born with the ability to learn in a quicker ratio to the passage of time than other men and without conscious application, and with an intelligence to accept or reject what is already presented as knowledge. There are some things which cannot be learned quickly and time, which is all we have, must be paid heavily for their acquiring. They are the very simplest things and because it takes a man’s life to know them the little new that each man gets from life is very costly and the only heritage he has to leave. Every novel which is truly written contributes to the total of knowledge which is there at the disposal of the next writer who comes, but the next writer must pay, always, a certain nominal percentage in experience to be able to understand and assimilate what is available as his birthright and what he must, in turn, take his departure from." -H
'Zawinski didn’t do many unit tests. They “sound great in principle. Given a leisurely development pace, that’s certainly the way to go. But when you’re looking at, ‘We’ve got to go from zero to done in six weeks,’ well, I can’t do that unless I cut something out. And what I’m going to cut out is the stuff that’s not absolutely critical. And unit tests are not critical. If there’s no unit test the customer isn’t going to complain about that.”'

I couldn't agree more. That's what I cut out as well when up against a deadline. The problem is, when is one not up against a deadline in the professional world?

Because of a combination of no planning, bad communication, and just plain laziness on the part of product, I got a chance to see what not being up against a deadline in the professional world is like. For a few months, my team wrote beautiful code, did in-depth code reviews, tested everything that could be tested, and dotted all the i's and crossed all the t's. To be honest, the pace fell even more than I expected as other team members who didn't know when to leave well enough alone just kept on making or suggesting unnecessary tweaks and re-factorings. While it was slightly cleaner and better, the code we wrote then was only marginally so compared to the code written in haste at crunch time. If I had to put a number on it, it'd be ten percent better. For two or three times the amount of time and effort put into it. The point is that there is always a balance that needs to be found.

I have seen and worked with the type of code that Joel refers to and it's definitely just as bad as any spaghetti. I have also worked with people who intentionally over-engineer or spend a lot of time on unnecessary minutiae that overly complicates code and the design. These are real problems indeed and they lead to code that looks nice from a bird's eye view and even a short inspection but leads to screaming when you have to work on it. I think both the duct tape engineer and his opposite are both extremes to be avoided most of the time.
Office Bully Interactive Scenario
18443737878|Gmail Help Number|Gmail Support Number
People has to pick a side. It makes no sense supporting two 'compatible-ish' platforms going forward.
we are the best service provider in usa for any technical support regarding gmail call us at our toll free number 18443737878. we are gmail help number, gmail support number.
Its like nobody can ever improve themselves without being reminded that they were once 'bad'. This, I believe, is the crux for why progress is never made in society until someone gets up and says "enough is enough". We have no perfect martyrs.
there are some paid one from VTC and Lynda
Their enterprise distributions were very much centered around GNOME. Remember that this is when they still had Xamarin.
Most of the time /bin/sh would suffice as no bash features are used but people still use /bin/bash.
Arch. I just started using it a few weeks ago for development purposes and it blows the socks off of every other OS I have ever used in almost every way (besides the initial install).
Learning to rank for personalised search (Kaggle competition summary)
Yeah, that's the wrong 1,000.

Reconsider if your unit price is under $1,000.

A $1,000 per unit device that you can sell can cover up a multitude of sins because it's likely profitable from the first sale.

A $10 per unit device won't be profitable until 10,000+ units.
So...here's my question to everyone applying:

What is the single motivation or incentive for you to get in? Does YC offer something that you are unable to find or obtain on your own?
...well, it makes me question the particular style of the article given previous allegations against the author. This breezy style of journalism is sometimes too entertaining to be rigorous.

Like the quote attributed to an attendee of the Eleusinian Mysteries? that you felt “new, astonishing, irrational to rational cognition.” Where did that quote come from?
Redis cannot replace etcd: etcd (like zookeeper and chubby) offer strong consistency, which Redis does not. These requirements are key for building things like a directory service (which is how CoreOS uses etcd).
I'm in agreement with you, but that essay you linked is... virulent. Easily misinterpretted. "There is no pure thought but those you come up with" type stuff.

This reminds me why I need to stay off these aggregator sites, why I now write letters to my friends instead of messaging strangers online. While the novelty of the discussion is welcome, I prefer [need] time to stew things over. Basic things. Really chew them. See now I'm sounding like Schopenuaer. Things are complicated. Damned complicated. More complicated than the 6 hour time window the obsolescence of this comment section allows for.
Every time you bitch, consider this: you've still got users.

It'd be appropriate to bitch about it if you didn't have users. But, in the end, it doesn't matter how fancy things are: the user is the only thing that matters. Ever.
>Multiple inheritance often makes it extremely difficult to tell where my code is coming from.

Thus the rise of the "can't do anything without an IDE" developer ..
Does this spit out a useful human readable set of instruction?

At its core, Autoprotocol is just a way to agree on how to capture all of the information about an experimental method, which in itself turns out to be deceptively complex (though looks a little obvious afterwards when you see it). That description is just JSON: it can be generated by scripts, UIs, or written by hand (and we at Transcriptic + customers do all three) and it can be consumed by lots of different things. If you have a lab of your own, we'll release our to-english converter soon! You can also post the protocol JSON to Transcriptic to run it in our cloud lab environment, which produces a preview of the instructions that looks like this: http://imgur.com/EOBfZfW
Making the voting process fair in 2015
Show HN: TimeStorm iOS version
It's a flaw. A bad one. But things like this get patched every day. Only an idiot would believe there aren't plenty of other undiscovered security flaws in windows, or any other OS. What matters is whether this flaw was ever exploited, whether it was ever spotted in the wild, before it was patched.

I am more than happy to criticize microsoft. I truly hate windows and everything it represents. But the system seems to have worked here. The bug was reported and patched before it became a widespread issue. I'll save my venom for those all-to-common days where Microsoft fails to address a problem in a timely manner. (or also Apple, plenty of venom for them too.)
As far as I know, ipredator is not a service to prevent logging, they're a service to prevent unauthorized surveillance.
Show HN: Msngr.js, a messaging library for JavaScript
I started working on this small library some time ago and use it in many of my personal projects. It’s not meant to replace any existing libraries (though you could certainly use it to replace some things here and there) but to augment by using messaging. I use this quite frequently when I work with web components where I try to make my messages as generic as possible so I can separate my UI from my business logic completely.

Not sure if others will find it useful but figured I’d see what feedback hacker news would have, if any :)
The great Medieval water myth (2013)
Check out the awesome Chrome experiment therein!
It was a balance test / demo, not just a "kick".
Furthermore, since these IMSI catchers are mounted on planes, can't they be detected by the fact that they are moving?
wow, hadn't read the post. that alone puts me firmly rooting for the io.js camp.
> This particular vulnerability appears in the GUI component of Microsoft Windows Kernel

There's your problem right there.
Reseller of AWS or GCE in Norway?
Hi,

I'm looking for a reseller of AWS or GCE in Norway so that we can get invoiced for the services instead of having to use a credit card.

Anyone know of a company that does that?

Thanks.
Surprised by the negative reaction.. More technically, processor speeds required far more electricity to increase clockspeed which required much more energy to disappate in the form of fans and heatsinks.
How many of those new protections listed (DEP, ASLR, page 0 mapping) are still useful with a system like Rust? Cause it seems like a hell of a lot of effort is going into hardening the environment cause the code is just that leaky, but I'm probably misunderstanding something.
Not my experience at all. The day I randomly installed win2k beta (distributed with some magazine) I never looked back. It was so stable yet so fluid. It smelled better design (gui, driver model,...) all over.
Note that even though Rust does name mangling, it does not necessarily mangle names exactly as C++ does (and different C++ compilers on different platforms may already differ on how they perform mangling, it's not standardized).
I just use "find definition" or mouse over.
I was expecting a "complete bootstrap", but even after the end of this article you're still using Mono to compile any further executables you want to run on CoreCLR, right?

I guess what I'm asking is, where's the open-source MSVS C# compiler core+build system+CLI tooling?
I have started taking "I write bad code", "I don't write unit tests" etc with a pinch of salt. I think in any real world scenario there will be factors that pull the code in one direction or the other. Sometimes the most important thing is to ship, sometimes the most important thing is to ensure that you can keep shipping. It is entirely contextual.
Or as a responsible game developer studio you could release the server for your 15 year old MMORPG to the fan base. Turbine is working on releasing the server and the tools for creating new content to the fans now after they finally stopped the monthly updates last year.

http://massively.joystiq.com/2014/12/05/work-on-asherons-cal...
I've read it 4 times, and people keep pointing out hidden gems I hadn't noticed. Hofstadter has a remarkably complex sense of humour! (e.g. http://en.wikipedia.org/wiki/Egbert_B._Gebstadter)

Although GEB is, IMHO, his best work, Metamagical Themas is, although a compilation of previous Scientific American stuff, absolutely brilliant!
Yeah, that's on the Brad Feld's blog. But not on the submitted post, unfortunately.
VaporX Extreme – N2Vape
By publishing on Cydia (and probably other markets) that require a jailbroken device.
Smoking is losing a lot of its social acceptance lately and for alcohol, well, I think we all know what happened during the years it lost its acceptance.
Smoking vs vaping
The essence fort developers:

> For developers hosting their add-ons on AMO, this means that they will have to either test on Developer Edition, Nightly, or one of the unbranded builds. The rest of the submission and review process will remain unchanged, except that extensions will be automatically signed once they pass review.

> For other developers, this is a larger change. For testing development versions, they’ll have the same options available as AMO add-on developers. For release versions, however, we’re introducing the required step of uploading the extension file to AMO for signing. For most cases, this step will be automatic, but in cases where the extension doesn’t pass these tests, there will be the option to request a manual code review.

> In the case of developers who want their extensions to be side loaded (installed via an application installer rather than using the usual Web install method) the review bar will be higher, equal to fully reviewed add-ons on AMO (with the exception of AMO content restrictions). This is a convenient installation avenue for software that comes bundled with an extension, for example an antivirus application that includes a Firefox extension that interacts with it.
Are Your Development Defenses Dangerous?
I keep hearing the stats are switched in NYC and even hear from women (and dating articles) that the roles are switched more often because there are less guys than women.

Don't like the comment about discerning and knowing that their "usual tricks won't work". Don't be with those women, don't be with those those men. If you're looking for an actual partner instead of having a one nighter I would advise not being with people that play these games. If they're playing tricks with this aspect of their life, how are they going to act in more critical situations?
Please do my Homework
If I were a judge, I hopefully would realize that this was about more than the specific implications of the present program. This is question of who can make claims to who. If the Executive can say to the Judiciary, "This will hurt people." I (as a judge) should have the power to say, "I don't trust you, so let's hear arguments from another point of view."

Trust is something a balanced and representative government should not rely on. The ruling in this case is an acquiescence of power from the Judiciary to the Executive.
Yeah, because you should chose your software based on your dislike for some community members, not because of real technical facts.
They're not apps, they're bookmarks. In safari it's when you select "Add to homescreen." They launch as an isolated Safari in fullscreen mode. A good example is http://forecast.io
I don't think the Hopkins founder is a great example here. He did have some impressive accomplishments, but at least according to this article [1], you couldn't call him functional in the same way a daily coffee or wine drinker is functional. A modern-day Halsted would be fired from any hospital, even if cocaine and recreational morphine were legal.

I know there's more to your argument than "Halsted did it so it must be ok", but I think this is a useful point.

[1]: http://www.nytimes.com/2010/04/27/health/27zuger.html?_r=0
China… We need to talk
Here's an article about "speed matters" for those that don't think latency is important.

http://blog.codinghorror.com/speed-still-matters/
Latest Debian netinstall if I do use Linux.
This is a great project indeed. However, as many here have already pointed out, there are many limitations to this approach, SEO and lack of ctrl+f for example.

Which reminds me of flash. Most flash controls had similar drawbacks. I think web development shouldn't repeat that mistake (again).

It also reminds me that Google Docs took similar approach. As far as I remember they use a lot of canvas with a bit of DOM intertwined where necessary.
At Transcriptic we perform experiments using what we call a workcell - a set of devices like liquid handlers (automated pipettors), PCR machines, and plate readers all linked together via a common interface and a robotic arm that moves containers between devices. That interface understands Autoprotocol and executes the instructions accordingly. Autoprotocol itself was designed to be an agreed upon standard for different types of laboratory automation (not just ours) to execute protocols.

An example of an experiment someone could run through our cloud laboratory interface would be to monitor the growth rate of bacteria expressing different genes. This would be done using a protocol that contains some pipetting steps to dilute the bacteria and then alternates between incubating the plate at 37 degrees and reading OD600 of its wells using a plate reader at a specified interval for a certain number of repetitions.
I like this article. I was good at the crazy multi threaded stuff at uni. Now I find I have a lot to learn about making real life products. 3 Years in and I have to admit attention to detail and simple yet robust solutions are more important than understanding the latest and greatest way of doing things.
Tinychart – simple, ready-to-go charts
Any Haggis to go along with it?
Hacker News isn't really a good place to post code, but here's an excerpt of the boilerplate required in Rust code that reads XML to pass I/O, HTTP, and XML parsing errors upward. This, according to the reference above on the new style of error handling, is now the official right way to do it.[1] Works fine. You get to repeat all this each time you define a new result type with possible lower level errors. What's wrong with this picture?

//
// Return type and its error handling
//
pub type FeedResult<T> = Result<T, FeedError>;

/// A set of errors that can occur handling RSS or Atom feeds.
#[derive(Debug, PartialEq, Clone)] // crank out default functions
pub enum FeedError {
/// Error detected at the I/O level
FeedIoError(IoError),
/// Error detected at the HTTP level
FeedHTTPError(hyper::HttpError),
/// Error detected at the XML parsing level
FeedXMLParseError(xml::BuilderError),
/// XML, but feed type not recognized,
FeedUnknownFeedTypeError,
/// Required feed field missing or invalid
FeedFieldError(String),
/// Got an HTML page instead of an XML page
FeedWasHTMLError(String)
}
//
// Encapsulate errors from each of the lower level error types
//
impl error::FromError<hyper::HttpError> for FeedError {
fn from_error(err: hyper::HttpError) -> FeedError {
FeedError::FeedHTTPError(err)
}
}
impl error::FromError<old_io::IoError> for FeedError {
fn from_error(err: IoError) -> FeedError {
FeedError::FeedIoError(err)
}
}
impl error::FromError<xml::BuilderError> for FeedError {
fn from_error(err: xml::BuilderError) -> FeedError {
FeedError::FeedXMLParseError(err)
}
}

impl fmt::Display for FeedError {
fn fmt(&self, f: &mut fmt::Formatter) -> fmt::Result {
match self {
&FeedError::FeedIoError(ref xerr) => xerr.fmt(f), // I/O error
&FeedError::FeedHTTPError(ref xerr) => xerr.fmt(f), // HTTP error
&FeedError::FeedXMLParseError(ref xerr) => xerr.fmt(f), // XML parse error
&FeedError::FeedUnknownFeedTypeError => write!(f, "Unknown feed type."),
&FeedError::FeedFieldError(ref s) => write!(f, "Required field \"{}\" missing from RSS/Atom feed.", s),
&FeedError::FeedWasHTMLError(ref s) => write!(f, "Expected an RSS/ATOM feed but received a web page \"{}\".", s)
//_(ref xerr) => xerr.fmt(f) // would be convenient, but not allowed in Rust.
}
}
}

[1] http://lucumr.pocoo.org/2014/11/6/error-handling-in-rust/
Does not sound like a terrific strategy to me.
It probably will become very hard to bolt the requirements on after you've finished your product.
And for people here in Germany, the pebble missing CE seals was a great deal as the shipped products got lost in customs.
Pretty easy to piss off your backers like that.
I like the simple interface here...but what I find surprising is that for this single-page app, the Javascript (http://tinychart.co/bundle.prod.js) is a whopping 18k lines of code! I'm not a Javascript developer (yet) - is this normal?! Seems an order of magnitude more than I would have expected...
Terraform is the odd one out; it's an "infrastructure as code" tool, like Amazon CloudFormation but with pluggable providers.
An article about a LIDAR, without calling it a LIDAR. How quaint!
> you're gonna wish you spent a bit more time at the starting line wondering what to build it out of.

Sure, but usually spending a bit more time at the starting line (or rather "much more time" or "all the time in the world, until there's no time left and you still have to use the duct tape version, now in an even bigger hurry") won't help you find the problem spots. Hindsight bias is very well and alive and usually all the "yeah, we should have thought about that before" remarks are just that. You wouldn't have thought about it before, because you need the scars to tell you "Bad idea, don't do it again."
This Human Rights Group Is a Model for How the U.S. Can End Slave Labor