skysight-inc/HackerNews huggingface dataset:
if you have other apple devices, i'd suggest sticking with macs to take advantage of icloud et. al. otherwise it doesn't really matter which one you choose.
The Tech Community Must Invest More In San Francisco
There have been numerous topics on "I need an idea" so I suggest you to use the search bar at the bottom and to others to NOT dog feed him links to essays et cetera. :-)
I Wanna Be Famous - About Us
I don't like that this thread is fast turning into a reddit style witch-hunt.
This is not a "I need an idea". There are plenty of ideas to use. The question is: Why did you pick that specific idea?
Thinkpad without a doubt!
I use vim for over 10 years now, I think. Every time I read an article like this about vim, I discover new stuff I didn't already know. Like commands or plugins that make my life easier. It's amazing.
Pretty cool for in process, lots of people doing this now but across services using web services/rest or message queueing. nice to have an in proc option but the comment wrapper seems it will be hard to debug? Definitely an interesting direction and something to play with.
Thanks alot. Works on WIn8
I'm sure there is! Just don't host it in the cloud...!

Edit: I think I accidentally hit the down arrow instead of the up arrow! Apologies!
I'm probably going to be one of many who will say that you should pick a pain you're already having and try to solve it. It's the only way you'll know exactly what to build and how to build it.

The more you try this the easier it will become, and after a few failed attempts you'll know how to get from the "new idea" to a finished product. Yes failed attemps, it'll probably take a while until you learn which things are worth building and which aren't.

Don't be afraid to be very specific. Pick a niche problem, don't try to build a solution that fits everyone. Just go after one specific use case and do it right.

You can try solving someone else's problem, or a problem you see in the company you work for, or a problem your customers are having. But be sure to understand the pain you're trying to solve, feel the pain, you need to know why are you building this thing. Don't just do it because it is cool, do it for a reason.
It's available in Debian's sid/non-free repositories, so yes.
Then rephrase the thread title and text...
I set my version up with a -f on the unmark rm so that I don't need to be prompted to remove it. Also added some basic completion for both jump and unmark

export MARKPATH=$HOME/.marks
function jump {
cd -P $MARKPATH/$1 2>/dev/null || echo "No such mark: $1"
}
function mark {
mkdir -p $MARKPATH; ln -s $(pwd) $MARKPATH/$1
}
function unmark {
rm -if $MARKPATH/$1
}
function marks {
ls -l $MARKPATH | sed 's/ / /g' | cut -d' ' -f9- | sed 's/ -/\t-/g' && echo
}

_completemarks() {
local curw=${COMP_WORDS[COMP_CWORD]}
local wordlist=$(find $MARKPATH -type l -printf "%f\n")
COMPREPLY=($(compgen -W '${wordlist[@]}' -- "$curw"))
return 0
}

complete -F _completemarks jump unmark
Honestly though, how do you start when you don't have any idea what to do?
> This is mostly because people try to treat higher order functional code as in fact just a fancy syntax. Writing higher-order functional code (code that creates, consumes, and modifies functions) requires a set of alternative disciplines that most people in our industry not only don't learn, but actively despise and in many cases mock.

Well it's a hell of a lot harder to write a good verb than it is to write a good noun. Similarly, writing good adverbs is nearly impossible (how many books on Lisp macros do you know of?). If I had to teach my Mom to code, I wouldn't teach her how to zip, fold, map & reduce lists-of-lists on the fly, I'd teach her the FullName noun.

Callbacks are just gotos that return. They can also pass along non-global context, like error information. It's a subtle distinction, and to be up in arms about it is indeed strange.

The industry moves slowly because they can afford to. A few million dollars can feed a hundred developers. The codebases get so large, the teams so big, that lowest-common-denominator kind of code will always prevail. Remember what I was going to teach my mom? Not lisp macros, no. Simple nouns, simple mechanisms.
Here's a variant I used successfully to deal with a complex project that was in danger of ratholing. The concept is "Tabata for work", if you're familiar with the Tabata principles, but it's basically just pomodoro with a twist.

