skysight-inc/HackerNews huggingface dataset:
I agree, it is "programming" vs "software engineering".

You are looking at the problem as a programmer, and making reasonable assumptions about how to solve the problem using objects and graphs and interfaces and models. If we had a better model, our project will go faster and be better.

I am looking at it as an engineer, and seeing what actually happens in real life when real humans build real code. If we had working code for simple problem A, then when we get to more complex problem B, our developers will have more experience, better morale, and better support from management who have happy customers.
Any chance this works on Android?
Lately they have cut things – the sequester was real and will be causing damage for decades[1] – but generally in the least productive ways possible. That gives them something to point at while still leaving plenty to rant about and, of course, more chances to grandstand over self-created problems like backlogs at the IRS, VA, etc. I'm sure we're going to hear plenty about this security breach and nobody will mention that the federal pay scale tops out below what the average infosec professional makes or that agencies have been begging for funding to improve their IT staff for years.

1. Most young scientists are leaving research due to budget cuts at NIH, NSF, NASA, etc. They're unlikely to ever come back so we've lost a large chunk of an entire generation of research in most fields. Sure, many of them are going to industry but I would submit that a crop of data scientists selling ads is less productive for the country long-term than all of the foundational pure research which industry rarely funds.
Correct me if I'm wrong, but the linear elastic region usually ends somewhere around 0.2-5%, meaning 1% strain is not well within the linear elastic region. If you just do σ_y/E, you'll get the yield strain. Using rmxt's numbers you get 0.17% yield strain. Using [1] for 1018 steel you get 0.155% yield strain. The strains you calculated are not insignificant.

[1]http://www.matweb.com/search/datasheet.aspx?matguid=3f2ce033...
Yes I enjoy programming in Java. On the server-side its performance is very good. As far as the enterprise goes, it will be in use for years to come.

It is a bit verbose but I'm ok with it. I know its fashionable to hate on it but I find it a comfortable language to work in. So, yes it's still very relevant in business and is worth learning.
But you haven't factored in the cost of the time machine. How much did that cost you?
Only about 300 years before Chaucer and you get Beowulf which is as incomprehensible to the modern native English reader/listener as Danish is.

https://www.youtube.com/watch?v=bGVDeafmsco

http://www.kami.demon.co.uk/gesithas/readings/bss_oe.html

And a good argument can be made that Shakespeare has a non-trivial percentage that's also not comprehensible to the modern reader/listener. And that was 16th century!

However, I agree that between Shakespear and the King James Bible's influence, that's about as far back as a Native English Speaker can go and generally understand what's going on. Much of it is attributed to the "Great Vowel Shift" in English https://en.wikipedia.org/wiki/Great_Vowel_Shift

It's amazing what important literature can do to "fix" language.

It seem remarkable that so much linguistic change can happen in such a relatively short time period, but my wife points out that in her home country of Korea, the original 15th century text that introduced their written language (Hangul) is not readable by modern Korean readers (slight differences in orthography from the modern Hangul notwithstanding).

http://boards.straightdope.com/sdmb/showthread.php?t=272447
Sigh ThomPete, where do you live? The Hamptons?

Really, you need to actually go out and meet the world around you. It isn't all wine and roses I assure you, but it is better than living in a bubble, those burst, you know. If you decide to travel to South America and go by Bogotá, contact me and I'll show you around the good, the bad and the ugly.
But, what are you defining as "architecture" here?

Having a design that requires you to completely re-implement your app whenever changes are required (even significant ones), seems more a problem of not following proven design principles than one of poor "architecture".
Yeah, keynote/"compelling conference content" presentations are very different animals. Even if some would prefer my presentations of the former type stood on their own better, my focus there is on the live experience. If you're presenting the findings of a consulting project? Not so much. In that case, the charts and graphics should be professional and clean but also focus on data/recommendations/etc. Very different animals.
I read each of the five "lessons learnt" in this article and thought to myself: "No shit, Sherlock!"

