skysight-inc/HackerNews huggingface dataset:
Yes and there's more that is wrong in the article:

"as demand for a product goes up, supply increases, and price goes down"

No, when demand goes up, the price will go up as well unless supply increases by the same amount. The price will only go down when supply increases and demand doesn't keep up with it.

"the tools many countries use to measure intangible assets are behind the times, so they’re getting an incomplete picture of the economy. The U.S. didn’t include software in GDP calculations until 1999. Even today, GDP doesn’t count investment in things like market research, branding, and training—intangible assets that companies are spending huge amounts of money on."

First of all let's skip the part about what the US did until 1999 because we're living in 2018 at the moment. And then the fact that market research, branding etc. is not included in GDP calculation has little to do with the digital age. There has always been market research and branding, not just now. One might argue that it should be included but that is really a separate topic.

"It took time for the investment world to embrace companies built on intangible assets. In the early days of Microsoft, I felt like I was explaining something completely foreign to people. Our business plan involved a different way of looking at assets than investors were used to. They couldn’t imagine what returns we would generate over the long term."

No doubt things were like that in the 80's. But just take a look at the most valuable Dow Jones funds now and it's clear that intangible assets are valuated well nowadays.
Announcing US-SJO1: New Data Center Launched in San José / Silicon Valley
Awesome, glad you liked the piece!

Genuinely, we're all just steamrollers and I don't think many new programmers really understand just how often solving a problem comes down to sheer willpower and persistence.
The only thing different about software is we haven't been doing it long so we don't know how to estimate. If you are writing a CRUD web app, it is just like the million others that have been written before and you should have the ability to give reasonable estimates. If you are writing a self driving car - that is new ground that only a few have attempted: there are many "unknown unknowns" that are hard to account for.
Use APSW instead of sqlite3: https://rogerbinns.github.io/apsw/
I had sent an email to my team last week about the book. I'll pass this on, thank you.
What an absolute nonstory
Thanks! That is awesome advice. I think that is a great way to look at it. I am going to follow that advice right now :)
Java Developers: Var Is Your Friend
>that the fair price according to classic economic theory is zero

I don't think any economic theory is that naive.

It's actually the cost of production divided by the number of sales, where the cost of production can be many millions of dollars worth of development and testing and the size of the addressable market can in some cases be very few.
Hey, no offense, but NYC has a few very large arts colleges and the city is teeming with arts majors looking for work. If you want to immigrate there, you'll need to really stand out from students that were hand picked from all over the world to study arts there.
I said that I'm ok with calling it "not bullshit", so I'm not sure what you're getting at. I was questioning whether or not it could properly be called profound.
Zero to Here: Guide to object detection using deep learning
They humiliated themselves
> There are no assumptions in supply and demand, it's not a dynamic equilibrium, it's a snapshot.

It absolutely is an equilibrium in normal economics: https://en.wikipedia.org/wiki/History_of_microeconomics
That's not what I am saying ... It's silly to think that 'investors' will ignore such a giant opportunity just because there's human rights issues. It's just naive!
Better collaborative data science
Sure they do. If FB stuck to legal-based censorship then they wouldn't need to ban atheist or gay rights content because those content are legal in the US. But if they swing to moral-based censorship, then those countries can appeal to morality ( their own ) and demand FB censor content in the US. Why? Because FB and tech companies have set a precedent.

What defense does FB or tech companies have against people who say they consider atheism or gay rights to be immoral or offensive? None.

What happens when criticizing a religion is considered hate speech? Wouldn't we have to ban atheism? What happens when people say they find content about gay marriage offensive?

Moral-based censorship opens the floodgates to unlimited censorship.
'Plogging' Swedish fitness craze is coming to the U.S
I am also going to point out a subtle mistake committed by this specific library. The examples include this:

hanımelinin çiçeği (flower of a plant called hanımeli)

That's subtly wrong. The flower is called hanımeli çiçeği just like portakal çiçeği etc.

I fear that the inability of computers to deal with Turkish will end up morphing Turkish into something computers can deal with instead of improving computers.

Turks have done great damage to Turkish since the junta. Just a simple example: Almost everyone says "Deniz Sokak" instead of the correct "Deniz Sokağı" while somehow getting things like "Anafartalar Caddesi", "Çanakkale Apartmanı" etc right.

Adding computers to the mix is not going to improve things.
Do you ever have issues with (US) candidates not wanting to live in the NYC area?
There are two assumptions you can make based on this chart. The first is still more or less true today: as demand for a product goes up, supply increases, and price goes down. If the price gets too high, demand falls.

Er, no. I guess even smart people like Gates get simple economics wrong sometimes. It's understandable, though, I've always felt the P/Q axes should be switched, since people always speak about the price as the independent variable.

