skysight-inc/HackerNews huggingface dataset:
Apparently not, I personally find the phrase "2000 line function" offensive but that part isn't censored.
Node v8 memory limit is the big problem for me http://stackoverflow.com/questions/7193959/memory-limit-in-n...
Sometimes I need to move data outside heap memory - Buffers etc. Looks like chakra have no such problem.
Personally, if a CSR is up front about what went wrong, what they did to try to fix it/what they're doing to get it fixed, I'm a happier customer. I've worked in enough large organizations to understand how difficult things can get when navigating multiple departments and multiple people trying to get some corner case situation cleared up.
Unhappy Meals (2007)
the pyramid is sponsored by Greggs.
Why Elixir
Even as someone who uses the newer languages/frameworks, I wish I could upvote this statement multiple times:

"It's not sexy, it gets the job done, and I know it'll run for at least 5-7 years with minimum hassle."
Slack publically admitted this. Saying money was cheap so they got a lot of it.
I'd like to hear what Bret Victor would have to say about these ideas.
Is it really? The military has been using camo to spoof image recognition since forever.

But I guess if this is for drops then camo wouldn't apply?
Some are regular people

Most are people that should not have stopped taken what their Psychiatrist has given them (or should go to one given the chance)

And let's not forget the scammers, of course
This thread is officially dumb. One guy miscalculates 75 Mbit as ~75 MiB, another guy fills ~70 MiB file with ASCII "1"s.
> The testing of a GPS-free version of JPADS is yet another example of efforts to develop alternatives to satellite guidance. “GPS is very expensive to launch and operate,” Defense Secretary Ash Carter said during an April 24 podcast from Silicon Valley, according to National Defense magazine. The global positioning system, he said, “makes us vulnerable to attacks, it is impossible to use in the valleys of Afghanistan or in a big city [where signals are blocked], or in places where the signal is poor.” “At DoD, we worry about enemies jamming GPS signals.” Army Maj. Christopher Brown, who helps run the service’s efforts in position, navigation and timing, or PNT, told C4ISR & Networks last year. “Threats to military GPS have evolved and improved at a rapid pace — from a proliferation of small-scale commercial jamming devices that can readily be purchased on eBay to large-scale military anti-access/area-denial (A2/AD) capabilities.”

So the real benefits here are: works in mountains, and future-proofs against better GPS jamming.
I agree. But I'd also say that it requires a bit of domain knowledge to know what you don't know.

That is to say: I know what I don't know in the fields that I study/practice in. I don't know what I don't know about the fields I don't.
He can, but chooses not to.
Been living in Overland Park, KS for 20 years and can say that the bust did not affect this area, but there was never a boom either; just steady growth. I can see how Wichita was screwed from aviation downturn.
Well presumably VR is a better solution for space navigation than having a windowed cockpit if we're on that subject already :)
Pft, 2000 lines :-)

What you do is that you:

A) Realize that there might be years of hidden bugs, but also fixes to complex problems, speedups, kludges, weird changes to requirements, etc, hiding in the code, so even really creative unit-test might not cover real-world edge-cases.

B) Take as small bit as you can, and just refactor out the smelly code into smaller parts. Often a good name around smelly code helps a long way.

D) Iterate. Until good enough.But not more... Maybe you have more important things to do than rewriting ugly code that works.

There is a big risk that since you probably won't understand everything that goes on, and why - you will break something important.
I don't know. I would think it was kinda neat because I got alot of respect for Elon but I would also kinda wonder about the extra mileage.

EDIT: Message to the down voters I am not saying its rational that I think it would be kinda neat. I am just honest enough with myself to recognize that I am not a purely logical beast.
Using Triggers on Schemaless, Uber Engineering’s Datastore Using MySQL
They've built over 100,000 vehicles, built out a massive nationwide charging network (plus a huge network in Europe and a decent-sized one in China), produced the best highway auto-drive system available today, and currently have the best selling car in their price segment in many areas.

Yes, clever doors and gimmicks like their new Summon feature aren't worth the hype they put into them, but that's not the only thing they're doing.

That's not a hobby company by any stretch of the imagination. Yeah, they have problems. Specifically, communications during the delivery process has always been troublesome for them, and there's no reason it should be. But that doesn't make it a "hobbyist organization." That's just silly.

I mean, GM's failed processes meant that their products spontaneously shut off and killed people, and they sat on their hands doing nothing while people were still dying, but we don't call that a "hobbyist organization...."
Image Copyright Infrignement = Invoice
I have a not-for-profit client that posted a image of a Las Vegas hotel on their website (where they are holding a conference). The hotel provided the image, but it turns out the hotel didn't own the rights for the image. We revived a $900 invoice from the image owner (Destination360) threatening a lawsuit. We explained the situation and agreed to remove the image, but they still want the $900 or else. Should we pay the $900? There was no previous DMCA notice or any other previous contact. I know this is not a legal forum, but others may have had similar situations.
Slowly and carefully, like you're defusing a malfunctioning clockwork bomb.

