skysight-inc/HackerNews huggingface dataset:
The Soviet Union didn’t live in the modern era - and the country which is comparable today is China - and they’re doing very well. I’ve heard many credible
claims that the Chinese state will fail, but it hasn’t till date.

So that point may need to be re-thought.
I mean, it's WSJ. 'Closing the book' is a common idiom in the accounting/business world with specific connotation around ending a project/line of business.
Did you even look at those numbers? That's a drop in the bucket compared to $800MM. Very curious myself as to how that breaks down.
> lack of a great pro desktop

FWIW, I have had every generation of Power Mac G5 and every generation of Mac Pro except the very first, and the iMac Pro is by far my favorite of all of them. It's the best Mac ever made, not just in absolute terms (where it obviously should be) but also relative to everything else contemporarily available.

I love that machine as much as I hate my 2017 MBP.

(It did cost more than my car, though...)
Ask HN: What is the best blog/article you read on internet?
I mean, we all knew this was going to happen, right? There's no way this was actually going to turn out to be a helpful thing, at least on this class of sites.
The reason that planning software development is bullshit is that you simply cannot know all the little details because in software development you're always doing something you've never done before (because if you did you could just copy-paste your previous work).

To use the 'going to the supermarket for milk' example. I could make a fairly accurate estimate for that because I've gone to the supermarket hundreds of times. I know all the different things that can go wrong and account for them, because I've encountered them before. The elderly person who wants to pay cash and has a bag full of coins. The guy who finds a 10 cent discrepancy on his €92,30 receipt and has to argue for 5 minutes with the cashier (while the row behind him keeps growing). etc. etc.

Now imagine that today is your first time going to a supermarket. In fact, before today you had never heard of the concept of supermarkets, or milk for that matter. How good will your estimate be ?

The only time you can make a decent estimate is after you've finished. Or to put it differently: making an accurate estimate is possible, if you're going to accept that making the estimate is going to take a long time, but I can't tell you how long.