After the dot-com bubble burst in 2000, I ended up working in FinTech. It was an eye-opening experience and, ever since, I have been constantly amazed by the irrational optimism/arrogance/hubris of people who have zero experience in the sector but believe that they know better than people who have been working here for decades.

It's actually embarrassing at this point. To quote Lucky Green, God forbid "there might be something to be learned from several millenniums of financial services best practices."
Oh! Yeah...Intel had been using anti-AMD "discounts" for quite some time, dating back to 1991. Things ratcheted up in the late 90's.

Giving dishonest information feeds inaccurate estimates.
Things have actually gotten worse for us developers. I've noticed now that I'm taking a significant hit on App Store views when I release a new version.

My best guess is that this is due to the reviews being reset on each release. If I'm out a couple of weeks of growth due to each new release I have every incentive to release less frequently.
same issue. did you ever get this to resolve?
Man, a few hours ago I was debating with some team mates about js frameworks. In the middle of this ocean of frameworks I keep going with ExtJS. And I'm very criticized about this. And today the discussion is as always - that it's a monster and I need try ember ou angular etc etc... But I keep using ExtJs happily focusing in my business and almost never worrying about why something not work and wondering how to use new new coolest javascript/css/html thing - I almost never touch html and css since I begin to use ExtJS. I'm happy and it's working.
Indeed. I never really understood how things ever actually make it through the horizon in the first place (as seen by far-away observers) in order to make the black hole grow.

I /think/ what's going on is that, from the outside, you never really see a big black hole. Instead, you see what is, for all practical purposes, a big black hole, but really it's an exceedingly dense band of stuff, red-shifted to the point of invisibility, around the horizon. Of course, once you go close enough to inspect it for real, you get caught up in the time dilation enough that it looks more and more like a real black hole. If you go through the horizon, everything that ought to have preceeded you through the horizon already has, and it all makes sense.

The math for this is quite hairy [1] and I suspect that we're mostly limited to numerical simulations. The closed-form steady-state black hole metrics are gnarly enough as is.

[1] Terrible pun -- look up the "no-hair theorem"
It's amazing how long this has been going on, yet a user-friendly database app hasn't supplanted it.
But, isn't the point of Yagni that there is not such a large continuum? Isn't the argument that attempting to anticipate the future to any degree is generally a waste of time?

That is the argument, but that doesn't make it true.

I don't know that it requires making "architectual decisions" as much as following generally good design principles and keeping your couplings reasonably loose.

Aren't these going to give much the same result in practice? But if the YAGNI advocates are correct and we can't usefully predict the future at all, how can you judge things like where to put your module boundaries and limit coupling?
I don't find Arch to have many hurdles (Until there is something broken and placed on the webpage). They should have some tie in with Pacman to say read the front page before updating or front page was updated on date so and so ... Would fix the last hurdle that Arch has over other ditros.
Android Wear for iOS could be the slap on the wrist the wearables category needs
Why are there so many shuttered storefronts in the West Village?
> As a result, a base install of Android without all Google's services is very poor and pretty outdated.

You can install AOSP or custom ROMs such as CyanogenMod and have a perfectly free, modern smartphone OS. You won't have access to all the Android apps in the Google Play Store, but that's self-evident. The F-Droid repo provides verified FOSS apps, or if non-Google proprietary sources are permitted there's the Amazon Appstore.

> Most of the work Microsoft does on Android (and iOS) would easily be replicable by Google on Windows Phone: Office, Skype, OneDrive... are all apps that Google has competitors for on Android and iOS.

The app in question, Cortana, will be able to integrate into Android at least as deeply as the Bing app does now, which means it can replace Google search in most ways. If Microsoft had an Android launcher, they could ensure Google is completely replaced (by supplanting Google Now). Combined with Microsoft's existing Android lock screen and other apps, all that's needed to complete the Microsoft Android experience is Windows Store for Android.

