skysight-inc/HackerNews huggingface dataset:
I took it as a vaguely racist comment on how a non English speaker might say it. I must be overly sensative.
I have the same issue now. I have a win7 pc at client's office, mac book air for personal use and mac book pro at work.
Since I use emacs a lot, I symlinked my dot emacs file to my dropbox file and kept all my custom packages there. (~/Dropbox/...)
By the time you spend the effort you sync everything up, you'll find it easier just to duplicate the key things you miss.
Also using one PC most of time helps the "oh its on my other pc" moment.
Surface vs Ipad - Why you should go for an Ipad
I've never worked in a business where there was a social stratification between specialists in the manner that was outlined in the blog that was linked to.

Deep specialization in one area with a narrow, but broad enough knowledge of other areas seems to be the norm to me now...and when I started working over a decade ago.
Nice! Can you please share where you got the data etc. for the visualization? More info on how you did this would be great too (if you can..)
Show HN: Wishberg: Born in Mumbai. Launched in Bangalore. Made for the World.
We've opened Wishberg (www.wishberg.com) in public beta today. Currently allowing users to share/discover wishes, reviews and experiences in their social graph.

Aim is to build social graph for product and purchase intents. Localized information for 200+ cities across 12 countries.

Appreciate reviews / feedback and suggestions. Please share on this forum or drop a note on pj(at)beingpractical.com
The problem with this is that everyone uses Yelp and nobody but hipsters uses foursquare. I'm fact even hipsters have moved on from foursquare. Without liquidity of use any ratings system will just be so sparse as to be anecdotal.

I don't see a problem wit yelp, reading only a star rating isn't a good way to make it useful, you have to speed read and sample the reviews. At a glance I can tell a reviewer who's fake, or one of the many that just like to hear the sound of their own voice, or they are just an opinionated asshole. But when you speed read a few comments you can pick up general trends. For example if many reviewers all say a hotel was noisy there might be something in it. Ditto for amazon. The "solution" that some have tried is to rate the rating, then use a pagerank-link algorithm to module the effect any one rater on the rating. In other words, if many people who themselves have been rated at rating highly accurately, then my influence on a rating is higher.

The suggestions I have seen here (mainly collaborative filtering) may be of merit, if that's have foursquare plan to do it then with more of a representative sampling of users and maybe it will work well. Currently though they would need a lot more users.

But personally I find yelp very useful, it just requires more effort than glancing at the star rating.
Breaks when you don't have enough content in the body, footer gets all messed up, reproduce by just removing a few rows from the content area.
This. NDT's saying that leaders are a product of their base. If you want better leaders, do something to change the minds of the people who elect them.
I'd love to know the answer to this too! Harjeet put in a brief reply on Quora: http://www.quora.com/Y-Combinator/Do-all-YC-partners-read-ea...

Lots of answers on the YC board there in fact.
Did they get lazy or do they not want people to actually redeem free content easily? It's a bit of a pain to mash all those random characters, not to mention the fact that the redeem button is all the way at the bottom of the app.
Well, I'll be the devil's advocate. What about Adam Smith? He noted that division of labor in a factory will increase its productivity and make the workers much more effective. While a software company is not entirely comparable to a factory, why does the same principle not apply? Devs who can concentrate on one part of the stack can become experts in that area, increasing their productivity--and consequently increasing the productivity of the company.
Really? What have you been doing?
The hacking has raised questions about whether South Carolina was unprotected or simply unlucky. Most of the stolen credit cards were encrypted, but the Social Security numbers were not. The computer system that was hacked [did not have a free layer of security monitoring] offered to all South Carolina agencies, according to the State Budget and Control Board.

-- interesting detail
As someone who hit that (perceived small but really large milestone) at 40, only last year, good luck, well done and keep on going.

Don't want to sound patronising or empty, but that's great - keep going
It's based on "thread" meaning "execution channel" which is usually core or, in the case of Hyper-Thread, a portion of a core.
The difference is that in this case the project leader really is John Videogames, or close enough.
but it would be super HARD to do both well

communication between developers is most important!
Adam Smith was pre-industrial revolution. He had no idea how far this would go. But he probably understood diminishing returns or hidden costs.
New Heroku Add-Ons Marketplace
Maybe Foursquare peaked in the Bay Area in 2009, but as a user since 2010 in Toronto, I can safely say that 4sq has been consistently trending upward since I got it. I think the same is true of every city in the world that isn't SF or NY.
No. With better communication comes the opportunities to specialize even further as the market grow.
The following quote comes to mind:

"In a democracy people get the leaders they deserve." -Joseph de Maistre
I disagree actually. I think having a specialization (front-end vs. back-end for example) is a good thing. It allows someone to dedicate themselves to one specific area and learn it thoroughly. When I'm doing back-end development, I love having a front-end guy who can make it look pretty - I don't want to have to use time/energy up doing that when I'm concentrating on making a secure, fast, maintainable back-end.

