HN user

visural

132 karma
Posts4
Comments45
View on HN

But the thing that’s unusual about good scientists is that while they’re doing whatever they’re doing, they’re not so sure of themselves as others usually are. They can live with steady doubt, think “maybe it’s so” and act on that, all the time knowing it’s only “maybe.” Many people find that difficult; they think it means detachment or coldness. It’s not coldness! It’s a much deeper and warmer understanding, and it means you can be digging somewhere where you’re temporarily convinced you’ll find the answer, and somebody comes up and says, “Have you seen what they’re coming up with over there?” and you look up and say “Jeez! I’m in the wrong place!”

It makes me happy whenever I read quotes like this of Feynman's.

Not a very rigorous test - but I just applied this to one of our (very) large angular 1.x apps and it had a consistent 20-30% reduction in profiled execution time across the couple of test interactions I did.

That said, I'm not sure it made much perceptible difference as the app already performed adequately and the reduction is amortized across all of the interactions the user makes.

As with the shirt example in the original article, the cost of labour (i.e. paying people for their time) represents the majority of the cost in building a house. The other items you list are using cheaper overseas labour in their construction, whereas if you're building a house by definition you need to pay local craftspeople for their time. Also due to their physical size, houses require lots of people to put together (i.e. the time is in some sense proportional to size of the item being constructed).

Am I right in saying that the complaints with btrfs in CoreOS are specifically around its use in conjunction with Docker?

(Interested as I'm thinking about building a homebrew NAS/general purpose server w/ btrfs, there's a lot of outdated info on btrfs but I was getting the impresssion that it's now a pretty stable and useable filesystem)

Y U NO commit?? 12 years ago

Netbeans also has a local history recording feature which is integrated pretty well alongside the git/vcs features (just hit history on any file and see a log of all your local changes intermingled with the committed versions).

There's nothing in the parent comment that seems unreasonable to me. You're putting a spin on it that doesn't exist.

The content of Quora today is what it is. The Internet Archive has no agenda for misrepresenting the content of any site. They don't want "records to be" anything other than what is reality now, tomorrow and the in the future.

The Archive's stance is perfectly reasonable. You can't arbitrarily go back in time and remove content that existed at the time, otherwise it's not a historical record.

So you can opt-out totally or be included in the archive's records, it's that simple.

I think you used the wrong word - IMO Uncle Bobisms often show a lack of practical pragmatism. The vibe I usually get from listening to him is along the lines of... "if everyone just did things the right way then we wouldn't have all these problems", which is firstly, not a realistic point of view, because there is no reality where every developer on a team is going to do everything the same way, let alone one person's idea of the "the right way", and secondly it's just unprovable conjecture that these things would solve all our problems in the first place.

I'd rather listen to people with a proven track record for shipping great software and a history of reasoned pragmatism regarding techniques and methodology.

While the benchmark shows that there is a measurable difference between using getters/setters and NOT using them. I have doubts this would make a great deal of difference in application level code. The performance bottlenecks are most likely going to be IO or calls, or if the app is CPU bound, actual calculation code.

I'd be willing to bet the percentage of time spent in getters and setters on the call stack is pretty insignificant.

It is possibly 600k non-spam emails per day? With the 70GB including all data w/ spam. Because with ~300k accounts 600k emails per day is only 2 per account which isn't much taking spam into account.

I recently read "The Naked Ape" and a theory discussed there, is that public speaking is actually an acutely unnatural scenario which we are not well evolved to cope with.

To stare at someone is generally a threatening gesture, certainly there are many social cues about when it is appropriate to maintain a fixed gaze, and if a stare is held to long or without reciprocal give-and-take then it is usually interpreted as threatening/aggressive.

Now think about public speaking - 100's or 1000's of people all staring at you, the speaker, at the same time. It's no wonder this triggers a fear (or fight/flight) response in most people.

It's also worth considering, in our distant primate past, we are used to communicating with only a handful of other people at a time, outside of the context of tribal warfare.

I'd be interested if anyone has any more recent research / theories on this.

I'm not sure how that contradicts what I said about DFA and other similar Kickstarters.

If you backed a Kickstarter that was pitched as solely a preorder for an already complete product, then you have every right to be upset if that Kickstarter doesn't deliver.

The original point though, was about kickstarters which are funding the development of products from scratch and allowing tracking and input from the funders.

After viewing all the negativity on here, I'd actually recommend people that feel the same _should_ stay away from Kickstarter.

If the only value to you is getting the game itself, then wait for it to be finished and buy it through Steam or your store of choice.

Kickstarter is meant for people who find value in not just receiving the product, but in watching, and discussing it through its development and also allowing creative people they respect the opportunity to the do the work they'd like to do.

Most of the negativity in these comments seems to be from people that just "want the game". Well that isn't what you signed up for. If you feel burned by the first one, you would be well advised to stay away from future Kickstarters, from Double Fine, or from any other developer.

I don't list my interests on my facebook profile, nor do a great many of the people on my friends list. For some that is because they don't want facebook having this information, for others, they simple can't be bothered entering it.

I don't think you can classify this as "using it wrong".

It seems obvious that if I or a user like me were to use this service it wouldn't work very well, and would potentially devalue the service for other users (through poor matches).

The developer of the service is artificially limiting their market by only allowing Facebook Connect and they may have problems getting the necessary critical mass for the service to be useful as a result. I don't think it's trolling to make this observation.

It's also worth bearing in mind the needs of the many, vs. the needs of the few.

With the kiddie porn issues, generally the number of children being talked about is a very small minority of the total, and usually the issue under discussion has only indirect possibility of helping those children.

However advertisement of poor food choices to children is something almost all children are subjected to on a daily basis, therefore when discussing regulation we can see that the majority of children will be beneficiaries.

Why would you want your phone to be the key to your most secure data?

Also from what I've seen in the past most finger print scanning and cheap, "organic" identity verification tech is not reliable and easily circumvented.

Despite not being perfect, basic password authenication (or even better- pass-phrase) is a security mechanism that's easily understood, easy to implement and can be pretty secure.

(Although still possible to do badly/incorrectly as we keep seeing).

From what I see it is usually well intentioned but not exceptional developers trying to write "good code".

They know some sort of abstraction is called for, but they end up picking abstractions which are actually a net negative for code complexity, rather than a positive. If you have enough of these developers then it devolves into code very much like the OP.

There is also a resistance to large refactorings which "clean house" of these sort of abstraction errors in enterprise teams and a lack of developers with the skill (and balls) to do it. So this cruft tends to accumulate.

It seems to me, the problem with AI as applied to gaming, is that just having "good AI" doesn't mean having the smartest AI that can kick the player's butt, it means having AI that the player can observe and formulate strategies against. If it doesn't behave in a human way, and make it's decisions clear to the player then it's not fun.

In short, for gaming the measure of good AI is "fun", not "intelligence".

I would assume this - "I have made two basic arguments about post-9/11 airport security. One, we are not doing the right things. And two, the things we are doing are wrong."

While correct, it would benefit Apache in the long run to foster better communities and tools for their projects to grow. While they provide value in terms of the protection/process/management it's all for nothing if the developers can't collaborate effectively.

GitHub has changed many developer's UX of opensource development to the point that they don't want to do it "the old way". Apache should be looking to grow in this direction to keep their developers and projects engaged.

Totally agree. I was super keen when it was announced to try it out. But they didn't even have a friendly error page for Apps users initially. Then the only thing they said was "hopefully really soon". And there hasn't been anymore communication since about when apps users might be invited.

At this stage, I don't think I care if they do finally make it available.