skysight-inc/HackerNews huggingface dataset:
The four pieces don't have measure, don't have unambiguous volume. It might help to think of them as fractals (though in fact they're even more ambiguous than that).

The only "realistic" answer I can give is that each of the four pieces would "take up" the full volume of the sphere as you moved them apart. Each of the four pieces is "shaped" like the whole sphere, but with infinitesimally small holes where the other four go. So not a single "water droplet" would ever go inside the four pieces, and while you were moving them around they'd take up the space of four of the original sphere.
In real life there are more possibilities in between 0 and 1..
Also look at how its done in other countries. Apparently americans can go to Germany to study for free in a recent article. Absurd indeed.
Except AFAIK there are zero features in POSIX that came from GNU/Linux.

Now, if anything I do agree that UNIX is stuck on the past by not having any standard workstation environment or adoption of modern kernel architectures.

Also CDE is not what one would expect from a 2015 workstation.
Specifically, shapes with infinitely many "sides" in a bounded region. (a ball)
Yes. Except that the ball can't really "be paritioned". That's a mathematical illusion. There is an isomorphism of structures, but there is no computable algorithm that can perform the partition operation.
Perhaps people with an innovative or entrepreneurial bent don't gravitate to Apple in the first place, even if they love Apple products.
Very much agreed. For one thing, comparing the human brain to a deep neural network leaves out the fact that the human brain mostly performs unsupervised perceptive learning, unsupervised causal induction, and reinforcement learning. None of these resemble the deep backpropagation done in most ML models.
There are two kinds of problems.

The first is "I need to sort this list in Python". The second is the broader application that list is relevant to.

When I'm coding, the first problem is uninteresting. Sorting lists is a solved problem. I just google it and paste in code that does it, and it's done and off my mind. The architecture of the broader application this fits into, though, merits a lot more thought and the broader problems it solves again are worth much more investment.
Lessons about the pilgrims are stock curriculum in every elementary school in the USA, usually timed to lead up to Thanksgiving.
True, and it’s telling that maybe the biggest break-out startup from Apple was Nest. And for that very reason, I’m surprised that there aren’t more creatively stifled Apple hardware engineers pursuing IoT startups.
The expense for markers alone has GOT to be many multiples of that for chalk. And chalk doesn't dry out if a kid leaves the cap off, and isn't really damaged by heavy pressure during use (it does break if dropped, though -- I remember teachers using chalk holders to help prevent this).
I wasn't aware that this little latency could be inconvenient. Thank you for pointing this out. I'll fix it in the next release.
What are you talking about? Pixar didn't come from Apple. It came from folks who left Disney. Then Steve Jobs, as himself - not Apple - invested in Pixar.
Hard-coded into the network layer? Not only is this not true, I can't even imagine how it could be true...
Jewels from an Ethiopian grave reveal 2,000-year-old link to Rome
That's cool, though powershell deals in actual objects which are more powerful than better structured input and output. For example, the objects returned by ps have methods for interacting with them.
What a sharp observation. I had one at http://dreitipps.de (yes, German). when I worked with my colleague of sweetbits at a startup for generation 50plus.
Web Tool – Name Ringtone Mixer
Thank you for getting deeper into this and finding the actual cause of the issue. It will help me to fix it in the next release.
In some ways it can be thought of, "This company is the apotheosis of tech. You can get the full experience of a startup, with the stability of a giant corporation. Why would you want to go anywhere else?"
The Surprising Persuasiveness of a Sticky Note
I guess it could very well be that the mentality of Apple and Google employees could lean somewhat into those philosophies.

On the other hand, your described Apple culture sounds to me a heck of a lot more sustainable in the long run (I mean, Apple has now been around nearly 40 years now), especially since the "become a bazillionaire" part from Google really only works for founders and early employees with enough stock and only for very few selected unicorn companies.
Exactly. Though technically, NeXT is "a startup that Apple spawned", I think?

Also: Be Inc., Palm/Handspring (Donna Dubinsky), General Magic, Eazel.
Micropayments for web/editorial content is a much harder problem. There's no central egress point for this content, it's spread over all the sites and a tracking system needs to be in place (but people hate that) as well as massive scale to touch all those sites and check the usage.

This is something that would need massive cooperation and integration between websites, ad networks and even ISPs to get right. If it was that easy, the industry would've already done it. The fact that Google is on it's second approach with their Contributor program and still not finding any luck is telling. (And Google owns a ridiculous amount of the layers in the modern web so they're probably in the best place to pull this off).
Interesting, I only know one person who works at Apple. She's a copywriter and she says that it's definitely a 60 hour a week job.
I don't think there's much question that this company is harmful to societies and individuals around the world. Does it make sense for people other than shareholders to admire this person?
Re: Eliezer Yudkowsky, also "Three Worlds Collide": http://robinhanson.typepad.com/files/three-worlds-collide.pd...
It sounds like you only have a sample set of developers at one company, perhaps being evaluated through the lens of some personal bitterness. It's possible that you may be simply experiencing a case of an organization that uses bad metrics to reward developers: measuring productivity by LoC is basically an industry joke, but still occurs. Other nearly-as-bad metrics like "tickets closed" are common. It may also be a cultural thing at your particular organization, or a reflection on the particular task. What's the use for this code? What is its expected time-in-service? Is this experimental or production code? Is this boilerplate code for an uninteresting problem long solved? Sometimes a mark of a good developer is to know what to spend valuable time on and what not to (as in the problem of premature optimization.) Finally, it's not necessarily a bad habit to ask someone you know has the answer rather than research it yourself, especially if the problem is unimportant/uninteresting/not your area of expertise.
>I am not sure how many of the commands have been converted

There's a page [1] on the FreeBSD wiki with a list of converted and ongoing conversion. I don't know if the list is complete but the page was last modified 2015-05-22, so it should be fairly up to date i guess.

[1]: https://wiki.freebsd.org/LibXo
> In short: what you do is part of a larger context, you need to align your priorities with that.

Let me just point out that this is the hardest part of being the professional. Reasons for this are many. One example is that larger context can be obscure to you due to bad company organization/management.
That surprised me too. In my schools the chalkboards were erased every night (except for anything marked "save") and the custodians would damp-wipe them every few days for an extra thorough cleaning. I wonder if they deliberately DIDN'T clean them, intentionally creating a sort of impromptu time capsule.
If you're not getting things done, then what problems are you solving?
Similarly I heard about an historian with a strong scientific view on history, he even coined a name for his field, unfortunately I can't remember it for my life.
Uncountable sets are not reality. They
are unicorns. They are a pretend construction that cannot be mapped 1:1 to anything in the universe, by definition. "Uncountable" means "outside the realm of real world algorithms and physics" . they are like "god of the gaps", a name for what we call the beyond the edge of the universe, which we can never reach. But we can assign some structure to it, roughly as an extension of reality, to imagine what it could be like. Sort of like heaven. Sort of.
With --xml ten years ago we would have had ten years of structured output from the coreutils and probably more good praxis of working with the format.
Common Ember.js Developer Mistakes
True, though having the conversion logic built into the app would require no server (costing $0 per month) and scale up to billions of installs without any effort on the developer's part.
The World's Healthiest 75-Year-Old Man (2008)
There's no contradiction. It makes approximately the right predictions, but it's completely wrong as a statement of how things actually are.

A very clear example of such a hypothesis would be one concerning identity. E.g., who was it who committed the murder? The hypothesis that Joe Smith did it might make lots and lots of correct predictions and yet still be completely wrong (because it was actually someone else).
the Google culture — which is more prone to eventually jumping ship and creating a startup.

That's funny because I've always considered Google a place where great people disappear and never come out except for a small number who start a company only to be aquihired by Google.

I could be wrong about that as well.
As others have indicated, you're presenting a false choice. Surely, "solving problems" and "getting..code out the door" are the same thing.

Top developers are identified as such because they are getting results, by which we mean "decent or better, properly working software".

That's it. No conspiracy, just results.
> if you find something on SO that does exactly what you need then yes, just paste it.

I think you should be very careful about doing this without an explicitly stated license with reasonable proof of author copyright for the code snippet. It's one of the things that can easily compromise the legal security of a codebase.
Not a big deal. Do a little research instead of making assumptions. I found a German entry in the 2007 Grand Challenge:

http://en.m.wikipedia.org/wiki/DARPA_Grand_Challenge_(2007)#...
But with Apple there is the "aunt and your friends and family factor". Everybody has heard of Apple and a large swath of people would tend to be impressed by the fact that you worked there. It would also tend to be the type of place that obviously looks good on your resume if you need to get another job in the future so it offers that as additional security.

Techies might care that you worked at Tesla, much of the rest of the world does not.
Software engineering is not engineering, yet you call yourself a software engineer?
> If I want to succeed, do I need to stop caring about solving problems and start caring about getting as many lines of code out the door as I can?

You need to start caring about solving problems. If the way to get a problem solved is to Google something and copy and paste a few lines, solve the problem. If you want to spend years letting things into your brain but not out, there are plenty of useless corners in academia.

That said, if the top developers you see are uninterested in learning more, you're working at a bad company. Which is not particularly uncommon: good developers go work where other good developers and good management are, and at the places with bad developers and bad management, there are still people who are at the top of that company. Top developers are good at finding answers by Googling, but that's a way for them to learn, not a way for them to avoid learning.
no sugar in what? drinks, snack, etc?

Triscuits solved my snack problem and they are high in fiber and whole grain with only three ingredients; get the low salt variety as they taste just fine. You can top them will all sorts of delicious fruits and vegetables to where each day is something different.

Sugar is so hard to move away from, I know many who got into juicing only to gain weight because they juiced what their tastes buds told them tasted best, fruits!

Sugar free naturally, stick to the vegetable isle. Drink lots of water and if you like it, experiment with different varieties of tea either hot or iced
Further summing up: It's a great career "statisfice".
It would be awesome to see some metrics of the proposed examples.

i.e. A conversion rate of each signup form.

Also, pick 1 language and stick with it. Иначе другим не понятно что там написано.
Every Single Web Portfolio Ever
You're asking a community full of people who consider themselves to be "top" developers whether there's room for criticism of top developers. Even if your observations were right (and I have no idea if they are or not), that's not likely to be a very productive conversation.

Don't focus so much on competing with other people. If you want to succeed, then keep improving your own skills and approach. It doesn't necessarily need to be the same skills and approach as other people, it just needs to work for you. If taking the time to study or read books and develop sharp expertise in particular technologies is important to you, then keep doing that. Someone, somewhere, will need your skills, and then you'll be the guy that knows X better than anybody else.

Think of it like dating, yeah? You look around and think, "wow, everyone likes guys with hair gel, I guess I need to use hair gel too", but it's a big world, and there are lots of people that think hair gel is gross. Maybe instead you practice having a great smile or being friendly, and that gets you happiness instead of hair gel.

Maybe you've hit real lows because you've been comparing what you do to what other people do and then deciding that what you do sucks because they get attention and you don't, so to defend what you want to do you're trying to convince yourself that what they do actually sucks.

But none of that actually matters. It doesn't get you any closer to happiness. Just do your thing and do it well.
I joined a pre-IPO company as a contract to hire, and then decided to not join as full time. But I had buddies who joined full time. They all left the company 8 months later after the IPO: the stock price fizzled out.

Just compare your salary and options, with what Google, Apple offer. And also check whether the start up is type A (Uber, Dropbox, etc), type B (box, etc) or type C (unknown potential).
It doesn't sound like you're describing top developers. Instead, you're describing really good script kiddies. The top developers are great problem solvers and, in my experience, are really good at remembering details and knowing when to apply those details.

Getting things done is huge, but grace takes a little more than the "get things done" mindset. Being a top developer is being a really good painter. Anyone can paint by numbers or look at a painting of a rainbow and take lots of time to copy it. But, not just anyone can paint the same rainbow without any such guidance. Both types of painters come out with the same result, but one did it employing techniques that may have been hard to come by and can't be taught. The painter who doesn't need said guidance is probably more valuable than their counterpart because the painter needs the least resources.
I can see how one might talk in parallels between the mind and a mill, or steam engine, or a computer. I don't see how it would work with a catapult, even in a historical context. Can you elaborate? Or even better, if you could show a reference to that.
Best of Firebase, a monthly Firebase newsletter
If you try the piston getting started example on Windows (the spinning square), change the freetype name to "libfreetype.a" and put it in the 1.0 path: C:\Program Files\Rust stable 1.0\bin\rustlib\x86_64-pc-windows-gnu\lib

Other than that it works.
I have to agree with @crdb. The CEO of the company I work at has a sociology degree, but bought a book on PHP/MySQL because "nobody wanted to program my stupid ideas so I just had to figure it out." He created the MVP himself by using copy/pasta jQuery soup, in line SQL queries and GoDaddy hosted PHP. He was able to get 100,000 customers though and got a CTO on board to convert the MVP to something scaleable (which I'm working on now too).

The CEO doesn't code anymore, but I had huge respect that he learned enough to get the ball going.
Seriously, I copy/paste code all the time. If I'm writing a complex newsfeed algo and I need to write a sorting function. 9 times out of 10 the sorting function I need is easily googleable for my language. As much as I love to code, why would I waste my time writing it again? Yes, I wrote it in college, I loved it very much. But I won't deviate my focus from my newsfeed that I'm building.

It's not much different from using a library. Understanding is fun, but reinventing a wheel can be a serious violation of prioritization.

Put in other words -- you must choose your battles.
Really a tie between Blink, and Atlas Shrugged.
Your final question is very interesting, it gets at the heart of the matter: the Banach-Tarski theorem shows us that in your universe of infinite points and no atoms, there does not exist a definition of volume which is consistent. So in this universe the water level in a tub cannot be defined.
If you know your estimates are going to be squeezed by two weeks, add that in and say it'll take eight.
There's a balance here. On the one hand, you have to have the ability to figure things out on your own when nobody knows the answer; sometimes you do need to read through a pile of undocumented "legacy" code and puzzle out what it does. On the other hand, no one person can know every last detail of a twenty-million-line codebase; you're going to have to be willing to work on codebases you don't fully understand, and do the best you can with what you know. That doesn't mean people working on such a codebase are not "interested in learning everything they can about development", or not "caring about solving problems". However, there's a balance; you can't be so busy learning that you never take the time to apply what you've learned; knowledge.

You definitely shouldn't be focused on "getting as many lines of code out the door as [you] can"; if you think that's what your employer and co-workers expect, then either you aren't interpreting it correctly, or you need a new employer and co-workers. However, you should be focused on being as productive as you can. Develop a reputation as being the developer who almost always knows the answer to whatever crazy question their co-workers have, or who knows a little something about almost everything; those people are invaluable in an organization. And in the meantime, don't forget to actually write code.
“BackRub is written in Java and Python...” (1996)
I love that this is the state of public discourse even on hacker news. Just accuse something of being like anti-vax and the down votes follow. No critical thought required.
This came out last year, and was discussed on HN.

One of the things I said then, which I'll repeat now, concerns these lines:

> But many of the subject areas that experienced a decline in older citations were part of two broader areas: chemical and materials sciences, and engineering.

> Consequently, these broad disciplines show almost no increase in old citations. Just why citation trends should differ in these disciplines isn’t clear.

If you look at the early history of information retrieval you'll see that chemical documentation was tightly connected with it. Several of the IR pioneers (Luhn, Mooers, Taube) worked with the American Chemical Society or presented at ACS conferences. I like to point out that "information retrieval" as a term was first presented at an ACS meeting.

By the 1960s, CAS (the Chemical Abstracts Service of the ACS), the Institute for Scientific Information, and other organizations provided pretty complete indexing of the chemical literature.

While it's improved since then, I believe the old literature for chemistry has been searchable longer than for other fields, and in large part because the chemical structure give a uniquely indexable key (usually) for indexing the literature.
You're experiencing what basically every smart computer science graduate does when going off into the world and encountering codebases that serve customers. They're huge and messy.

I had this same rude awakening at 22. You're used to dealing with 500 lines of code; now you have to deal with 200,000 lines of code. Even 10,000 was too much for me at that age.

Computer science is about being smart and understanding things. Software engineering is about realizing how dumb you are compared to the task, and developing strategies to control that complexity and manage your time.

The best programmers I've seen have these qualities:

1) They have simply exercised their brains enough to wrap their heads around 50,000+ lines of code. They know how to read code.

2) On top of that, they know how structure their code to avoid having to understand all of it line by line. They write their code to facilitate "chunking"', the same skill that a chess player uses to assess a board position quickly.

3) They trade off time vs quality by sweating the details WHEN IT MATTERS. For core parts of the program, it absolutely pays off to do original research. For example, writing data structures for search algorithms or graphics engines.