Development time estimation, and every methodology that attempts it (I'm looking at you, Scrum), are little more than desperate attempts by managers to feel in control and relevant.
The story of Samuel Rosen and surgery of the stapes bone (2016)
Well, they're just checkboxes inside the main tasks. You just think through how you're going to perform the task (which you'll anyway have to do when you get close to actually doing it), and note down the sequence of steps. Then you try to estimate each step. Sounds simple, but it works.
Not a good feature. Figuring out the rules that would allow the use of .. in a path name in a safe way seems a lot more difficult than figuring out why you want to put .. into your archive and changing what you are doing to avoid it.
Did you write this yourself? It's very good.
> Payday loan revenue in the rich burbs roughly-zero, Payday loan revenue nation wide mysteriously between $6B and $46B depending on data source

Payday loans may "solve a problem" but they do it in a predatory and exploitative way.
> When we asked them to demo, their presales consultant struggled to create anything other than a canned demo.

The opposite experience is what sold me on Looker - super competent team and very clear in how “the magic works”. All logic and queries are right there to copy/paste into your own editor to fiddle with if you so choose, or use the built-in SQL runner. At the same time, non-tech users need not worry about such stuff.
Having been through multiple month long planning "phases", that were eventually shown to be wildly inaccurate I disagree.

This is exactly what we used to do in the waterfall days. It didn't work.

The only way that's been compatible with me is to build something really small but valuable. So small that its hard to be disastrously wrong. Once you've released that value, build upon it.

Stakeholders tend be much happier as they at least have something they can use really early on.
Size and complexity of tunnels increases as the population it serves does. Railroad tunnels have stricter grade and curve requirements than car tunnels, as well.

It is also already possible to get from NJ to NYC in a relatively reasonable amount of time, which makes the cost/benefit different than the Faroes turning things from half a day to minutes.
Ionic theme monthly updates 05/2018
Serious question, Can you get data from any other car manufacturer? I know ICE cars collect information but do you have access to it?
I think that's where side projects come into play. I'm working on a language project on the side because, just as you mentioned, work consists mostly of CRUD APIs around tracking business resources.
Funny thing- I'm a bioinformatics making 70k and with a family. I'm ready to leave the space to make money. I'm at the point where I wouldn't mind something less altruistic -it's all the same uninteresting work. Crazy to read your stories of wanting to go the opposite direction.
> This is a beautifully detailed but self-refuting argument. The self-refutation comes midway through, when the author admits: "To be honest I can’t say that I’ve contributed to non-Github projects either."

So because I'm not homosexual and not a female, I cannot support gender equality or denounce homophobia?

The school of thought that new replaces old no exceptions is boringly wrong. Github flow has its advantages. I as a solo amateur hacker cannot devote the time to maintain my mailing-list+bug-tracker or my gitlab instance, thus putting things on the platform with a wide userbase is a better option. For my private stuff I keep them offline anyways. But I've sent patches both to Emacs via the mailing list and to various OSS projects on github, and the latter was more confusing to me. Still, they were equally useful in that I could get the task done multiple times using them.

Just like pen&paper vs. digital. I'm deep into Org mode, notes agenda ox-latex and everything, but many things are just better with pen&paper, and the digital equivalents won't catch up soon (no energy needed, typing on touchscreens suck, touchscreens suck in general, especially when you need to do things quickly, pen and paper are cheap and widely available). Or just like microwave did not kill the traditional oven or replace the stove.
I stand corrected. I was mislead by the scary warning, which is still there.

The tarfile module is still vulnerable:

https://bugs.python.org/issue17102
just push them up with git...?
From the reports I've seen, GDPR is equivalent in the relevant parts, only the last bit (who the DPA can directly investigate) has changed, which isn't central to the case.

What I found interesting is that they reference the analytics visible to the page administrator: Does that mean that turning them off makes a material difference? Or is it just an additional thing the page owner has to take into consideration?
Conway's Law: "organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations."

And most organization -- or collections of three or more people -- have dysfunctions. There are rarely process problems where technology is the main problem; it's the wet-ware between the keyboards and the chairs that make or break projects.
PII is a term coined in the US
Developer Toolbox: Encryption/Decryption with the OpenSSL Command-Line Interface
Just a quick note on the email point — the specific thing I was responding to was this from TFA:

"Many people, especially younger devs, have never seen a real mail client like mutt. In their minds they may picture an overflowing GMail inbox full of top posted replies all mixed together from different projects. That’s not an enticing image. Perhaps this article can start these developers on the path to rediscovering the care and engineering that went into classic email clients."

My point is that this is nostalgia for terminal-based email clients.
> It does. However, in your linked document just below the `extract` function there is `extractall` that actually has a warning that it does /not/ mitigate directory traversal.

You're misreading the warning. It's saying that the module attempts to mitigate the issue (referring back to ZipFile.extract) but pointing out that this may not be entirely reliable, and thus that as the library user you really should inspect/validate archive paths before doing an on-disk extraction.
Non-technical academic (Grande École in France) here. I'm at the edge of technical issues every day, though they fall just outside my responsibilities as security consultant and Risk Analyst (they are for the architects to deal with).

My technical knowledge/know-how (acquired over years of Linux, BSD, HN, etc.) still gives me an edge in understanding issues my clients face.

I'm not dealing with technical issues per se, but I can make the link between tech teams and management/non-tech: what one party expects from the other, whilst not sinking into a bottomless pit of unreasonable requests and expectations.

The work is fast-paced (~8 hours at most/project, over the course of ~3 weeks) so I have to adapt to a number of situations, where tech people might deal with said technical problems - and I can give them my 2 cents.

I'm also using my free time to work more on my machines, etc.
Oh yes I misread encryption as compression, sorry.
I think neither solution is the correct one.

I find that in the case of the second solution: "thorough planning" you get a bunch of people fabricating estimates of estimates with padding or not padding or trying to estimate a bunch of unforeseen events that are too far ahead to get an accurate handle on.
Sure, the second is likely to be much more accurate just because the second is likely to be much, much longer but I have never given one of these estimates without it being followed up by immense disappointment by business with a desire to strong arm me into something shorter. This demonstrates a fundamental issue with the topic. Its not about the estimate at all.

I think the problem with estimates is their finality and assumption of correctness. I figure once you're in the developer-years category you might as well iterate the estimate a bit to get a better sense of it.
Error bars should be translated into risk for the business decision.

Too often I see people claim to be making "rational, facts based" decisions on estimates (beyond 1 year+) are complete codshit. This is not rational decision making. These decisions should be about risk management assuming failure as opposed to thinking you can slot year+ development estimates together.

I think very often the desire to lock down development estimates into "rational fact" are business decisions of risk masquerading as technical developer decisions of fact. I have yet to see a situation where we deliver an estimate that blows a business decision out of the water where the business just backs down. It just learns to ask a different question and gets the answer it wants out of that.
I do think traits are somewhat evenly distributed, but some traits are multiplicative towards a person's net competence in a certain role. I imagine the distribution is a fat-tailed one.
Introducing DNS Resolver for Tor
Amateurs.

"Unfortunately, our website is currently unavailable in most European countries. We are engaged on the issue and committed to looking at options that support our full range of digital offerings to the EU market. We continue to identify technical compliance solutions that will provide all readers with our award-winning journalism."
Long time ago, I dropped it somewhere near the end (random life circumstances). Thanks for reminding me of it - I recall it as being pretty insightful. I'll read it again.
Haha no. Lots of problems here but every time they're solved we go back 5 steps when we get a new set of software from the vendor and have to solve them again. And trying to automate that just means more steps to do every time we get a delivery because we have to retrofit all those scripts into the new software set, which we never know what actually changed and if our scripts will even work with the new stuff.
The issue is not the amounts, but the flagrant self-dealing.
How to be a Manager – A step-by-step guide to leading a team
It seems like Tesla's on the fast-track to an Uber-tier reputation.
Danso, by no means I wanted to "stalk" you but I noticed you posted at least 5 negative/harsh articles about Tesla last month, which is fine to me as HN has a lot of Musk fanboys to counterbalance, anyways, I was wondering if you have any customer story to share about Tesla that affected you, i.e. did you own one and it was a bad car or did you lost money investing in them? I am genuinely interested in that background so if it may read offensive to you please let me know so maybe I can rephrase it! PS: I would like to buy a Tesla myself but I can't because of where I live, so I can only read people's account about them
police reports of accidents are public record, you should be able to pretty easily go from crash data to personal identity based on public records. Sounds like PII to me.
Glad to hear it. Their support and drivers are horrendous; I was left with a mostly useless $800 laptop because the wi-fi wouldn't work after a Windows "upgrade" (I've since switched to GNU/Linux and never looked back).
Retrocausality Could Send Particles’ Information Back to the Future (2014)
The number one reason is scope creep.
Presumably extras would be advertising/"attention-economy"-driven and thus subsidized by another company rather than the drivers themselves. Or if Uber let drivers have mini vending machines there's a clear ROI on a relatively small investment (or the vending machines are rented etc). Perhaps the more expensive "black cars" would have freebies.
You already are renting/paying a monthly use license fee if you "buy" a phone from your carrier with a monthly payment and the ability to upgrade after x months.

I did this by accident when I "bought" an iPhone a few years ago and was told I couldn't keep it after I water damaged it and got a replacement. I started buying devices outright after that.
https://news.ycombinator.com/item?id=17237708
> Most of my work seems to be boring CRUD work where the challenge is gluing libraries together or figuring out business requirements.

This is ~80% of software development. To stay sane find a domain where the business logic interests you. Maybe you're into sports, crypto, sci-fi, whales, whatever.

Try and find a job in these domains. In my experience it makes the day-to-day grunt work of developing software more enjoyable since you're solving novel problems in area that you care about.
A free, teacher-less university in France is schooling thousands of programmers
Isn't this true of any car company? BMW, Mercedes, and Lexus aren't going to hand over vehicle data. You can't just ask Google for your Android Auto data.
If you're already exposed to what the working system looks like and you later on have to follow the setup tutorial to get it going yourself, that's much easier than starting from scratch. And it's more motivating too, since you know more of what the end result will give you vs hoping that it helps you solve the problem at hand.
I work with a lot of ThinkPad Yogas. They are decent. The business machines are not terrible on bloat. I would still download a Win10 installer and nuke the factory image.
I'm currently working on a very interesting problem, currently we are making software that makes automatic phonetic transcriptions: https://github.com/persephone-tools/persephone

The quick summary is that you take audio files which you process then run through some models that do labelling and at the end you get out transcriptions in the international phonetic alphabet https://en.wikipedia.org/wiki/International_Phonetic_Alphabe...

In the past I've worked on things that were very boring but also things that were very interesting, sometimes even in the same company. Even if you structure your career to try to spend as much time on interesting problems you'll still run into some boring stuff. If you really want to work on interesting problems it will likely take some effort with deliberate planning and you may end up making less money than if you did other work but these are the decisions that you will have to make. Try to find things that interest you and give you opportunities to master whatever it is, this tends to make work a lot more fulfilling whatever you do.

Incidentally in this language project I've done some work on a Web API that's mostly routine but it's very satisfying because I can very directly see how it makes a lot of other people's lives a lot easier. There's some very clear impact there and it makes some otherwise routine things a lot more enjoyable.
> This saves money for the advertisers, by transferring wealth away from content creators.

Not really. It actually increases the pool of money available to content creators.

Everybody wins.

> It boggles my mind that publishers still favor this model over display ads (targeted to articles, not readers).

Because they generate more revenue, I'd guess. Mind-boggling, I know.
Web "standards" for PWA's are pushed out willy-nilly by Google. Just because it is preferable for Google to push towards everything on the web, it does not mean that all browser vendors should create new APIs that were declared "as standard" in their draft version and pushed out into Chrome.

Service Workers, for example, are just a working draft and somehow not having the spec implemented is considered as lagging.

PWAs are fine for some uses. However I think it would be better for everybody if the vendors were extra cautions when creating and approving these standards as these APIs tend to crystallise and browsers end up supporting a lot of deprecated cruft. I was young when MS was doing the same thing with IE6 but I still remember the pain in the ass making anything remotely compatible was. And back then we were not talking about access to stuff like microphone or background activity.
Both companies are in a position to do so, they could pay the users for their data.

Would you never pay a cell phone bill again but trade your personal data for it? I feel like there’s enough people out there that would.
And that is/was Gmane. But it's dying a slow death due to disinterest. You can access it via the NNTP protocol.
Since there is clearly an interface to obtain the data, used at least by third-party vendor 'Crash Data Group', it seems it'd be possible to develop an external logger to plug in while driving.

Such data loggers are commonly used in racecars, using either their own sensors, or in stock versions, also tied into the OBDII ports. It looks at everyghing from driver inputs, to engine performance, 6-axis G loads, etc.

Seems it'd be pretty nice to get the data anyway to help manage your own driving (or check the habits of someone borrowing your car, like your kid), and in case of an incident, your own log of the events so you don't have to pester/subpoena Tesla.
Without access to the data we don't know how useful it is full stop.
Researchers find genes unique to humans may explain our big brains
I thought the same, and assumed that they'd made it public as a way to showcase positive corporate culture.
One way to get ahead of it is to try pitching proposals to problems your organization can't afford to ignore.
I recently bought a 2017 Macbook Air with the refreshed CPU and it's a great machine for the price.

Yeah, the screen is old, but it's not that big of a deal IMO.
At least the local data can be accessed with OBD interfaces [1] most of the time. I don't know about stuff like theft prevention where the GPS location of the car is being constantly transmitted over GSM/UMTS/LTE, though.

1: https://en.wikipedia.org/wiki/On-board_diagnostics
> What use would this type of data be to the average consumer?

We can also reverse this question: why would Tesla hide this type of data from their customers so intensely?

One reason that comes to mind on both questions, is that customer's (or someone on their behalf) are able to review if the crash is due to software malfunction.

> isn't this otherwise very similar to being in a plane crash and demanding the black box data

Most people don't buy (hence own) a plane but buy a ticket with an airplane company instead. The airline company actually does get to access the black box data in case of a crash. So do the authorities.
Well there's some noise like in everything else in life, but I don't think there's any empty studies (okay there's even a few cases of lying which is sad beyond words but thankfully they are very few i think).