1) Understand at a very fundamental level what it does (there are probably multiple things).

2) Understand at a very fundamental level what it does (this is really the hard part)

3) Document your hard-earned understanding (tests, ironically, do not work well for this, since there are no fundamental units to test at, and there likely is a metric ton of shared state)

4) Refactor it into something easier to understand and test.

I've had to work with a similar 5,000 line C function at the heart of a DSL parser; literally the core of the entire business. Changes were made very slowly, and with a lot of consideration. Refactoring is still underway 6 years later.
How to Ship Side Projects
This is true, but microsoft has a particular history of malice few other companies can match.
https://news.ycombinator.com/item?id=10929525
I would add landmarks and do small refactoring within the function until I'm confident in my ability to start splitting it up into smaller functions. This should happen naturally as you make changes and add new features. However if you're not in the function enough to make this happen then it's probably not worth refactoring to the business.
Maybe its because I'm a JavaScript dev, but I seem to clearly understand the critique (vs maybe if you are a Ruby dev it just sounds like "I don't like it"): too many built-in methods, lots of magic behavior, and an over-reliance on syntactic sugar. Seems pretty straightforward.

Possible non-code-altering solutions to the problems include: 1) limiting educational material on Rails to only use a subset of the built-in methods so that newcomers aren't overwhelmed by feeling they need to learn the entire std library before being able to make progress, 2) Using more explicit versions of code vs the more terse but harder to understand versions enabled by syncretic sugar to ensure that people coming from other languages first understand what is going on, then are blown away when they discover you can write it in an even cooler way, 3) a deeper explanation of what is going on under the hood to make the magic seem "OK".
Chakra only works on Windows. They have on their roadmap plans to work on the interpreter on other platforms, but nothing about getting the JIT running. So I sincerely doubt we'd see a switch.
When you have a shitty dealership, you drive somewhere else in town to buy a car.

I went to five different dealerships when I bought my car. Three of them were shitty / scumbags. The last two were good, and one offered me a better price.

The benefit of the dealership model is that customer service is decentralized, and different dealerships even offer different levels of customer service. Some offer free tuneups for life for example (and seem to factor that into the cost of the car). I went for a dealership with a lower price, since I expect to do my own oil changes / basic maintenance.
Are you saying that the people who died ran without any preparation?
At least it wasn't a loss, besides time and mental anguish.

But yes, it's extremely weird that they didn't just immediately apologize and offer him a nice discount on a different car.
In general, the data is exactly what you'd expect: people with some college out earn those with none.
A couple years ago I built a digital signage application using the Chromecast. However, it was very apparent that it was a terrible platform for digital signage.
The Chromecast is designed from the ground up for sharing content on a TV. It is not designed for a 'kiosk' type of situation where the device always boots to your content.