But the data structures are less than 10% of the code in an information retrieval system; the graphics engine is is probably 10% of the code in a real game.

For the rest of the system, you need to plow through it quickly, perhaps copying and pasting code from older systems.

Usually you have different developers working on these parts -- some people are good at plowing through tasks; some people are good at working on well crafted code solving a difficult problem. But the latter are usually experienced developers in their 30's, not fresh grads at 22. At 22 you'll be tasked with plowing through code.

After 13 years of professional programming, I think that "taste" is basically learning what matters. Lots of things I obsessed over when I was 22 didn't end up mattering. When you can only work on 1,000 lines of code at a time, you're simply missing the big picture. So basically that's a thing you have to work on to succeed as a developer.

With that said, there's also the fact that most software is shit :) Software is shitty and in particular insecure due to its sheer size.

http://steve-yegge.blogspot.com/2007/12/codes-worst-enemy.ht...

So I described the status quo in the industry... but if you can somehow move beyond that, that's very valuable territory.
Agreed if it's anything of significant size. If it's 2-4 lines though, it's almost certainly fair use. Can a lawyer comment?
I've a number of friends on various teams, from WebKit, to iOS, to datacenter folks, to various app teams, and hardware teams and not one has ever consistently worked a 40hr work week. Most are easily averaging 50-60, with spurts close to or over 100 before launches. Consistently the message I've heard is people are expected to "work till its ready", so I'm not sure where you'd have heard this about Apple.
There will always be more people of merit than there will be jobs of merit. If this last statement is true, what are the
implications for the losers of society?

This makes me think of the Hunter S. Thompson letter posted a few days ago[1]:

Let’s assume that you think you have a choice of eight paths to follow (all pre-defined paths, of course). And let’s assume that you can’t see any real purpose in any of the eight. THEN— and here is the essence of all I’ve said— you MUST FIND A NINTH PATH.

[1] http://www.openculture.com/2015/02/hunter-s-thompson-life-co...