skysight-inc/HackerNews huggingface dataset:
One of the biggest traps self-taught developers fall into is not recognizing (seemingly) complex problems have likely been solved before.

A simple example in Python:

for dog in dogs:
print dogs.index(dog)
calculate_dog = something_complex(dog)

vs.

for i, dog in enumerate(dogs):
print i
calculate_dog = something_complex(dog)
Who cares? IPv4 is a dead technology and this is like complaining that the UK has a bunch of fax machines in storage somewhere. 10 years ago, this would have been a waste. Now it doesn't even matter.

Even Comcast supports IPv6.
Genes for face shape identified
Or, you know, secure the airport properly to see nothing bad or unusual is happening...
GC is an abstraction which, although complex in implementation, is something which makes your program simpler. So the correlation has less to do with how our tools are implemented, but the properties of the tools as we interact with them.

Also, simplicity, like security, is a trade-off. When performance is paramount, people will reach for C or assembly, and rightly so. Conversely if performance is not the #1 priority, developers feel free to use higher-level languages like Java or Ruby.
Making A Better Internet: A Story In Three Acts
I'm in the opposite situation.

My ISP and wifi router support IPv6; but my modem does not.
And without this modem failing, I probably won't shell out $150 for a new one.
According to [1] there are a few - no big names, though. As [2] says, running IPv6 is fairly boring; you get access to the same web as everyone else.

[1] http://www.sixxs.net/faq/connectivity/?faq=native&countr...
[2] http://bens.me.uk/2011/adventures-in-ipv6
I think you're missing the point. He didn't ignore the suggestions, he felt that particular suggestion to restore the entire phone was unacceptable. Just because Apple says to do it, doesn't mean it may be the absolute best solution so the author went about finding other possible alternatives among the community. Unfortunately, beyond jailbreaking it there was no other worthwhile solution. In the end, he did exactly what Apple told him to do... and it still failed.

Now what?
You are correct for laptops (for now, anyway). For tablet form-factor devices, UEFI will prevent other OSs from being installed.
Well, I wouldn't phrase it that way, but it's not a fallacious argument.

If I were to rephrase, I would say, application developers aren't full stack developers.

Modern languages and frameworks hide a lot of complexity, allowing application developers to focus on business problems, which is a good thing.

But if you want to continue to grow as a programmer, and understand the tools you use, or use them to maximum efficiency, understanding things like Big-O analysis are crucial.

I don't often do complex "math" or analysis using Big-O... but understanding the core tenants are crucial, especially as you move from building apps to building frameworks themselves.
Yikes! Looks like I'll take Mopac into downtown today.

Hope the threat doesn't amount to anything...
It seems like a pretty straightforward MapReduce, though I agree that if you're doing searches repeatedly or your data is small enough you should use a database.

(map = search a partition and return top k results, reduce = combine multiple n*k result lists into a single result list)
Hey, some of us HAMS are still using AMPRNet ... not many, but some.

That being said, here is a list of people in charge of allocations: http://www.ampr.org/oldsite/amprnets.txt
Why should this video be any different?

It's not: those are also examples of censorship.
Whelp, that certainly makes knowing which chip to buy a lot easier.
Resistance is futile! It is a slick language. It hit version 1.0 in March, which is probably why you're hearing so much about it now. Its concurrency model lets you keep all the machine's processor cores busy, without you going insane; that's worth the price of admission for me.
I think this is just it though. You don't necessarily need to be able to sit down and formally write out the exact amortized big O complexity, (or little O, [O|o]mega or theta) but equally it's good to have some idea of how something would scale.

I feel like self taught developers who are serious just learn this by intuition because, frankly, if you're writing software where it matters then very quickly it becomes an obvious concern. If your self taught and it doesn't matter then it doesn't matter!