He's conflating the idea of pricing along the line with the demand line itself. Yes, at higher prices, less quantity is demanded and vice versa. Similarly, if you can sell the thing for a higher price, more people will be interested in and able to sell it, so the quantity available will increase, and vice versa.

However, "supply" and "demand" refer to the whole lines themselves, not points along the lines. Changing supply and demand means the lines shift. If "demand for a product goes up", the demand line shifts to the right, the equilibrium quantity increases, but so does the price, the opposite of what he's saying.

His misconception then leads to an even larger error in understanding with the next part:

The second assumption this chart makes is that the total cost of production increases as supply increases.

This is false. What it says is that with if the price you can get for a good is high there will be more suppliers. The canonical example is oil: when it sells for $20/barrel, only Saudi Arabia and places with it easily accessible will be able to profitably drill for it, and so the quantity supplied will be low. But at $120/barrel, you can now use fracking, deep water drilling, and other much more expensive processes, and so the quantity supplied will be higher.

Supply and demand is not about any individual producer producing more, and so it's not particularly useful in analyzing the behavior of a single firm. It's about the aggregate effect of multiple different parties, each with their own respective infrastructures and costs, profitably contributing to the supply (or not) at different price points.
At one point the packaging was required by the retailers, who wanted it to conform to a standard shelf size. Eventually it could shrink to CD or DVD jewel case size. Might be a discussion of this on filfre.net somewhere.
Testing Elixir REPL Applications with Only ExUnit
I'm not sure whether I have followed your example correctly, but interpret it as being that the local population was essentially law abiding, because they knew the camera locations both when they were visible and when they were non-visible, and that the main issue was with out-of-town drivers.