On the other hand, the closest you can get to replacing Cortana on Windows Phone is to disable Cortana completely, which means queries will be handled by the search engine in your default browser instead. IE is the only browser option, but you can choose either Google or Bing (except on phones that disable the Google option).

Google does achieve remarkable results on iOS despite its restrictions. But that simply demonstrates the monumental effort it would take to bring a sub-par version of the Google experience to a locked-down platform, whereas Microsoft can take over Android with relative ease. iOS has marketshare and legacy ties to justify the expense, but WP has neither.
It looks like a per generated from a PowerPoint deck to me.
That's not an issue unless she wanted to be president. She taught in the US, and that's good enough for me.
Looks like the quick fox is no longer.

"Grumpy wizards make toxic brew for the evil Queen and Jack."

https://www.google.com/fonts/specimen/Roboto
So ARMv7 you mean? This is CPU hardware level memory model dependant. Not absolutely sure, didn't look that hard, but I think this doesn't implement ARMv7 memory model correctly, so maybe it doesn't always function right. It might be possible for a message to be committed, but some cache lines containing message bytes still dirty.

This implementation is using sun.misc.unsafe afterall.

Different ARM CPUs implement different memory models. So what applies to one ARM design might not apply to another. ARMv8 is probably easiest to support due to new instructions, load-acquire and store-release.

Again, not sure without further analysis. And no time to do it.
Be careful calling it Tetris, the company that holds the rights I think pretty consistently goes after people who violate it's trademark and copyright.
A more obvious reason that dating sites don't get funded is that they're uniformly terrible. No one understands dating well enough to create a service that works reliably, and according to Pew Research fewer than 1 in 4 online daters actually find a long-term relationship online. So the sites become an exercise in hand-waving, and I can understand why investors are reluctant to invest in what boils down to pure marketing, the service equivalent of a Pet Rock.
It's commonplace. The H1-B visa is virtually designed for indentured servitude.
Not necessarily, but see also the second last paragraph on https://news.ycombinator.com/newsguidelines.html
I can only assume that the point you're trying to make is that there's not nearly enough information for a reasonable answer. It's certainly hard to come up with solid ideas without a clear understanding of the game's pacing.

In RTS games, teching and building armies compete for resources, so I'd hazard guessing that Game 1 happens because somebody opted for early aggression, which forces everybody to spend money on units to fight off the early threat. Looks like a well balanced game where both teams kept the aggression level high, which justifies the long duration, and the low-tech end-game.

Second game looks like there was little to no early-game aggression, which meant that everybody got to funnel resources into teching up early. I'm not sure if late-tech battles are more all-or-nothing, or whether one team was just clearly stronger than the other -- though if that's the case, why didn't they push for an advantage earlier? AoE is much more symmetrical than, say, Starcraft IIRC, so one team having a weaker early game but a stronger late game doesn't seem likely.

I'm curious, though: how does this relate to the article?
This is largely just an argument against bad presentations - PowerPoint or otherwise. I agree that PowerPoint is not the right medium for many things (e.g. technical reports), but a lot of these critiques are also the strengths of PowerPoint. The lack of space forces the presenter to slim down their argument to the essentials. That shouldn't encourage burying important information in sub-bullets, but to the contrary, encourage highlighting key risks/concerns.

The downside of technical reports and white papers is that it's far too easy for people to blather on without purpose, and it's far too hard for me as the audience to review. I can skim through a PowerPoint in minutes and get a good sense for whether it's worth my time. It's much harder to do that with a long free-form text. I also think the presenter is more important than the medium in most cases: I bet the same person making those awful NSA slides would write an awful white paper (and vice-versa).