PDF: http://library.crossfit.com/free/pdf/39_05_Tabata_My_Job.pdf

Instead of, say, 20-minutes-on-5-minutes-off-20-minutes-on the same work, the idea is to divvy up a series of tasks and work on each of them for one Tabata sprint. Ten minutes, with five minutes to enjoy yourself between tasks.

Over two hours, you cover eight separate tasks. It's also really surprising what you can get done in ten minutes; send a certain set of emails, review a document, re-work a spreadsheet, test an app. I would not recommend it for coding, for obvious reasons, but if you are in more of a product management role where you are juggling cats and need a structured system to help you deal with all the cats, this definitely worked for me.

It also helped with prioritisation because after spending 10 minutes on each sub-project, it was easy to see what would need more attention that day and have a better idea of how long it would take. The only drawback is that sometimes I really did need a little more than ten minutes (I experimented with some 20 minute blocks, but interruptions became more of an issue).
As I understand his description of the area mapping algorithm, this is actually a bilinear interpolation from the resulting, rotated, image over the original image.
I think you missed the "going out of their way" part.

Can you imagine a tribesman thinking, "man, I should work extra hard today and bring home more meat so I can afford that necklace the other guy has"?
http://paulgraham.com/startupideas.html

...
I'm fairly sure this is his twitter: https://twitter.com/ANDYJBEASTMODE

So, I guess it shouldn't be shocking that this former media studies major is not what we'd call a genius. The twitter account includes references to studying at Berkeley, supporting the Giants, Chicago, sharing Groupons, using MDMA, and smoking pot.

I wonder how long before Andy Johnston renames / deletes this account too, as part of his futile attempt at a cover up.
Great idea! Thank you so much. Now let's create some problems.
Starting, every day, is a skill worth mastering.... And when you start everyday you will eventually become a master: "Quality is a Habit not an Act."

The best sentence in this post happens to also be the last one.
Working suspend and resume was always the deal breaker for me and caused me to switch over to OpenBSD on my laptop.
Is this just a paid blog post for PG&E?

My power costs 3x what it did in Virginia because of tiered pricing based on square footage. That's all that keeps my power usage in check
I think that a lot of the cost savings from open source projects are probably captured towards the top of the food chain, so I wouldn't necessarily see it as altruism in the "helping the poor and downtrodden" sense.

That is unless you specifically choose projects with the view to helping those in your community, and whether you choose your community to be fellow developers or other people sharing your geographic space.
You mathematicians, with your... understanding of the basic mathematics behind things we developers already use every day, you all think you're better than us, don't you? DON'T YOU?!

Can't I just be left to be impressed by a direct use of the math behind a crappy textbook random number generator in peace?

-.-
Reshaping New York
Hire a Lobbyist to Help Defund the NSA
HN, reddit, digg et al. would have failed long long ago if half the websites required a login before you could see the linked content. I see no good reason to make an exception for just one particular website.
The funny part of this is that if you look at his list of reviewed places he has a bunch from Chicago, IL, then the 2 for the 2 locations of Sauce in SF, then another place in Chicago on the SAME DAY.

Now I know that you could wait to review places, but that certainly seems like a suspicious line. Also 2 of the 3 total reviews he's ever given a 1 star rating to are Sauce (out of 71 total reviews).
Right, of course.

It can get really hard to tell where the line is, though. For example, multiple for-pay third-party clients for Google Music now exist [0]. Personally, I think this is still a value-add for Google, but I could understand why some would think it's exploitative.

Another thought experiment: say the unofficial use of the platform originally required a fair amount of reverse engineering. Can the person who figured it out be held responsible for other's abusive behavior?

