skysight-inc/HackerNews huggingface dataset:
There are compelling uses for inheritance polymorphism - GUI frameworks are generally examples of this technique put to good use.

I suspect that OOP systems would be a lot less likely to go haywire like the author describes if the Liskov Substitution Principle were better-known among programmers.

I'd even like to see it baked into a language. Get rid of overriding base methods. Instead the superclass's version is always called, and the subclass is only allowed to tack on some additional code that runs after the base method returns. Yes, returns - the subclass's code shouldn't be allowed any chance to modify the result. It shouldn't be allowed to directly modify non-public fields that belong to the base class, either.

I suspect that a language with those kinds of restrictions on inheritance polymorphism would encourage developers to be a lot more thoughtful about how they design class hierarchies. Which they should be, since someone might get stuck with the results of those decisions for decades.

Taking the C# example - Microsoft decided to push mutability in collection classes all the way down to the root of the object tree. Which creates a lot of pain for conscientious developers. Mutability isn't just a non-essential feature of most collections, it's also undesirable in a great many cases.
NY Digital Health Accelerator taking applications for start-up funding
I assumed it was taken while the poster was driving.
No, you grow up.

Find some evidence to back up your thesis rather than pointing at pretty stuff and saying "see, designed!" and ugly stuff and saying "see, no designer here!"
FaceSpan 5 (Mark’s Misadventure)
This is gonna be HUGE and is exactly what the fledgling start-up community in Santiago needs! Great job guys!
You might want to if there's a killer new API feature available, or if there's a new iOS device with a different resolution that requires a rebuild to support.
F5 networks announced SPDY gateway
I'm one of the hosts, we're going for a shorter format (15-25 minutes weekly) with a slant for story telling with interviews with cool people in the Django community. The first episodes are really just us feeling it out.

If anyone has suggestions on how to better produce a podcast, we would love to hear it! We're big fans of NPR (RadioLab, This American Life, Planet Money, etc...) so we'd like to emulate the masters a little bit.
This very question scares the hell out of me. Language just seems so far away from what really matters.

The language is a part of this, but assembling the right team with the right mentality is the key. There was the DOD Ada mandate and over the years there were some interesting studies showing reliability differences between Ada and C++, but also in hopes of keeping costs lower, they use C and C++ in a lot of that stuff now so that they can use off the shelf software libraries and such. That says a lot, the ability to hire people and develop with some velocity matters too. Language won't make a shitty architecture good. Language won't make a shitty team good, either.

Fundamentally, if you pay attention to where this stuff matters most, Ada has to be a standout choice but those industries don't change, they don't adopt new stuff and the whole process by which that happens in them isn't one that results in the best technology, it's one that results in a consensus technology. The risk of a line of code knocking a plane down or letting the missile hit the wrong target are just fundamentally different than letting someone log in to a web site; maybe they shouldn't be but the very culture difference between those groups is huge and so you can look at them and say "ah, we should use Ada too, 'it's safer'" but that is probably not a great business decision. At least, not right now.
My guess - not much. There are a lot of factors that go into how much a group of users is worth. Do they add a lot of value to your product? I would pay a lot for Woz, Bill Gates, Obama and The Pope to be active users of my product, because their membership would raise recognition of my brand. But just four random people? Worth a lot less. Four random people who are signing up and will forget about my service the next day? Even less than that.

An IPad costs about $500. If you gave one away for every 1000 people, you'd be paying $2 per person to try out your product. Assuming that your product is somewhat niche, you might have a signup rate of 1% (random guess) from a pool of the general population. This would make your cost per user $200.

It would probably be a better idea to imagine who your users will be and target this subgroup specifically. As an analogy, if I'm selling calcium pills to everyone I see on the street, I probably won't sell to many - no matter how good they are. But if I go find people who are afraid of osteoporosis, I will probably be able to sell to many of them.