Long story short, people have a really hard time concisely and precisely expressing their arguments, and we all need constant practice to get better. Everyone should also have several options in their presentation tool kit and be able to use the right one for a given task.
Loaded with lead: How gun ranges poison workers and shooters (2014)
Android and iOS development Leads with samples
2014 Data Science Salary Survey (O'Reilly) [pdf]
My argument is pure logic, based on a direct comparison of the total cost of doing it both ways. No fudge factors are required.

The conclusion fails and so YAGNI always gives the best possible result only if there is no real world situation where the initial assumptions in my argument hold.

Clearly there are actually numerous situations where those assumptions do hold, so YAGNI cannot be trusted to give the best final outcome in all cases.
Your response is actually very surprising. I'm looking at the problem as a software engineer, who has to make architectural decisions about the applications I'm building. You're looking at it like a programmer. YAGNI is very much not an "engineering" response, it's a "programming" response. Engineering is all about careful, methodical design and architecture and planning for the future maintenance of the product. YAGNI is pretty much the antithesis of this.

I'm curious what kind of software you work on. Most of the software I do is applications / frameworks development. Planning ahead is very important when developing the architecture of an application, and is doubly-so when doing any kind of API design (both when developing frameworks and when developing reusable components inside of applications). You certainly don't need to implement everything up-front, but you do have to understand the future requirements and design appropriately. Failure to do so leads to blowing out time / budget estimates later when you realize your code isn't maintainable anymore and all the "quick" implementations people did to avoid having to make architectural decisions are now so fragile and dependent upon assumptions the implementor probably didn't even realize they were making that you can't change anything without having large ripple effects.
No, not really. This is "proper time", i.e. time as measured by the unfortunate person in the space ship who's falling in.

The observer outside never sees you hit the event horizon in the first place, so I'm not sure it's well-defined to talk about how long an outside observer thinks it takes you to hit the horizon once you've crossed the singularity.

Incidentally, one thing the article got right is that time and space are kind of switched inside the black hole. Once you cross the horizon, the singularity is no longer something that's radially inward from you. Instead the singularity is in your future, kind of like tomorrow is in my future. This is part of why you can't escape. Once you're inside, it makes no sense to fire your rockets to push yourself backwards in time. In fact, firing your rockets just makes it worse. You'll accelerate, and the resulting time dilation will actually /reduce/ the perceived time before you hit the doom in your future.

This is a big difference between GR black holes and toy classical black hole models. In a classical black hole (a point mass and an "event horizon" around it where the escape velocity exceeds the speed of light), you can try to throw something outside the horizon, and it might escape the horizon, but it's guaranteed to fall back in unless someone catches it or it has rockets and can continue propelling itself outward. In a real GR black hole, you can't cross the horizon from the inside in the first place. Despite this, if you squint a bit, the toy classical model predicts the Schwarzchild radius correctly
I must not have made my position clear. I don't think that they're particularly committed or effective deficit hawks – the true fiscal conservatives were purged years ago – but rather that this is now a key part of their public image. They heavily promote the idea that government is inefficient because it keeps people voting for them and, most importantly, keeps corporate-backed groups like Fox News from going on the attack in the next election.

That might necessitate a token effort somewhere to cut things but the real goal is the posture, not the results, so maximizing inefficiency isn't something they're concerned with. In most cases, they'll try to cut things which affect people who don't vote for them anyway – mass transit, funding for the poor, etc.
At MIT, Mastering the Science of Working from Home
Yes, my first thought as well. The Verge has gotten downright terrible of late. So much of the content on the site now is either pop culture click bait or PR fluff pieces for tech companies. Other than the reviews, which are still decent but don't offer much that I can't get on any other tech reviews website, I can find very little reason to go there.
That might be a way to "win" internet debates. But I use it to write software.

It's actually quite simple. YAGNI applies to features/functionality only. Not refactorings.
What about the next 37 cases, wherein you didn't need the second feature?

Yagni says that more often than not, you won't need it. Every single case may not prove out according to that dictum, but that doesn't mean that the overall approach is suboptimal.
Alot of the same arguments about the final coming of 3D were made. Not saying that's the case for VR, but it's an unknown yet if this will the crossover point or if there will need to be another generation of development before we exit the VR uncanny presence valley.
Very nice! Not sure if it will get Perl 6 any better adoption, but still very nice.
(for those not so good at math, 1ns = 1 clock cycle at 1GHz)
Not only ARMv7, but running on Dalvik or ART.
I can't believe I'm supporting Paul over Obama on anything, let alone this.

Given it's his last term, I'm surprised that Obama is at this so much. It could be the pivotal cause that sinks the Dems in 2016 and Paul's filibuster only bolsters his own campaign.

Feel dirty supporting a tea-partier.
Training for Discontent – Parenting and Ambition in Silicon Valley
Got it — thanks!
That's true, since of course developers need to be able to test their own applications, but that's hardly comparable to letting ordinary users install third-party apps, as you can on desktop Linux/Mac/Windows and Android.

Except for Apple's higher developer fees, you might as well say that iOS allows sideloading, then.

If an ordinary WP user wants to install an app that hasn't been published, they're out of luck, whether or not they have an SD card.
I am so disappointed in Obama. I voted for that liar twice.
This is a great post. I cannot believe "Party Machine" is from '78. Holy crap, that's unbelievably contemporary.

It kind of goes to show how similar many of the music making tools are today, but here's a guy putting together an amazing jam and Carter was still in office.
Oh, it'll shift to 64-bit on ARM soon enough. Power efficiency. Flags register consumes less power and less memory (cache) subsystem traffic.

It's funny that only things 64-bit ARM doesn't help with is supporting more physical RAM (32-bit designs like Cortex A7 and A15 support 1 TB) or 64-bit register width (almost totally useless). You probably want to rather use 128-bit wide NEON instructions...
Currently, the link in the article that leads to irs.gov personal account creation, http://www.irs.gov/Individuals/Get-Transcript , doesn't work for the stated purpose. And while a more direct link I found, https://sa.www4.irs.gov/eauth/pub/login.jsp , doesn't work either at the moment, perhaps at least one of the two will work sometime soon.
Quantcast has more accurate metrics for Vox sites (comscore is just guessing, but Quantcast actually gets data from the sites directly).

It reports 81M US visitors/month for the entire Vox network (https://www.quantcast.com/p-d9vfr8QTWnv1E) and 13M for The Verge (https://www.quantcast.com/theverge.com).

That actually lines up pretty closely, so it's likely they were talking about US visitors rather than global (which is ~2x for The Verge).

(Disclaimer: I used to work on Quantcast's measurement product).
CPU memory model and atomics support is what matters here. Dalvik or ART are unlikely to have anything to do with it, as long as they provide access.
> It makes me wonder where the divide is.

I think it works beautifully if you're applying it along with "refactor mercilessly", backed by good unit tests. It's a principle that doesn't necessarily stand on its own; it needs to be part of a healthy, iterative system of development.

If refactoring becomes difficult or dangerous for whatever reason (eg, designing an API for long-term, widespread usage), then YAGNI may not work.
Car DVD Player GPS Navigation for Volkswagen Golf
The push for surveillance is clearly something that is a "must have" from Washington's point of view -- to the point that it trumps ordinary political concerns.
Compete's data is almost totally useless in my experience. Just look at what they show for my site right now (a similar growth pattern): https://siteanalytics.compete.com/encosia.com/

Here's my actual data from Google Analytics over the same period: http://encosia.com/i/encosia-unique-users/
This seems very curious. Is there any information out there as to why Obama is supporting this?
I can't tell what type of lower case 'g' i'm getting without looking deeper :(
The tea party was a ground-swell movement that got co-opted by the Kochs to promote very little more than the Republican status-quo in terms of political ideology. Once they got involved in funding things it turned from libertarian (anti-war, pro personal liberty) into something much different.

The tea party is probably only as dirty as the Koch's money. Remove that and you've got a bunch of people who basically believe in the goodness of individuals. That isn't terribly dirty IMO.
well, that actually is a great piece of information to be aware of, the whole in-game strategy changes!