[0] https://itunes.apple.com/us/app/gomusic/id457883228
Dang, they actually ARE carrying with that threat and giving them bad reviews? That's so messed up. I didn't think that'd actually happen. Hope this gets quelled quickly,but I'm bringing the popcorn and the lawnchair just in case.
It is production ready, and many people are using it, but as with any deep stack technology, growth is a slow process. From an engineering standpoint, I'd say the data structure wasn't fully mature (ready to replace nearly all uses of InnoDB) until probably the end of 2012. Most of this was issues with concurrency that we methodically picked apart from the 5.0 release through 6.6.

A few users still point out annoyances here and there (like the location of files on disk, how certain metadata is presented at the MySQL level, dealing with corner cases in the query optimizer) that don't have to do with the data structure, but with the integration as a MySQL concept, and though these complaints are rare, they will eventually need to be addressed, and it's hard to find the manpower to address them immediately.

Part of this problem is that it just takes a long time to sand down all the rough little edges of a product, even though the core data structure is mature. Another part is educating people, changing expectations (for example, teaching people that unique indexes do have a higher cost than non-unique indexes), and generating better documentation. It's a slow process but we're confident that it's progressing and will continue. Recall that InnoDB, while broadly accepted as superior to MyISAM for many years before, only became the actual default engine in MySQL 5.5.
Please inform the people in power about this.
Depends on the site. Talk to Steve Jackson. Or Aaron Swartz (better hire a psychic, he's dead). Or Weev.

And if you think that private companies and/or web sites didn't play a huge role in any of the above cases ... well, you and I inhabit different universes.

As others have pointed out: private companies can collect and/or process information that governments uses. They're also susceptible to hacking by government or rogue agents: Google, Yahoo, Microsoft, and Apple have all been targeted by Chinese government-related hackers (mostly looking for Faulun Gong and Tibetian activists).

Other companies such as Cisco simply hand over the tools authoritarian states request.
You can load some of the lenovos up with 32gb of ram from their website @ 2k USD.
Good idea, but you shouldn't overwrite ctrl-O, which is a wildly useful function in bash: run current command in history and retrieve the next. If you want to re-run a sequence of several history commands, you can find the first in history (such as via ctrl-R reverse-isearch), then repeatedly hit ctrl-O to run it and retrieve the next command from history.
That is correct. Do Not Call (the USA law) does not apply to businesses.

We found a great remedy: answer their calls with a soundboard. We like the Mr. Rogers soundboard [1]. Its fun, harmless, and they'll stop calling very quickly.

[1] http://www.ebaumsworld.com/soundboards/play/1866/ (warning, autoplays some sounds)
I now realize I didn't answer how we check uniqueness. We just do a query like any other normal point query, using a serializable transaction, and if we pass the check, then we do the insert with the same transaction (which took a row lock when we did the query because it was serializable, so nothing could have violated the uniqueness between the query and the insert).
Young programmers: please don't buy into this mindset. It's one of the many ways to find yourself exploited in this industry.

Contributing to Open Source is a good thing, but only do it if you're getting some benefit from it. Does spending your time writing code for other people give you some business advantage? Help establish your reputation? Pay you cash money? Tickle your creativity and make you happy? Cool, then go for it.

But think twice before spending your time patching somebody else's thing for free. Chances are they are getting one of those tangible benefits from it, and if you're not, well, what does that make you?

Notice that many of those big, altruistic Open Source projects that made the world a better place also made the world a better place for their corporate sponsors in very specific and well thought out ways [1]. There's not that much real charity to be found, even though it would make a better story if there were.

Notice further that all those upsides listed above can also be had from developing your own for-profit, possibly closed source software products or working for somebody else doing so. If whatever you're doing isn't getting you further ahead than that, it's your duty to yourself to fix that.

[1] http://www.joelonsoftware.com/articles/StrategyLetterV.html
He's not saying "Use Groupon or I'll trash your business" he's saying "You treated me poorly and now I'll get my revenge" This guy's a goofball for putting it in writing but social media has definitely changed how businesses have to treat whacky, unreasonable prospect's and customers. (The Groupon angle is a red herring)
Met deze gezonde voeding terug naar school | Leef Nu Gezonder | Leef Nu Gezonder
The EFF publishes a Surveillance Self-Defense resource I'd strongly recommend. The tools page: https://ssd.eff.org/tech

Essentially: encryption, self-hosting, small-scale hosting (the NSA have scaling problems with vendors, though don't expect that to last), privacy tools including browser privacy (privoxy), tor, VPNs, the FreedomBox, and others.
That's true but what a huge PR blow, plus they hired the guy in the first place. This could get ugly if something isn't done right away.
Lets see, in the 2nd edition of code complete, section 7.4 "How Long Can a Routine Be?" has a bunch of studies listed. Lets take a look:

1. A study by Basili and Perricone found that routine size was inversely correlated with errors; as the size of routines increased (up to 200 LOC), the number of errors per LOC decreased (1984).

2. Another study found that routine size was not correlated with errors, even though structural complexity and amount of data were correlated with errors (Shen et al. 1985)

3. A 1986 study found that small routines (32 LOC or fewer) were not correlated with lower cost or fault rate (Card, Church, and Agresti 1986; Card and Glass 1990). The evidence suggested that larger routines (65 LOC or more) were cheaper to develop per LOC.

4. An empirical study of 450 routines found that small routines (those with fewer than 143 source statements, including comments) had 23% more errors per LOC than larger routines (Selby and Basili 1991).

5. A study of upper-level computer-science students found that students' comprehension of a program that was super-modularized into routines about 10 lines long was no better than their comprehension of a program that had no routines at all (Conte, Dunsmore, and Shen 1986). When the program was broken into routines of moderate length (about 25 lines), however, students scored 65% better on a test of comprehension.

6. A recent [sic!] study found that code needed to be changed least when routines averaged 100 to 150 LOC (Lind and Vairavan 1989).

7. In a study of the code for IBM's OS/360 operating system and other systems, the most error-prone routines were those that were larger than 500 LOC. Beyond 500 lines, the error rate tended to be proportional to the size of the routine (Jones 1986a).

8. An empirical study of a 148 KLOC program found that routines with fewer than 143 source statements were 2.4 times less expensive to fix than larger routines (Selby and Basili 1991).

The 25 lines is just one of the studies, related to students of CS in particular. In general, it seems like the data indicates that somewhere between 100 and 200 is optimal for minimum errors per line, lowest cost to modify, less need to modify, and overall undesirability. So the "short, 5-10 line functions" seems to be not only entirely unsupported by empirical data, but actually harmful in general.
Even if I'm a proponent of reducing paper usage and planting new trees, I can think of some cases where keeping some printed paper documents could still have some benefits even nowadays, IMHO.

* You need to travel in some places with no good access to internet or power source (as in a far far away country, or as in a local subway/underground of ill repute after 9pm),

* You thought it would be nice to delete all your original printed copies after using a JGIB2 scanner,

* You don't have the hardware or software to read your old digital copies,

* Some obtuse administration refuse your digital copies,

* Some benevolent but overly attached agencies, or some malevolent people, are trampling with your data in the cloud,

* A Carrington-class events occurs for real,

* And so on ...

but luckily, all of this never ever happen, right ? ;-)

As for the OP printer design it seems great, but when I see the 2 meters stack of paper in the illustration, I can't help but think that the printer will ran out of battery or ink before the middle of the stack.
Emojify turns your photo pixels into Emoji icons
You don't have much experience, then.
Rails.app first prerelease
Technically you can have a format which is literally defined in such a way that not all inputs can be perfectly represented. On example is mobile phone audio, it is defined to operate at a particular bit rate, which is less than that required to represent all possible speech signals.

However, you are right that 'lossy' is usually used to describe its intended use rather than its actual formal limit. For example, you can (probably!) non-lossily encode an image as a jpeg, but it won't be as good a compression ratio as you would get from a format which was specifically designed for use with lossless compression. It might even cause the file to get bigger.
Does that act that's being threatened have to itself be illegal in order for the threat to qualify as extortion? Yelp reviews aren't illegal.
Why the downvoted? I think the travel industry would benefit froma groupon like service.
To be fair, it doesn't look like they are doing much. Rather this Andy Johnston guy is going on a rampage to exact revenge for a perceived personal slight.

I'd imagine Andy's actions expose his employer to many liabilities, but there's no indication that Groupon condones these actions thus far.
I didn't say PNG did anything, so I'm neither correct nor incorrect about what PNG does (though on second read compressing is a better word than omitting, though either way the "guessed" pixel is where the information goes missing). I'm disputing parent's claim author said savings was from blur. He didn't. He said:

> PNG has an ability to “guess” pixels based on their top and left neighbors and successful guesses compress to almost nothing. Usually only few pixels match a guess, but latest ImageAlpha's “Blurizer” option manipulates image data to match the guesses, making compression much much more effective.
Consider an extremely simple codec that uses only (lossless) run-length encoding [1]. You have an image of a blue sky with a few white clouds. One of the rows might have pixels Blue-Blue-Blue-Blue-White-White. This would be encoded as 4Blue-2White. The amount of information is the same, but you've removed redundancy (this is more or less how fax machines work).

A lossy codec would take advantage of limits in human perception and encode LightBlue-MediumBlue-DarkBlue as 2LightBlue-DarkBlue. On a large enough image, you wouldn't notice the difference.

[1] https://en.wikipedia.org/wiki/Run-length_encoding
On my primary platform (common lisp) when printed it looks like a large set of nested structures made up of "terms" (ie "create_database", "table", "function", etc) and datums (array, float, kv pair, etc).

It's easy to pretty-print and get a view of the entire query structure before it's shipped off the the protocol buffer serializer. That's lisp though, and the print methods for the protobuf objects are built into the protobuf library. It's really going to depend on your language, probably.

The nice thing about the query language is that the mapping between what you send the driver and what the driver sends to the server is pretty much 1:1, so what you see in front of you is the printed query (save for bugs in the driver).
I would recommend The Lean Startup by Eric Reis. I wouldn't want to try and generalize the book, but essentially you propose a hypothesis, and then test your hypothesis using a Build/Measure/Learn feedback loop. This creates an environment that trains you to validate your ideas/approach, which in turn facilitates the most effective use of your (and your team’s) time and resources. Anyway, getting back to your question, I would do both concurrently and use the feedback from your customers to validate the features / functionality you build into your MVP.
This reminded me to look up the naked eye comet predicted for the end of the year.

Sadly http://en.wikipedia.org/wiki/C/2012_S1 says that expectations have substantially dimmed for it (pun intended), though it should still be a good thing to look for.
And the links to the preceding discussions:

https://www.hnsearch.com/search#request/all&q=starbucks+two+...
Artificial Intelligence and What Computers Still Don't Understand
Ok, so I should have put more effort into this submission, but it was early on a Saturday morning and I was just a bit annoyed with all the chatter about callbacks & their failings. Also people spend a lot of time bemoaning the lack of new ideas or research and I was just making the point that new ideas are being explored and research is being undertaken all of the time, but is largely ignored :)

I guess I'll write a blog post about it and write it in a more "hacker news friendly" format and then submit it again.

But just to answer your questions, yes I've implemented this fully in 2 different languages, C https://github.com/reillyse/C-AESOP and Java https://github.com/reillyse/J-AESOP and partially in Javascript https://github.com/reillyse/alacrity .

The focus of the research was for sensor driven applications so I didn't do the partial implementation in JS until later on.
I used it in two applications as part of the evaluation section of my thesis. So, dog food well and truly eaten.