I would suggest that you stop thinking in terms of absolute numbers of random people (especially if they're not paying) and think more about the value that they can bring to you (whether it is word of mouth marketing, content creation, advice, money or something else). For many products, random people are not the best choice for an initial user base.
Well, the price the rest of the world pay to watch TV is the cost of the equipment.

Cable is opt-in, of course, but your TV is not a paperweight without it. Sure, you don't need a TV license if you only play videogames, but I'm sure you'll have a hard time convincing the auditors.

Blind people surely benefit from television, and have a severe handicap, and that's the point.

"Should they get cheaper broadband too?" Maybe, but they probably pay less since speed is not so important to them.
Latest PHP patch cannot fix the bug
Advertising's Race to the Bottom
The issue of model code creeping into controllers is common with rails and rails-style frameworks precisely because they are not MVC frameworks. MVC was a pattern created for making GUI apps in smalltalk in the 70s/80s. It has gradually been warped and twisted since then, especially when people tried to cludge it onto web development. The resulting thing doesn't really resemble MVC at all, and certainly doesn't deliver the benefits MVC was created to deliver.

MVC is a triangle, rails style frameworks are a line. This is called MVA (Model-View-Adapter). The "adapter" being in between the view and the model who can only interact with the adapter and not each other. The second issue is that in adapting MVC to the web, many frameworks continued with the "one controller per view" notion, despite that being done because of the limitations imposed when creating GUI apps. There is no need for multiple controllers in a web app, all input comes in the same way no matter what view the user is seeing. In fact, the user doesn't even need to be seeing a view, there is nothing tying a view to what actions are possible, you can always submit any http request you want. Your "routes" are your controller, there is no need for a second level of controllers on top of that.

The goal of MVC was to expose model functionality to the user directly so they could understand and work with the domain model clearly and easily. Controller meant "controls the input and output" not "controls the users experience". The guy who created MVC considers naked objects style frameworks to be the closest thing to MVC for the web, not rails style MVA frameworks.

And there is something very weird about this statement:

>On top of that, it’s very common to see logic pushed down into the model

Of course that is common, that is what is supposed to happen. Models are not "stupid containers to pretend to kinda represent my DB sorta but not really". Models are the business logic. Models are the actual application. You are modelling the domain, not modelling the database. The model is the domain, it is all the business logic. The view is the way we present information to the user. The controller is the part that handles input and output. Very simple and effective system, but very poorly understood and virtually never used any more.
It's often been necessary -- most recently, iPad apps needed to be built against a new version of the SDK to correctly use 2x graphics on the new iPad's high-res screen.
I don't see any confirmation to this yet. I suppose this is _the_proposed_ feature, not the real one.
I'm glad you found it easy. Personally, I found it very challenging: although I thought I matched the requirements for mathematical background that Prof Roughgarden outlined in the intro lecture, it turned out to be a struggle to keep up with some of the concepts when it came to apply them in the theory questions.

The programming exercises were fun, but I don't think they were really the point of the course - this "part 1", at least, was much more about analysis than about design.

As a contrast, I've just started their compilers course: there the theory questions are slightly easier, whereas the programming questions are much more involved - the first one has already taken me several hours and I'm nowhere near finished.
Excuse me? His response was nothing but polite and a perfect example of constructive criticism.
One place where I wholly disagree with Chomsky is the unimportance of the deficit. That is a major, major problem. It is true that creating jobs would help shrink the deficit, but I think there is a lot of rampant spending by the U.S. government that does absolutely nothing to grow or maintain the economy or jobs and should be abolished.

Take a step back and note that you don't actually point out or argue how the deficit is supposedly a problem.

So there are spending programs by the government that you disagree with. Fair enough, I'm sure everybody has some government program that they disagree with. [1] That's what politics is about: disagreement about what the extent of government should be, and in which areas it should be active.

What that doesn't give you is an argument that the deficit is bad. If you genuinely think certain government programs are undesirable and should be cut, then it makes sense to simultaneously cut taxes somewhere so that the deficit remains the same. Otherwise you would effectively be squeezing the private sector by reducing the government deficit.

[1] Though it seems weird that you would only support government spending that grows or maintains the economy or jobs. What about national parks as an example of a pretty obvious good that has no economic benefit?
Misleading (and possibly flat-out wrong) title:

"There is no specific information in the deal as to exactly how much additional free space Dropbox will be providing on Samsung devices beyond the 2 GB. "

Can't we find a way to ban accounts that are solely for promoting their own blogs?
Here's some food for thought. Are GC-based and/or lazy-evaluation based languages suitable for safety critical and mission critical apps? It's more difficult to reason the execution time and the memory cost for these functionality.
How to Live Unhappily Ever After
IIRC type systems based on linear types are quite promising for making a version of ML without a garbage collector --- there could be some interesting progress here soon!
5 Books that Shaped My Life
Objective-C isn't the hard part about iOS programming, it's fairly simple and can be learned in a day by a programmer.

It's the frameworks that are hard, and you have to learn those using RubyMotion anyway.

And not only that, but you have to rely on objc framework documentation and do the translation to Ruby in your head. Too many wasted cycles, imho.

On the flip side, I like seeing experimental tools like this to promote new ways of thinking and coding and it will inevitably foster new features into the official SDK (ala blocks).
For the major iOS versions, many developers will have an update ready on release day. People will download apps just to play with new features. Keeping current with the SDK is absolutely a business advantage.
Of course, many micros are still programmed in assembly. And assembly still plays a big part in many subsystems, though I would concede much would be written in C. Not literally everything.
Same here but from 8 to 16 on both my desktops. Huge improvement under Windows, less under Linux with SSD. Working habits vary, but I multitask a lot.
The problem is you really want to inherit the implementations as well -- otherwise every one of the classes that use the Isin interface must implement its storage and accessors as well.
But having C with all its vulnerabilities in the kernel caused many - if not most - of the security relevant issues of the kernel(s). Think of buffer overflows alone.
I think hosting a static image is cool, but doesn't the Internet Archive already have a full-HTML archive of these pages? e.g. http://web.archive.org/web/20110729013424/http://www.nytimes...
Hrmm.. I think the REALLY IMPORANT thing to notice is not that they dropped "Azure" but that they dropped "Windows" as well. Everything in the list that had "Windows" in it, does not have it anymore.

This is a step in the right direction if MS wants to survive long-term.
Most of the images we serve are loaded from a different server, and can be dynamically changed by editors, etc. Putting them into a sprite would probably be more work than it's worth.
I used to do this to put in at least one or two softball questions. It helped to weed out who was paying attention and helped when deciding if someone should get a C or C+.
> The obsession with "rockstars" and "ninjas" who have unwavering "passion" just smells like a search for naïve, exploitable labor willing to give up evenings and weekends for foosball games and beer.

Yes, that's right. I've worked at these companies. Avoid them.

Keep in mind that small businesses that have been around for a decade can be just as bad as some startups. I had a terrible experience at one where I worked 80-100 hour weeks for months before I quit.

I've worked at several startups and small companies, and it's a mixed bag, but none of them have been perfect. The main thing to keep in mind is that the personality of the founder is the single most critical factor in your happiness.

My best work experiences have been at companies that are out of the startup phase and profitable, with around 50-70 employees. They have the HR and reimbursement processes worked out, they don't flagrantly break employment laws, and the hours are closer to 40-45 a week. Just keep in mind there's an expiration on these jobs; eventually they inevitably become big, bureaucratic companies. When a mid-sized company starts hiring vice presidents the clock starts counting down.

Right now I work in a remote office with five other people, and the main company (60 or so employees) is in a different state. It's pretty much the best of both worlds.
You use something else. It's still just a format string, not a whole localization solution. Named arguments means it might be easier to hack together something like

templates = {'en': '{adj} {noun}', 'fr': '{noun} {adj}'}
print(templates['fr'].format(noun='fromage', adj='délicieux')

but that's still a hack, and doesn't even come close to addressing cases like Chinese's "{adj} {counter_word[noun]} {noun}" or gender concord or any of the myriad other things you come across in practice.

Edit: used 'positional' instead of 'named'.
Thanks for taking the time to write this. I needed to hear a lot of these things too.
You're confusing the issue that you have. From what you describe, you worked in an environment that is simply toxic to you.

I think you need to write down the things that you want in a job, wait a few days, and see if those things still make sense. Then figure out how you are going to get a job where you can have those things.

I've worked in small companies, fortune 500 and government. My satisfaction at these jobs had/has very little to do with the type of organization. It's a combination of the culture of the organization, quality of management, and where you are in life. The things I loved about working in a late stage startup at 21 are things that I would hate today as a 33 year old father.

You need to find the right role. You can even find gigs in government with a fast pace and minimal bureaucratic nonsense or hardcore operations roles that demand overtime and pagers.
Startups are hard work, but infinitely more rewarding than BigCo. If you burn out, it will be on the work and not the politics (if you choose carefully).

But this post is a lot like the myriad "I am just getting out of a shitty marriage... Can I ever love again?" posts on the internet.

Of course you can. Job security for a programmer is a ridiculous thing to be concerned about (assuming you're in a startup/software hub). You can fall out of bed and land in three recruiters. You will never miss a meal.

That means you have infinite freedom compared to most other folks. So start interviewing! Don't interview at places that suck. Have drinks with folks at 6pm to see how many people are still in the office. Different companies drink deeper of the workahol than others.

And re: your judgement of YC companies. I know stereotypes are a real time saver, but why would you judge 400ish companies by the actions of a few? YC invests in a pretty wide range of folks.
There’s a Tool for That: 13 Essential Tools for the Ninja Web Developer
I got 50gb added to my Dropbox account when I logged into the Dropbox app on the 7" Samsung Galaxy Tab 2. Maybe it will be a feature for all upcoming Samsung android devices.
Cost of living in the Nordic countries is very high.

Here are the prices for tonight in a large mall-cinema in West London:

2D: http://booking.myvue.com/Home/My-tickets/cinema/westfield/ui...

(£8.90/£7.50 adult/student)

3D: http://booking.myvue.com/Home/My-tickets/cinema/westfield/ui...

(£12.05/£9.80 adult/student)
The problem with "logic getting pushed down into the model" and the gist of the statement is that not all logic is domain logic. Reaching out and touching facebook for a status update, for example, is not domain logic and doesn't belong in a model. And while I agree that we should be modeling the domain, not the database, I think its clear from working on a lot of complex and legacy applications over the last several years rails developers model what the database allows, not the actual domain, thanks to the widespread acceptance of ActiveRecord as the only tool in that toolchest.

I'm in 100% agreement WRT to MVC—Rails' idea of MVC was never really MVC as MVC was originally envisioned.
Useful Online training sites on Software Development
We disagree.

The big-O results of the paper are interesting and with more work could prove a starting point for improvements in very long FFTs. Why long? Because, for big-O asymptotics to kick in, you'll need large n.

But, the domain of applicability seems to be a niche. The "7 non-negligible coefficients" result you refer to is for 8x8 DCT's (as in JPEG). That's n = 8. There are optimized implementations for the small-n cases that will utterly dominate a big-O optimal algorithm like this. Compare Strassen's algorithm for matrix *.

Have you looked at the code complexity of the algorithm in the paper? There are several interlocking components (hash functions, rebinning) that have their own big-O optimality claims and, in some cases, randomization. Getting it all to work together efficiently, given cache issues, even for large n (say, 10^6) would be a serious engineering challenge. People have been working on optimizing data flow for FFT for decades now, and the state of the art is very advanced.

I agree, that the result is interesting in principle. Runtime is actually sub-linear in n, the sequence length.
When I bought ruby motion I was a bit in provisioning_profile hell. I shot off a support Ticket and got an answer within 4 minutes from Laurent Sansonetti. When I told him in a second Mail that I'm not too chummy yet with Xcode he came up with some really useful links half an hour later.

By now there is a very active Google Group.Wrote a question yesterday and had an answer within 10 Minutes. Very friendly vibe, mostly Rubyists dabbling into Xcode, but also some very nitty gritty in depth topics.

Also the BubbleWrap repo (https://github.com/mattetti/BubbleWrap) is chugging along nicely, cool for a young project... So, yes: you can get help.
but it's not a matter of what we believe ought be so vs ought not be so -- that is, it's not a matter of what we want to be true. It's a matter of the strength of evidence we ought to have in order to draw conclusions, given other sets of evidence. It's a normative position, but it's not the specific normative position (based on confirmation bias) you described above.

Think of it as a spectrum. On one end is the pure flake -- always giving too much weight to the newest evidence, no matter how weak, and therefore swinging wildly between different beliefs (I've heard this called "regressive bias"). On the other end is the pure dogmatist -- always giving too much weight to prior evidence, and therefore holding fast to a prior conclusion, ignoring or dismissing even strong contrary evidence ("confirmation bias"). Somewhere in the middle is the proper level of evidential weighting -- giving both old and new evidence the appropriate level of consideration, and therefore changing beliefs exactly as much as is warranted.
The Activity on ClojureScript is Phenomenal
Facebook Is Your New I.D For Social Good
Many RSS readers these days are pretty good at feed discovery if you just give them the blog URL. At least, both Google Reader and Newsblur (http://www.newsblur.com) seem to be able to dig up a feed for anything I've thrown at them.
"The prevalence of social bubble-worthy companies whose value propositions are little more than "cat pictures" suggests an inflated sense of self-importance among the founders, and I can't expect to keep my level of enthusiasm in line with their irrational exuberance."

i totally loled :)

organizations that expect unreasonable working hours from developers or sysadmins are a bad place to work. the only places i consider it somewhat reasonable to work employees over 50 hrs / week are professional services firms where the firm is actually gaming the billable hours of the employee involved.

remember that you have a choice about the amount of hours you work: don't let yourself get into a position where you're being chided to work countless hours. a good manager knows that working most employees over 40 hrs / wk leads to lower quality work product, but as i mentioned above, the only place where this consistently translates to revenue is a prof services firm. ppl are more likely to commit errors and generate crap product once you push them over an 8 hr work day. this is not to say some ppl can't work a 16 hr day and be nearly twice as productive as an 8 hr day worker.

don't get discouraged and don't let ppl push you around with respect to the hours you clock. i'm sure you'll find somewhere that fits you better than behemoth X.
That's just a bug. It will be fixed (there's even a patch in https://bugzilla.mozilla.org/show_bug.cgi?id=752877)
I'll be honest, I downloaded the CAM version and it was crap to me, and someone had mentioned it was a great movie, so I went to the theater to see it because I didn't want to miss out.

I think the guy who released that CAM might have been doing the movie studio a favor because it might have made the next guy feel like he didn't need to do his own upload which might have been better.

If there was a good version available when I went to pirate it, I wouldn't have dragged myself to the theater.

I wanted to buy a large popcorn and soda with my cash when I got in there, but I only had $12 so I had to put it on the card.

I just wish they would release stuff on Amazon or iTunes (although I hate that program) the same day as it comes out.

Anyway, I spend way too much money on Amazon videos.
Yep. Its already a standard! What could possibly go wrong!

Seriously. Solving purely social problem with purely technical means is just doomed.