With a formal background you may or may not use it, but I'd say the only difference is knowing the formal notation makes talking about it with other programmers who also know that notation easier, but even then it's not like algorithmic complexity is (at it's heart) at particularly difficult concept when directly applied to a project. I always found it much harder as an abstract idea rather than when working with a specific algorithm.
100x the original price as punishment for very low cost products where infringement is hard to catch doesn't seem unreasonable to me, no.

Staying too long in my parking space costs me about ten times what I would have to pay otherwise, and that's an offense that's easy to catch.
>"presently not provided by the Linux kernel"

How long until the commits start rolling in for this?
I've got the impression that most of the phone internals has been updated. I prefer that to cosmetic design changes for it's own sake and gimmick features that isn't yet established and/or used by many. I like what Apple bring with it's media expertise and the added hardware image processing and panorama photo.
Also, I would say that Whitespace being "simpler" than Python is a fallacy, or at a minimum a reductive reading of the word "simple." I doubt the rules for writing in ASM, C, or whitespace are all that simple, despite the building blocks being relatively simple or few.

Honestly, I'm just repeating variations on http://www.infoq.com/presentations/Simple-Made-Easy.
It was only 73 recorded deaths starting from 1946. This would be one of the crappiest cost/result ratio in lifesaving efforts in the history of humanity.
This kind of story seem to come up over and over in the programming world. I'd like to add something from my experience working in large development companies.

The first months or so, it's perfectly understandable that a new developer doesn't "get" the application, how it works, or even what it does. The myth of the ninja programmer turning things around, applying a mix of beautiful elegance and sharp efficiency to save the business big bucks, is just that, a myth.

Actually, during this period, a new recruit should focus on one thing only: survival.

Deliver the mindless code, even if it doesn't make sense (or seems plain wrong), but deliver it on time. Do not slack off on your hours, show up (at least) ten minutes early and leave (at least) ten minutes late. You may be the genius programmer who delivers in an hour a day's worth of an average programmer's productivity; but now's not the time for cleverness. Now, I repeat, is the time for survival.

It is also the good time for getting to know (and being accepted by) your colleagues and your direct managers. Coffee/cigarette/you-name-it breaks are important. Do not miss those.

So when do you get the chance to behave like the great programmer you always thought you were? From experience the milestone has always been the same: The next batch of recruits (which in my case has always been around 8-12 months in large enterprises).

As soon as you're not the "new guy" anymore, things automatically change. Not only have you already earned the acceptance and trust of people around you, but you've also seen enough of the code and interacted enough with business analysts. You have much more elements in hand to be creative and take initiatives.

In short, I'd add one thing to this article: Be patient.
It's true that you can never see the whole picture, but as time passes, you can definitely detect the places where you can have an impact. Until then, you simply have to turn on your survival mode.
Don't property rights trump free speech rights? (IANAL)

Legally? Free speech has a right is mostly about freedom from governmental interference. Private companies usually can censor whatever they want.

But I'm pretty sure people are discussing the moral aspect of this, not the legal. And one can consider that Google shouldn't do this, even if they have the legal right to do so.
> Haskell actually has three (or four) competing exception handling mechanisms nowadays.

Yeah, knew about Either in general (see my top-level comment about sums vs. products), just not the monadic bits around it (MonadError and ErrorT, in particular).

> If you use the Either error result approach, you can conceivable put a stack trace (or something similarly identifying) in the Error data-type, so you can avoid the "Where did that NaN come from?" issue.

True - even just making exceptions take a Loc parameter seems like it could be a good step, but that would be basically requiring TemplateHaskell, which would ruffle feathers for sure...

> I think we need to see Algebraic data types in more languages, before we will see this approach used more often. (In my opinion algebraic datatypes and the pattern matching they enable rank in the same league as garbage collection in that they are a feature originally invented in and for functional languages, but useful outside as well.)

I agree wholeheartedly. Lack of easy-to-use algebraic datatypes is my biggest pain-point in languages that lack 'em.
This includes an example Scheme interpreter, so it's finally possible to see MPS in action.
IBM has an entire /8 that they use internally for addressing their computers, none of them are publicly routable or even publicly accessible.

Even if they were to start announcing them or selling them it would be a HUGE project for IBM internally to make sure that their computers aren't going out on the web for internal resources, and it becomes an huge issue of having to renumber.

Unfortunately there is no good way to support something like that. Some companies didn't need to use the private LAN addresses because they had their own /8 and changing it now would require too much effort and work.
Faces in stop-motion films are now made using 3D printers
It should be possible, but I guess airlines probably aren't keen to spend money on something like that since they won't see it as their problem. Their paying passengers aren't the ones dying.
>So, there is no other phone that can beat its design and construction, but "is it enough"? Is being the best enough?

The Nokia N9, Lumia 800, 900 and 920 are pretty well built and designed too. If you haven't, try going to a store and playing with one.

Coming to the design itself, it's tied in with fashion and at this point the design has not changed(except for the new back) since the iPhone 4 over 2 years ago. Design and fashion do age. The iPhone 4's design was a leap over the 3GS and combined with other features warranted a new version number, while this iteration feels that it should've been named iPhone 4X, X for extra long. Why get a new iPhone 5 when you already have an iPhone 4 or 4S and can add a Galaxy or Lumia and keep the old phone around as a iPod Touch music player?

Also, even if the design is superlative and timeless, for many consumers it is just one factor. The other factors are raw power, technical specs, camera quality and features(which the Lumia 920 is going to have a head start on). If the iPhone 5 cannot compete on specs with this years phones, what chance does it have with the Android phones of the next year?

However, there's another bigger factor that I previously commented on:

I think their problem right now is that users' choice is overwhelming them and the one-size-fits-all approach of the iPhone has diminishing returns after a point. The variety, choice of screen sizes and price ranges of the competition is only getting better by the day.

A new iPhone is released only once a year, so it better be very good with a lot of new technologies, features, new designs etc. for sales to last all through the next year. iPhone 4S sales started lagging in the 3Q itself this year, compared to the 4th quarter for the iPhone 4. This is because people start waiting for the next version or switch to the competition because they have better specced devices with more features. I think Samsung timed their Galaxy S3 launch perfectly to coincide with the iPhone 4S getting old enough to beat, and they beat it in monthly sales for the first time, which is a noteworthy thing in itself.

The whole situation is reminding me of the PC wars in the 80s, where Apple had a seemingly unassailable innovation lead, and then squandered it away by offering limited choice and higher prices, while Microsoft very smartly licensed DOS to Compaq and others like Dell and HP, and the rest is history. Apple's marketshare is now 17% vs. Android's 67% which is about 4 times more. No wonder Apple is going crazy with the patent war against Android. That's probably their only weapon against the equivalent of the attack of the hordes of beige boxes' that previously took them down.

The iPhone 5 is good enough to get great sales and beat all sales records ever, but the key is how well it does starting about 6 months from now.
You can breath pressurized air directly from an air mask without wearing a pressurized suit. Many military aircraft use this system (the air mask is strapped tightly to the face to maintain pressure).

I'm sure at some point you need a pressurized suit to make breathing possible, but it likely has more to do with preventing decompression sickness and protecting against the cold (at very low pressure the moisture from your skin will rapidly boil, cooling off your skin).
Developement links of the week (I)
Exposed Vocals
Exposed Vocals is the YouTube for Unsigned Artists! URL is incorrect - should be www.exposedvocals.com
Web development is 99.999% based on fads. This is the current fad.
Sector/Sphere is what the Sloan Digital Sky Survey uses.

Instead of supplying map and reduce routines, you implement generic "user defined functions". This gives you some more flexibility about how the work is handled, though if you want to just implement map and reduce UDFs, it supposedly gets better performance than Hadoop.

It's also designed to support distributing work over WANs. I think Hadoop really wants every compute node to be on the same LAN.
I've seen CS degrees do these kinds of things as well.
FILTER_VALIDATE_EMAIL probably is a smarter way to go, but I think context matters a lot. If this is for a consumer web service user@hostname isn't going to be 'valid' for the service.
>whether it is the "true" driving factor behind the attacks

Can't you see the analogy between my scenario and this scenario? You make it sound as though if the video was the true motivating factor, then it should be banned. This is analogous with the Catholic mass in my scenario - by following the same logic, if the mass were the true driving factor behind the atheist's violence, then the mass should be banned. You can't let threats (or acts) of violence influence what is protected speech and what isn't.
The Architecture of the Mighttpd High-Speed Web Server
A silly, trivial article with major errors or questionable fudges in basically every paragraph.

The writer says the phone can be summed up by an extra row of home icons; there are in fact improvements to many hardware and software facets of the device. One may not think the improvements are major, but denying their existence temporarily to make an argument is silliness.

He then gripes for two paragraphs about his own personal impressions about how Apple presents products, including one paragraph griping about a guy who is now dead, and thus presumably not responsible for the presentation in question, i.e., the iPhone 5 presentation.

In the next paragraph, more whining about presentation, plus a blatant lie, saying "Apple tried to convince us that it had stolen a 16:9 display from the gods". Apple did no such thing. I watched the entire 2-hour event. There is not a single boast about Apple magically creating 16:9, originating 16:9, or any other such nonsense. In fact, 16:9 was barely mentioned. At all. The writer is simply making it up.

Then griping about a Jony Ive video.

Then silliness about how "Thin and light smartphones were an exciting concept a couple of years ago"; perhaps the writer hasn't noticed, but thin and light has ALWAYS been a driving concept in smartphones and basically every other kind of portable (and even non-portable) tech design. It has always been an issue and will always be an issue. So when someone makes something circa 20% thinner and lighter, yes, that is noteworthy. It will not change the course of planetary history single-handedly, but it is notable.

He then lies about the hardware, saying that "you would be hard stretched to find any new features except for the single-chip GSM/CDMA/LTE radio". But that's not true either. The CPU is reported to use A15 cores, which would make Apple first to market, but all the writer can do about that is boast of some vaporware product using the A15. The writer ignores the camera upgrades, the speaker upgrade, addition of an extra mic, etc., etc.

Later in the article, he gets the software wrong too, talking about how iOS will use the additional screen space: "Rather than do something interesting with this space, though, Apple will simply letterbox all 3:2 apps". That's already untrue; Apple has already redesigned the OS and its own apps to do interesting things with that space, and third parties who make major apps will of course do full redesigns in most cases too.

The author then makes a hilariously bad statement about why Apple made the phone thinner: "It seems like Apple felt compelled to increase the iPhone’s screen size, but at the same time it couldn’t summon up the marketing cojones to introduce a phone that was both larger and heavier than the iPhone 4S."

Yeah, that's right. The author is actually saying that the phone is lighter and thinner because of Apple's lack of "marketing cojones".

It's just hilariously bad writing and control of the facts, all the way through.
In this context self-taught obviously means: didn't pursue computers in secondary education. I've learned way more about development post college, but I wouldn't call myself "self taught."
The entire iOS app ecosystem has been built upon the idea of 'pixel perfection,' and now this historical focus on perfection has ironically put many, and perhaps most, iOS developers in the position of having to modify their apps to support a growing variety of specific-to-the-pixel screen resolutions.

In the interim, users have to put up with ugly artifacts like black bars and up-sampled graphics.

--

PS. The Android team's decision to provide from early on a resolution-independent GUI framework that automatically uses all screen real estate, regardless of resolution or aspect ratio, is looking smarter by the day.
Intel declares Clover Trail Atom processor a “no Linux” zone
I'll evade your difficult idea with a more pragmatic rebuttal: give almost any government in the world some legal speech model like what you describe, and you will be in prison for spreading the "false, dangerous delusion of atheism". The inability of government to determine, and enforce, truth is the only thing protecting your highly unpopular beliefs from censorship.

Free speech is in principle the right to speak the truth; in practice it's the right to assert falsehoods which enables it.
Sometimes it feels that the more you know about "the system" as a whole, rather than your section, the less likely you are to be pigeon-holed into one role or another.

This can be both a positive and a negative - your career won't follow the normal "developer to senior developer to team lead" path, but you will end up being given tasks as a developer that would normally be assigned to someone with a much more senior job title would get.

The negative is that getting paid for your extra knowledge is extremely hard, and your extra knowledge it worth much less outside of your industry (or even outside your building), so moving jobs won't help so much.
Exposed Vocals
The YouTube for Unsigned Artists. Upload, stream and share music videos for free!
Mike Daisey: Don't pre-order the iPhone 5, the ethical choice is to wait
I don't agree with you on that point. Android layouts are designed from the beginning to handle different screen sizes and proportions, pretty much like html. One of the iPhone's strong point has always been that you can design "pixel perfect" apps, so that your design is exactly what users see (as a contrast in Android you have to define "points of stretching" for your screens).

The point here is that you have to create a new layout for the iPhone 5 (if you don't want your app letterboxed) and this adds an extra layer of complexity to the development. Seeing that there are also rumors about a different form factor iPad you would then have to maintain 6 different layouts (standard/retina/16:9 for iPhone, standard/retina/new layout iPad). Well or 12 if you have specific landscape layouts.

Designing UI on Android apps can be a pain since you don't have the "pixel perfect" paradigm, which is a common criticism on Android from iPhone developers, but if you manage to get them right you can get away with a single xml layout (of course, you can able to make things more complicated).

It seems to me that Apple are getting themselves in a bit of a mess with this. The tradeoffs with the "pixel perfect" method haven't really materialized until now.

Maybe I'm just being over pessimistic with this and it will be a non-issue, I really can't tell at this point, but I see this as the greatest issue with the iPhone 5 (which in turn is probably the reason they didn't increase the screen size earlier).
I'm pretty sure that military pilots have to go unpressurized to 25,000 feet in order to be qualified. however they don't have to stay there for very long. and certainly not as long as the duration of a commercial flight.
Serial iPhone and Mac hacker Charlie Miller takes job at Twitter
Six months of Paper: sketching the future of app startups
FireFox OS Gains Traction and Major Carrier Support with Sprint
I did not see statistics on # of people stopped, # of people who were deterred, and less than a 100 succeeded in hundreds of thousands of flights.

Attempting to stop people or bombs in under carriage would EXACTLY BE SECURITY THEATER. That is an overreaction to insignificant but recently hyped/fear mongered threat that results in no statistically significant reduction in risk. But, writes up good in the papers.

People thinking like you are why security theater can exist.
If this is for a consumer web service, user@existing.dns for a non-existing mail box will be 'valid' according to this link, but still completely useless.

Please see the link I posted.

1/ Using PHP PCRE for email validation is considered harmful

2/ Using filter_var for email validation for a web service is useless

3/ Sending a confirmation link by email is the way to go
These Working Gadgets are Made of Bread
I see that it would be a lot of work, but so will switching to IPv6 be. The question is: which will be worse? which will actually happen? I don't know.

I'm probably forgetting a lot of things but to me it would seem doable to switch to private LAN addresses using DHCP and NAT, as long as there are no hardcoded IPs lingering around (but only hostnames which can be updated in a central location).
The world is flat, didn't you know?
http://mathdotrandom.blogspot.com/2010/12/block-ads-on-pc-an... this should probably appply to iOS too...
How many graduates are:

1. From Harvard
2. Making over 100k
3. Have a house
4. And a retirement account
5. Have 1300 a month in disposable income.

This is pretty much a non-story.
And that, kids, is why you want to look for a rootable, reflashable phone.

Don't look at me like that. My sister's phone is rooted. Same for the guy at Radio Shack who sold me my last phone. Neither of them know shit about how to do it, but they got someone else to. Rooted and re-ROM'd smartphones are a pretty hot commodity these days.