With these limitations, I built a digital signage app based on Chromeboxes instead (http://metascreen.io). The Chromebox has a 'kiosk' mode which allows you to specify which app should run when the device boots up (very critical for business digital signage).

If you are looking for something super low cost, checkout digital signage solutions based on the Raspberry PI. Would fit your expectations nicely.
1. Unit tests. Otherwise modifying old code is full of potentially unforeseen landmines.

2. Read the function a few times to get a sense of what it's doing.

3. Break the function into blocks of statements that are performing a related task.

4. Factor those out into smaller functions.

5. Recursively repeat 3-5 until you're satisfied with the new functions' line count.

> Should I tell my manager that the function needs to be refactored and take time to refactor it?

It's absolutely worth mentioning. Time estimations are one of the harder tasks of Software Engineering. Being up front with your manager can help better set expectations.
He consults on Riemann? I was under the impression he wanted nothing to do with helping people use it, and is just a general consultant. Like, he's not trying to support Riemann, he built it because he needed it. Maybe he's changed his mind?
Why would you need to unlearn it? Simply write code as you would write it in a case sensitive language.
One of the things I noticed was the covering the holes with paper changed a lot the tone of that instrument but very little the power of it.

That's why violin mutes, which allow a violinist to practice quietly, attach to the bridge...to reduce the transfer of vibration to the chamber via the sound post and bass bar...
Are you me? My life seemed to slowly "fall apart" after college, and after I began working in the full time world. From the outside in, I am a wonderful success. I have a great job, enough money to be comfortable. I travel, I hike, I golf.

But I can't help but feel like it's all wrong. Work hard for what? So you can amass enough money for when you're too old to work? That whole way of life seems counter to the "life is short" argument. Because of that, I find myself needing to constantly move on, ever searching for something truly fulfilling. Work seemed to fulfill me for 4 years or so, but I feel like I've achieved what I set out to achieve, and now it is hollow.
HP's “PC LOAD LETTER” UX fiasco – how did they allow it? how to prevent?
Arch seems to be kosher

$ uname -r
4.3.3-2-ARCH

No root:

$ ./cve_2016_0728 PP_KEY
uid=1000, euid=1000
Increfing...
finished increfing
forking...
finished forking
caling revoke...
uid=1000, euid=1000

Only took about 25 minutes on a Lenovo core i7. That's kind of scary.

EDIT: Actually it seems that atomic_t is 64 bits long with x86_64 these days, so no hope of overflowing.
> Progress over stability

> We have to dare occasionally break and change how things are to evolve and grow.

> ...harder to swallow in practice. Especially when it’s your application that breaks from a backwards-incompatible change in a major version of Rails. It’s at those times we need to remember this value, that we cherish progress over stability...

I encountered this doctrine first hand. A division of a company I worked at had its division's website rewritten in RoR by some outside consultants. Even brand new, it was a mess of Ruby gems of conflicting dependencies which was undeployable. The build system was a train wreck as well. Some of the main web pages of their web sites like rubygems.org were not available - the web site had "progressed" and when you clicked on a link, the page explaining anything had disappeared. I mean hell, go to rubyforge.org this minute (1:15 PM EST) - it is down, of course. The blog of the author of the Ruby gem that then was the main gem that handled web serving did not inspire confidence.

As I would have to maintain it (as a sysadmin, not programmer), I refused to deploy the system, since it was an unreproducable mess of conflicting gems and gem versions and kludges. They decided to pay the RoR consultants additional money, despite them having never delivered a working system. By the time I left, it still was never deployed. The division closed dozens of offices soon after, and then the division shut down - perhaps not completely related, but probably somewhat related to this project.

Meanwhile, the company's other divisions had decent programmers programming for Java application servers, and that code and those servers were much more solid. Builds rolled out easily (and could easily be rolled back if need be). It was really night and day. It makes sense this contempt for stability is explicitly part of their doctrine.
Indeed.com, Craigslist and maybe Linkedin.
You could start by writing comments. There is little chance of any bugs coming from that. If there are any tests available then you could work on understanding the tests and then step through the code in the debugger. Hope that helps.
How to Hypnotize Yourself in Under 3 Minutes
It's important to remember that ChakraCore only currently builds on Windows, so this is only for Windows Node.js builds.

The ChakraCore roadmap [1] shows that they plan on porting the interpreter to Ubuntu, but not to Mac OS, and they don't plan on porting the JIT. So even it does go Windows + Linux, it will still be a low-performing toy on Linux.

This is vaguely interesting from a technical point of view, but doesn't seem like it'll majorly impact the future of Node.js, except maybe as something Microsoft can offer for Azure customers that choose Windows Server.

[1]: https://github.com/Microsoft/ChakraCore/wiki/Roadmap
The Not Very Smart Home
You're sure it wasn't Buttle?
While the "Buy Pre-Owned Today" option is given equal weight on the website, I specifically am referring to what happens on the back end. When you buy new, a new car is configured to your liking. I have to imagine Tesla's fulfillment operations are arranged primarily around this case (take new "shell" car, install customer-selected options, deliver to customer).

It's the same process only in what the customer sees. And I'll agree that the customer should get a similar experience from a similar process. Tesla seems to have failed in this case. However, it's clearly not the same process on Tesla's end. Selling an inventory car is a subset of the pre-owned car sales process, and selling a specific inventory car that was somehow (erroneously?) available for R&D is a very specific case. Has the car been made road ready? Have they removed any beta features that are not for the public?

This is a special process. However, since Tesla offers the option, it is their responsibility to ensure they can deliver.
I may have been projecting. I apologize.
For a function with 2,000 lines of code, we have to be honest with ourselves and accept that testing will never be sufficient; if there's 2,000 lines of code, you can bet good money that there's global state manipulation as well.

Making the assumption that anybody is capable of sufficiently testing such functions and subsequently re-writing them will only introduce new bugs and old regressions.

Seems harsh, but I've had to work with a few such monstrosities. Global state galore.
Pretty much. Would you work as hard or take as much of a paycut if you got virtual lottery tickets instead (lottery tickets that even if you win may not pay out since VCs have a higher priority stake in them)
Where a function ends and where a function starts is somewhat artificial. For example, if this were BASIC it would be just be a label.

I would read the thing a few times and figure out exactly where to add the functionality. Refactor second, if time permits. If the thing is 2k long clearly, refactoring it isn't a priority.
Can you explain what you mean by this comment in this context?
Yeah, that's pretty weird. People experience this problem all the time with dealerships: you call up and make a deal on a car, they "hold it" for you, you get there and it turns out the car you wanted "was just sold" but the dealer is happy to sell you this other one instead, which by the way is several thousand dollars more expensive.

At least with Tesla, you can be pretty sure that Elon Musk actually did take this guy's car. The dealers will just lie to you; in the scenario above, they typically never had the car in the first place.

I'm not defending what Tesla did here in any way, but this problem certainly doesn't make a case for dealers.
Er... am I misunderstanding or is everyone else?

Tell your manager that you want to refactor it. Just don't tell your manager "it's shit".

The "don't say it's shit" was when speaking to the manager... not using it on your thread. Unless I'm the one misunderstanding the statement...
How to get AND keep a job in Industry after a PhD
> they're also indicating that there's clearly nobody enforcing ownership or accountability for reported issues.

Based on gossips about how it allegedly is like to work for Elon Musk, it might be that people are even more scared of reaching out to him than to violate the process.

Which is a deadly issue: when people are too scared to give honest feedbacks to their CEO, the CEO stops knowing how his company actually runs. Parallels can be made with soviet countries, run through the deforming lenses of five-year plans and fantasy reports.
If I was Elon Musk, I would promote that guy and put everyone else in "hot water" for not escalating this issue.
> They're obviously very good at engineering

Everyone's very good at low volume. I'd say wait for the mass-production model (ie: Model 3) before we judge their engineering skills.
I believe that number includes casualties caused from retrieving the package, but it still seems high to me too
I loved the KLF. After reading the The Illuminatus! Trilogy I was facinated with the idea of how much freedom you could have in our society if you just stopped following unenforced cultural norms.

Bands like the KLF were a huge part of my early 20's.

The entire "Andy Kaufman" method of turning society and the media into your own private playground always seemed like the highest form of humor to me.

I am beyond jealous of your experiences!
I didn't intend for that to be a negative, just that it's a different point in it's life.

I'm not trying to make any argument about Rails, but am very interested in your opinion. Has it accumulated cruft? Is it missing something that newer frameworks have embraced?
Yes, you can use HTML/CSS rendered views on mobile but they pale in comparison to native UIs.

The latest app frameworks decouple client-side application logic from the view rendering layer. Meaning you can use the same application logic on your web app as you use on mobile EXCEPT the view on mobile will be rendered natively. Not through a hacky, slow, inconsistent embedded web view. Native native.

If the approach is successful as the framework devs expect, mobile app development (and the app ecosystem as a whole) will go the way of the dinosaur.

Pulling data from many sources on the server requires proxying requests to third parties and providing inline caching of the responses for performance reasons. Despite the fact that the source you're proxying to likely already implements their own caching strategies.

Have fun addressing bugs caused by cache invalidations when you're dealing with multiple caching layers.

Not to mention the increased memory/computation footprint incurred from hosting the equivalent of a database view of an entire third party service on your backend.

Or, you could just request the data directly on the client side.

That's what I mean when I say 'reduced complexity.' Unless you consider setting up CORS whitelisting and some AJAX requests to be really difficult. Then, carry on.
I'm presuming you've researched tiling window managers as part of your work on this?
IBM Corporate Song book
I have requested an invitation for both my personal and work email addresses. I seem to have an account for my personal address but I can't for the life of me think how this happened. I don't have any emails from you... Really odd? Anyway, regards the work account - how long till my invitation is actioned.

And no - Homepage isn't too simple. It's great.
I like this direction. Now that my primary personal laptop is a MacBook Air 11" (and my wife's is a 13"), I find we both use full-screen apps more frequently than on larger monitors. But, it doesn't feel like the OS has kept up, and the full-screen experience is less than ideal. Apps continue to open in windowed mode, and I have to resize or full-screen them. Swiping moves me from desktop to desktop, not app to app. Take some of the app-switching work that is now present in OSX and roll it into OSX (or Windows). I haven't put a lot of thought into this - I just know the OS "desktop" no longer feels like it works.
For those of us who were stuck with the JVM, fortunately there's now Grails (obviously modeled after Rails). Groovy makes programming for the JVM fun IMO.

I've used Groovy/Grails for a number of web apps, both in commercial settings and side projects. Since I had previously been doing a lot of Java, being able to leverage the existing Java ecosystem and libraries with Rails-like productivity was a huge plus.
Great points. This is very much aligned with my experience.
We will, Ian is already working on it.
E-mail notification failed according to Professor Curtis Cooper in interview for Matt Parker's "Standup Math" youtube channel:

http://m.youtube.com/watch?v=q5ozBnrd5Zc
i don't see how that would matter. Do women divvy up their complements equally between men and women? I bet not.
I would say yes, as long as you're building a greenfield project that is a database-driven web application, where your priorities include high productivity and quick time-to-market. It's basically been the default choice for web startups for several years now, lots of startup devs know it, and there are battle-tested libraries available for just about anything you want to do with it. And it is still aggressively adding new features, e.g. first-class support for websockets just came out in rails 5.