However, there is a limit to this. A back-end guy should still have some idea what goes on front-end and vice-versa. So, the key is to be an expert at what you're best at, but not to be a dummy at what you're not as good at.

[On a side note, I don't see why specialization should create contempt. In my opinion, it should breed appreciation]
The author provides neither evidence nor any logical argument for any of his claims.

He says "You must do both or you'll be irrelevant."

But there are plenty of examples of people doing cool stuff that is specialized.
Also, I think working only on backend or only or frontend is kinda boring. I like to tackle the whole thing.
Create a fuctional sliding panel menu using jQuery and CSS3
MBA Mondays: One Last Thing About Sustainability
What you said:

"When I'm doing back-end development, I love having a front-end guy who can make it look pretty"

How that sounds to me:

"When I'm done with a hard day's work, I love having a wife at home who can make me a drink"

Seriously! Read what you wrote.
Why does his level of education impact on this? He has made several intelligent and important people in New Zealand look rather stupid - so at a bare minimum he plays a shrewd political game.
Ditto with Dev vs QA.

Ditto with Dev vs BA.

Ditto with Dev vs DBA.

Looks like the recurring theme here is Dev vs X
Categorization is subjective. Both of those categories are so expansive that you could spend lifetimes learning to be better and never fully mastering them. The problem isn't camp A thinks they're hard shit and looks down on camp B, it's that young programmers / engineers think they're hot shit when they have a lot more to learn. Choosing a specialization is hardly ever a bad strategy, but it's important to keep prospective and be able to learn / play other roles.
I just downloaded the sample app. Neat stuff.

Is caps-lock toggling the only way to use it in the paid app, or does the menu item turn it on and off? Do numbers and other coding-symbols get chorded in the main app? Also, is there any research into how long it takes to go from Dvorak to this sort of style?
Hehehe, that's a good one. But we both know what he meant :)
AMD's Bold ARM Server Gambit
Yes, and you also got that nice Strauss music when the computer was enabled.

It was a bad idea to activate it on the wrong side of the station though ..
It depends on how much/far you travel. Sometimes you luck out and find a free outlet at an airport, but not always.
A Tent.io server in Node.js would be amazing ... then you could build the interface with http://meteor.com/ . We are creating an open elearning app for kids
http://one.ie/about/foundation with tent.io . It seems like tent.io, node.js and meteor are a perfect fit.
if the videos are unlisted, randoms will be unable to find them
this is really...safe (and boring). there are a myriad of more interesting ways mobile photos could be arranged and displayed. perhaps geo-tagged? people? instead a grid. temporally arranged. that looks like my fb profile. yawn.
I kind of get the feeling they just don't want to give things away.
When I'm doing front-end development, I love having a back-end guy who can flip the switch and turn it on.
And the author is also wrong, because he thinks that all software is made up of a frontend and a backend.

Unless, of course, by "our profession" he means "us, the people who can only code web apps"
I think everyone of us should try and specialize in at least one thing. That does not imply that you do your best to know nothing about relevant fields. For example if you are a web developer who works on Ruby on Rails and makes awesome web apps but don't like working on the front‒end, i.e HTML/CSS/JS then that is OK as long as you have some basic knowledge about those technologies and respect those who do work in that area.

Back to the specialization, I really think you should have at least one area in your chosen field where you have deep knowledge. How deep? On the above example - maybe you know internals of Rails + Rack very well. If you are on the front‒end may be you should have a thorough understanding of how browsers work, how HTML/CSS is parsed and rendered etc. I don't really have a good explanation as to why this is important but I've noticed that the really good web developers or designers tend to have at least one specialization or deep interest within their fields.
I don't see what is wrong with having interest in one area say back end, having done it most of the time during your experience and hence have more relevant material on your profile. But still being open and able to do front end when needed. However, clearly lack enough exposure or substance on paper for that. To me it is the resistance to do any thing different from previous experience that is the culprit. Not the basic classification
Nice looking theme, but kinda looks like an imitation of another looking theme released 2 months ago: http://wrapbootstrap.com/preview/WB0F35928
Good luck being a decent front-end and a decent back-end developer.

Besides their different nature. The volume and amount of knowledge is too much to be able to do both at a decent level unless you sacrifice your personal life or you are some sort of super talented nerd.

If you dedicate 24 hours a day to both, there will always be someone who will dedicate theirs to only one. You can't beat that competition and it is only going to get worse from here as the technology develops and both of these streams will become more sophisticated and require more knowledge and experience.

Yes, back in 1980s a programmer could easily do both because front-end wasn't much more than some simple html tags. But not now.

Front-end and back-end go hand in hand and it is good to familiarise yourself with which ever you don't specialise in and recognise and appreciate its importance but if you try being both you'll most probably end up being a half-arsed back-end developer and a half-arsed front-end developer.
You cannot have everybody do full stack development and devops and [insert whatever specialization you have here]. I know great programmers that got stuck in another specialty (because my company tried to create such broad specialization employees) and left, because they were only interested in a field, like backend programming or mobile. But they never said "I don't want to do sysop because it's not hot", they said "I don't want to do sysop because it's not my job".

I'm a programmer that now trains as a DBA+sysop and I like it. I saw condescending (brogrammer style "I'm way cooler than you") types in both camps, but usually from the guys that never tried to understand somebody else('s job). For my colleagues I tried to create small presentations like "this is what a DBA can do to help you and this is the way you can help them" and "what an usual programmer knows about databases" to bring the camps closer together and to understand eachother.
You sound like you're unfamiliar with public transport?

The way trains usually work nowadays is that you open a website, enter from where to where you want to go, and when you want to arrive, push the "pay" button, and print out the resulting page (which contains your schedule, sometimes a backup schedule, and a QR code that works as your ticket). Then, you just follow the schedule.

There's absolutely no need to know any map or lingo or network.

The main point I'm making is that, for most people, computers are appliances. I use my stove, but I'm not a cook. I'm not a "stove technician", either. I just know that I need to heat stuff at a certain level for a certain amount of time, and I only have to turn a simple knob to achieve that.

Similarly, most computer users aren't programmers or techs. They just want to write a letter. They should be able to do that without knowing about viruses and SSDs and RAM and OS upgrades and file format incompatibilities.
"The greatest group of political scientists to ever congregate in one place and time" were probably the Athenians that, out of the same conclusions on human nature, concluded that if you want political equality for all, your political system must only allow small, non-renewable and other controlled mandates taken by randomly chosen citizens (yes, they have considered elected but have rejected it). The key point being that those randomly chosen people don't have the power, it the assembly of all the citizens that have the power.

And it's based on that that they have created the first (and only, for some people) democratic system ever. Ironically, the person that have created our current democratic system knew exactly this Athenian system but explicitly rejected it because it was ... democracy, and that is was a system were the people really has the power. It's only since Tocqueville has started to call it democracy that we think about it has democratic, Tocqueville who explicitly said that he wasn't afraid of election because people would vote what we told them to vote, something impossible in the Athenian system.
I think it was just an over all generalization. I wrote my opinion based upon reading this article and i am not even remotely doing a web app for over 7 years. It is mostly embedded / networks / c. Still i didn't feel like he was talking about web apps only. Full stack - front vs back end are standard terms often mentioned in recruiting at all big name companies as well as startups
Wow, that's a b2b type site which is prettier than most consumer sites (and actually useful).
I don't think I understand the analogy? If two people are working on the same project and one enjoys and specializes in front-end development and the other enjoys and specializes in back-end development, and the project is roughly 50/50 front-end and back-end, why on earth should they NOT split up the project accordingly? They will both enjoy working on it more, they will get it done faster, and with better results than if they each took half the front-end and half the back-end work. Neither partner is "exploiting" the other or anything like that (as implied by your analogy); it's just in their mutual interest to divide the work in this way.
Why not use excess energy to lift millions of tons of worthless rock off the ground and then when power source fails, use the winding down via gravity to turn generators?

Gravity is never going away and never going to run out.
Django Sprint in Toulouse, France
YC's Bufferbox is battling back: http://www.blogto.com/city/2012/10/bufferbox_wants_to_put_an...

Now in 7 Eleven's, train stations and Sobey's (grocery stores).
Hm hm hm. Ok.

That must be regional then. Where I'm located (the Netherlands), these terms are very much web app only. Nobody working in embedded systems would call himself a "full stack engineer". Stack? What stack? I make robots move!
To be honest, the absolute smartest Math/CS-types I know (with a few exceptions) went to the United States or the UK for their undergraduate studies and decided to stick around rather than return to Singapore. Start-ups in Singapore probably don't even know they exist.
From the horses mouth, 1:38:30 : http://www.youtube.com/watch?v=Fgn2fhZBAVA&feature=fvsr

Definitely didn't say anything about not having an API going forward.
The Obama campaign in 2008 beat out Apple to win marketer of the year. I can't remember his opponent's symbol. (Do other people remember McCain's symbol (not slogan) off the top of their heads?)

More than likely the designer knows that fact or is generally aware that more people recognize Obama's logo. Not really "political backing." After all, Al Gore is on their board. They don't need to be "subtle" if they want to back Obama. Jobs even sat down for dinner and discussion with newly elected Obama.
This is already being done, by pumping water uphill:
http://en.wikipedia.org/wiki/Pumped-storage_hydroelectricity

I'm sure there are a bunch of interesting tradeoffs between using water or a bunch of rocks though.
Atoms can be linked together to form an arbitrary structure. After all, a tree is a graph.
How about hardware startups in Singapore?
Huh? I think you completely misunderstood the sentiment in my post. I'm saying that not all software as made by a group of front end engineers and a group of backend engineers - that structure is rather specific for web apps, and the occasial internet-heavy mobile app.

If you write software for cars, rockets, printers, cell phones, game consoles, or ATMs, these distinctions hardly apply. To rant about how everybody's either a frontend engineer or a backend engineer, to me, implies that the author's world consists of web apps only.
Over specialization is for insects
So basically just IFF/RIFF with fields exchanged?

See:

http://en.wikipedia.org/wiki/Interchange_File_Format

http://en.wikipedia.org/wiki/Resource_Interchange_File_Format
Exactly. If this is indeed David Braben, all he had to say was "I want to make a game", and I would throw money at him.
Link to said tweet?
The big difference between the QT Atom structure and RIFF is that RIFF is a series of independent chunks (IIRC), whereas Atoms are a big tree. Structurally nearly identical, though.
Sexy as hell. Great job.
Oops.. looks like the script is being blocked :)
VMware ESX Source Code Leaked Online -- Again
I'm another one who writes for a living and writes 100% in Markdown, then convert to HTML for Markdown. I just moved my own site to Kirby so I could publish with straight Markdown files. I know we're far from the only ones that do that.
Nonsense. You just need to have a huge amount of experience which can be gained which takes time.
Nice design. I wish that you focused on one thing - travel, cars, whatever. By doing everything, I'm not sure what to do.

It also feels a little ... lonely? It'd be better if you had some hint of user activity on here.

I was hesitant to sign up fearing that you'd spam my facebook wall, without more context.

Good luck!
As a developer, with a good few years of experience behind me (admittedly in non-startup areas like insurance and equity plans), who's actively looked to move to Singapore I've found it quite hard to find any jobs that didn't fall into either the entry level code monkey (MUST KNOW HTML & XHTML) or the high level investment banking sector.

Really good local talent will probably drift towards the latter and startup's just can't compete with those sort of salaries. I imagine it's the same issue with New York.

As with all good jobs, startup positions are never really advertised openly. And if they are, they're not there for long.
It's true that specialization is good for company, but you have to have right employees for that to work. If forced overspecialization makes your developers bored, they will be less effective at work, thus diminishing the effect of specialization. In addition, your best people will leave out of boredom, or require much better compensation to stay. Luckily for software developers, right now we have a choice to change jobs, and don't have to put up with things that people in most other professions have to.
Over-specialization is the curse of our civilization
Sounds almost like the IFF format, which was used for just about everything on the Amiga, and then later (with minor changes) as the basis to microsoft's RIFF, underlying wave files, .AVI and a lot of other formats.

IFF is: struct chunk { char tag[4]; int32 length; byte data[length]; byte padding[(2-(length%1))%2]; }

The padding is to two bytes; the tag uses ascii exclusively and no space (33-127), although every format I remember uses upper case + digits. The length does not include tag and the length field, not the padding. Microsoft, in a typical "we don't care" move adopted the spec except they specified little endian whereas IFF is originally big endian.

The entire file must be one complete chunk, and is thus limited to 2GB (signed integer length).

This format has been around (and at some point, dominated image storage with it's "ILBM" chunks, as well as other domains) since 1985 at least. https://en.wikipedia.org/wiki/Interchange_File_Format
Rails does not specify the mapping of models to database schema, so it requires specification of migrations instead to document changes to the database that go along with any code changes. So migrations are explicit commands (in a pretty simple dsl) to add columns etc. spread out over many files as the application evolves. This means each schema change requires adding a migration file with those changes in it, rather than modifying a master schema or mapping. There is a schema.rb file but it is created/modified automatically.

There are trade-offs to each approach but it is probably one of the areas that Rails could still improve by looking at other ORMs - I'd prefer to see the schema specified along with constraints etc for each field at the top of each model to make it explicit and self-documenting, and perhaps doing away with migrations altogether.
That sounds totally wrong. As others have pointed out, specialization is the main ingredient in successful division of labor.

Read my variant at http://shezi.posterous.com/over-specialization-is-the-curse-...
Talent is a non-countable collective noun, like money or sugar. Consider "Where has/have all your money gone?" Has is the correct answer, at least by American grammar rules.
Hm. Why not Pointesa?
Microsoft hiring for "Cloud TV" team
I believe that the problem with this is that it's very weak, ie you need to lift a large amount of weight to a great height to store much energy.

More details:
http://physics.ucsd.edu/do-the-math/2011/11/pump-up-the-stor...
Show HN: Total downloads from rubygems.org going to reach 1 billion