There is, of course, no reason why a local council should not decide to deploy visible cameras in such a situation, alongside a national network of non-visible cameras (you obviously don't need to have both visible and non-visible cameras at the same site). The cost-effectiveness argument still holds, under the assumptions previously mentioned.
Is this a common insinuation of the word "humiliated"? That's not the read I get from this article at all.
>We asked repeatedly, but Intel provided no advance notice. We did not
even receive replies to our requests for dialogue.

Intel's treatment of *BSD is frankly quite insulting, especially so given that they serve a _huge_ portion of the internet traffic, with Netflix using FreeBSD for content delivery.
Post-Quantum Cryptography: Efficient algorithms for supersingular isogeny DH [pdf]
Where I work, we separate the roles of Product Manager and Engineering Manager. The former focuses on roadmaps and priorities and works with the engineers directly while the latter focuses on people’s growth and career goals, and has almost no say on what people are working on or the handing out of tasks.

It works well. It’s nice to have someone to talk to and work with who isn’t invested on what you are working on today or riddled with conflicts of interest.
Child drownings in Germany linked to parents' phone ‘fixation’
Web is important because a fair level of development is being done for non-technical end users.
The costs of producing N+1 and N+1000 should in fact be different. With N+1 you train the user, with N+1000 you bring in some UI experts to design a better interface that doesn't need to be trained in the first place.
This is the sort of article that makes me imagine a dialogue between a senior software engineer and a newb developer that goes something like this:

Newb: Hey man, I think for this project I'll write my own SQL datastore from scratch. I've looked at a bunch of them and my project, which is basically an inventory management system, is such a special snowflake that it needs its own datastore.

Senior: That would be insane. Never do that. Use what's already out there, and is tried and tested. In fact, just use postgres and make it work.

Newb: Aw, ok. I was so much more excited about writing a new SQL datastore than I was about the actual project it's for, but sure, I'll just use postgres. starts to walk away...

Senior: Hold up a sec before you go, I want to run something by you. Because our discipline, which is basically a team of people who are hired to build things on a schedule, is such a special snowflake, I've invented this totally new way of thinking about work, and of organizing a team and leading it, and there's a bunch of new terminology and I have some cool diagrams... I'm lobbying that we all switch to this at the end of the month.
Dropbear has been created in 2002.

From the project ChangeLog:

```

[..]

0.28 - Sun Apr 6 2003

- Initial public release

Development was started in October 2002

```

..why is it surfacing now on HN? O_o
Yeah I signed up months ago but haven't gotten an invite yet =(
Oracle open sources Graphpipe to standardize machine learning model deployment
I suspect the biggest obstacle here is overcoming bureaucratic obstacles like vendor approval. Also, PIs and universities don't have a strong incentive to bring down costs. Their (both institutions and PIs) pay is tied to grant money brought in and lower costs mean smaller grants.
>The relevant comparison, for the sentence to be true, would be between "The imagined pain experienced from thinking about torture" and "The pain experienced from thinking about torture".

I don't understand what the comparison is supposed to be there. You can't "experience" imagined pain. If you're saying that you can imagine being in lots of pain, and that imagining this scenario isn't itself painful, then of course everyone agrees with that. But this is a banal observation, and one that seems to contradict the original sentence.

>People of course rarely question the reality and experiences associated with eating cake, but they do with people experiencing pain, which makes the sentence more insightful than you seem to believe.

If you're saying "we should generally believe people when they say they're in pain", then sure, I agree with that. It's just not what the sentence we're discussing says.
> Maybe try digging a tunnel through a mountain, where the kind of rocks and caveats you find on the way can make you overrun your estimates?

Usually the client doesn't call halfway through the project and tells you that the tunnel you're digging really needs to start 10 miles further up the valley...
The author is talking about a societal shift whose consequences are difficult to foresee; one person electing to only use CDs, DVDs, flip-phones, and the like makes little difference to the broader trend.
You get different things from pair programming compared to post-completion code review. They share some benefits and to some extent can compensate for the lack of each other, but ideally you want both.

If you're reviewing someone's code at the code review stage, you can only do so much. If it's working, tested code then asking for major changes is either pointless or very costly; there's little point in suggesting out a better way of approaching a problem if it requires major surgery. Unless you spot a potential bug or something that will cause major problems, you're realistically restricted to suggesting minor changes like style suggestions or better names for things.

With pair programming you have two people collaborating on a design from the start where suggestions for better ways of doing things are much easier to incorporate. If pair programming for a complete feature is either not feasible or undesirable for some reason it is at least often worth pairing to start a feature off.

Code review on the other hand also has some benefit in getting a fresh pair eyes on a piece of code to spot obvious mistakes that people elbows in deep in it have glossed over or find hard to see, such as left-in debugging code or user credentials.
Are you allowed to work as a student?
I disagree with this entirely, its basically the opposite of the point of the article. It sounds like the kind of leader that would have to insert their superior technical knowledge into every decision the team makes and who won't recruit the best people to take technical leadership of different aspects of the project.

Maybe we're envisaging different kinds of projects here. If it were 3-5 people building some component I'd expect there to be a technical leader in that group that can push it forward, as you say. But even they might not be the 'best' coder, whatever that means.

A 50 person project is never going to have a single person like that though.
Check out F# today to see what will be added to C# in two years! :-)
Photoshop, being nearly a monopolist, seems to almost fit the definition. Regulation is the only thing here that doesn't match, but being a de facto industry standard would be close enough for me.
Break a dozen secret keys, get a million more for free (2015)
On goodreads.com you can review book yourself and also discuss with other reviewers. There are also groups (https://www.goodreads.com/group) which works like forum.
I wholeheartedly agree. I think it’s however more of an unacceptable problem in non technical industries who hire technical workers.

For instance, risk assessment isn’t all that helpful if your deadlines are bumped up by weeks or months and the client or your coworkers or bosses have no concept of why the project “can’t just be done immediately” when you’ve planned for added weeks. Even worse when they don’t understand why they can’t suddemly throw new variables at you after all estimates have been completed like new, potentially breaking features. Last minute scope creep is a real problem in some non-technical fields because the whole software solution is often some “nerd magic” and there’s no desire to understand the problem or solution except where to click and can they have it all by the end of the week. Theoretically maybe it could be done, but there goes all window provided for unexpecteds.

Admittedly, this is probably more of an organizational flaw than directly associated with the subject at hand, but a very real tangent.
I read all my books on kindle normally, with the exception of textbooks and things that are more dense or books that require large paper sizes.
I'll speak for myself, but I don't think this post passes the "intellectual curiosity" test:

https://news.ycombinator.com/newsguidelines.html

"On-Topic: Anything that good hackers would find interesting. That includes more than hacking and startups. If you had to reduce it to a sentence, the answer might be: anything that gratifies one's intellectual curiosity."
(emphasis mine)
I'm more frustrated by my own inability to tell the "rules" of English. I can tell something "sounds odd" but I don't know enough grammar rules to know what is "correct" grammar and what isn't.

For example, saying "Google are deciding to go back to China PR" sounds completely incorrect to me. It ought to be Google IS, imo but clearly enough people do this.
Is x86 dead now?
I wish there was a screenshot, just to gauge what it could do without installing.
It's the Magic Formula (EV/EBIT and ROIC) and it has not always performed well:

https://seekingalpha.com/article/4116677-greenblatts-magic-w...
"hardly 0.1% of them might fall ill in any given year" is a very unrealistic assumption - is service is available (which is not universal in India at the moment, but is promised to be with this reform) the expected number of annual per capita doctors visits is at least 1 (OECD country average is 7, poorer countries get 1-2), not 0.001, a thousandfold difference. Not all people won't get ill in a given year, but a large portion does; it depends on how severe illnesses you count but it's 30-60%, not 0.1% or 1%; and some people (much more than 0.1%) get multiple illnesses in a single year.

I'm arguing that on average people (all 1.3 billion of them) need much, much more than $1 of coverage each year. You don't need $7200 to treat common diseases, but many of them will need more than $1. For every person that needs $0 of coverage there will be one that needs more than $2.

If the estimate was comparable to $10 per person (so, excluding private insurance, roughly $10 billion total not $1-2 billion), then it might be worth starting a discussion about the details and how much what costs. But $1/person/year is so ridiculous that it's off the charts.
It's also easy for code review to devolve into "this isn't quite the way I'd implement it; scrap all this work and start over"
Running a Software Business on 5 Hours a Week
I don't consider managers to be the leader of software teams.

The best managers I've worked for knew how to navigate the bureaucracy and politics of a large company and had next to no technical talent.

The best leaders I've worked for knew how to get shit done. If anyone dropped the ball, they could pick it up and score the points.
How can something be serverless if it habdles http requests? Does it just process requests and never serves responses, or is it just a hip-sounding misnomer?
Thanks. You seem to be spot on about the HN community not finding this interesting. We've announced a number of projects on HN over the years and while I didn't think it was a slam dunk I did expect a better reception than this. Oh well.
From what I have read there are some rules on working time
Random Number Generators Can Be Fooled to Behave Badly
OT, but what will happen to them after global warming?
I guess its not too different than what happens during summer times.
Adobe products are continually worked on. Most subscription software is. You get continued support and feature updates, and the subscription model makes more sense for that kind of development than the yearly waterfall version releases.

JetBrains has the best of both worlds with a fallback license to let you keep using an old version, or a subscription to get continued updates.

Games are becoming increasingly long lived pieces of software as well. With bugfixing and updates continuing for years. The industry is struggling to find novel ways to make money in that environment, which is why you get things like loot crates. I would prefer an honest subscription over that.

What I see is a devaluing of software as a product. I should be able to spend a couple of hundred hours on a package for a framework and sell it, but there is always someone offering a free version and then using weird and sometimes shady ways to make money. I wish it were more common to just sell code for money, instead of people pretending they are altruistic and then selling your data, selling your eyeballs or locking you into their ecosystem. Subscriptions are at least an open and honest transaction.
Gates' says "it combined Apple's MP3 technology...", your example says "Apple combined MP3 technology..."
I mean it's good to remind people of older and less-known projects, but Dropbear is quite common for embedded Linux applications.

OpenWRT uses it for example.
I think the difference in software engineering is that the cost and time of digging a tunnel is almost zero. When you write code that "digs a tunnel", writing the design and code are the hard part, distributing the compiled code is usually predictable and simple. So I think software engineering is closer to the planning phase in civil engineering, where you need to go research the mountain, plan multiple routes, deal with regulation, etc. I bet it is also hard to estimate in civil engineering how long it's going to take to complete the plan to build a tunnel.
Simply put, options are an option to buy shares at a specified price sometime in the future.

For example, a company can give you options to purchase X amount of shares at a ridiculously cheap price ( like $0.0005 per share ). Many startups do this. Sometime in the future, you can exercise the option and get X amount of shares. If you don't exercise the option, then you don't get to buy shares at the agreed at price.
That's not a code review. That's either a suggestion that the initial commit is 'wrong' or the reviewer is a jerk. Either way, this is the PM's fault - not enough information to finish it right or too reviewer nitpicky on useless stuff.
You think software developers are unique in making claims that their field is unique in some regard?

A lot of us have the issue of perspective. We believe we have problems no one else has and fail to consider that others may have problems we can't perceive. Out of sight, out of mind.

Also, millennia is already a plural.
Cool, British Airways also leaks your booking information to a set of third parties the article highlights - without consent. If one enables an ad-blocker, it's impossible to check in apparently.
And that's just one of the differences between a good coder and a good senior engineer.
Software is incredibly open ended. Maybe even more open ended than writing in English because software can be written in several languages or even in brand new ones.

The lack of natural structure in the work means communication and collaboration among the development team(s) is all that more important.
All good theories go out the door when your dev team is offshore. Read good detective stories for an inspiration: how to uncover lies, separate truth from bluff, trust no one. Considering how many projects are done by offshore teams - this article reads like a ballade to sunshine in the midst of a hurricane
One of the best pieces of advice is to not go to New York City. Everything, from rent to groceries is at least double what you'd pay anywhere else.

If you're dead set on living in a city, Chicago and Boston are flooded with technical growth at the moment. If budget is a big factor, consider Cincinnati. It's smaller but growing and dirt cheap to live quite well!