Why does this noise bother you? Besides, keep in mind that the grant-chasing doesn't happen because of greed, it happens because people want to continue doing science and that's the only way to maintain an active lab.

I could shit on the state of academic publishing for days, but at the end of the day, there is an overall positive direction in this 'academic endeavor': the creation of knowledge.

I find this direction much lighter on my consciousness than "generate value for the shareholders"
see https://www.qubes-os.org/ and https://www.qubes-os.org/news/2018/01/22/qubes-air/
Doing it perhaps for the click-bait karma?

Edit: I'm one of those people that believe in what Elon is doing and while I don't consider myself a fan-boy, I get plenty frustrated by all of the biased negativity I somehow feel the need to inject some balance by saying something. That may come across as only ever defending, but the amount of negative fluff articles is astonishing.
The question is, if it belongs to me, can I voluntarily give it up even under the known condition I can't ask for it back? I mean, it belongs to me right? That's where these laws often run afoul. You can have more freedom with consequences, or less freedom with restrictions.
This is why agile tries to push the business stakeholders to define -problems- rather than -solutions-. Developers then try and come up with a solution, and pitch it to the business (effectively).

Almost every issue I've had with the business/developer dichotomy (and I use that instead of product because different orgs place product differently) has been due to the business trying to pitch solutions to dev that invariably end up not actually addressing the problem (even simple things like "that's the wrong color" or similar, are because they believe they're responsible for the solution, and they have a very clear idea of what the solution should be, without actually being able to articulate or recognize the problem. Does the color actually matter? If you have a problem that implies it does, yes, if you just came up with a solution on your own and in your head that solution was yellow, no).
Do you have more info on this? When is it expected to be done?
> And the UK is improving rapidly with good coverage of reliable chargers in most parts of the country (still no >50kW chargers however).
For me, not designing the product as a platform is no. 1 root cause of all the delays and confusions. People then to deliver for speed, make compromises. Over a period we end up in mud pile and slows down all future developments. This makes the speed slower & slower with age.
Plasma to treat wounds instead of antibiotics
Oh boy, I was so excited to get a Tesla when the time finally came, but if they're still pulling this crap when that happens, guess I'm getting a Benz instead.
You can always use an ftp client or rsync to fetch mailing lists as a bunch of mboxes, and use a program like notmuch or mairix to search them very fast (not sure if notmuch supports mbox though, but I've used mairix in the past and it's nice).