skysight-inc/HackerNews huggingface dataset:
I hear this argument whenever there's a discussion of 'should designers learn to code'. I have two problems with it.

First, it's an argument for a very select set of design+engineering projects. In almost all real world situations, designing something that is possible to build without 'pushing the boundaries' means a design that might actually get implemented. Not everyone works on the bleeding edge of engineering, nor should they if they want to focus on all the other obstacles to creating a successful product. Most organizations have technical debt and UX debt as it is.

Second, why does understanding the engineering side of the equation mean an inability to come up with boundary-pushing design solutions? If anything it would seem to mean an informed pushing of the boundaries when it's actually necessary for a design. It's like the advice English teachers give out -- learn the rules before you break them.
My comment itself is a good demonstration of the point I was trying to make. I anticipated the possibility of misunderstanding or misinterpretation of my first statement and put in the time to add the second to qualify my point.

I did not intend make a blanket generalization against quick and dirty solutions (ref: google about Doug McIlroy and Don Knuth trying to solve the same problem[1]). I am in fact stressing that there exists a tradeoff that needs to be considered. Usually the tradeoff is made towards less work (ie: lazy programmers) -- less work for the foreseeable future (and if you can't forsee at least somewhat in the future, you're not doing it right).

By responding to just the first part of my comment you've confirmed the last part.

[1] https://www.google.com/search?q=literate+programming+the+wor...

edit: I mistaken said Bill Joy instead of Doug MaIlroy initially
Phosphate tends to be a pretty different animal from methyl.
> There's excellent local craft beer in even smallish midwestern cities

Which is precisely why I want this to be a thing. I want a friend who is flying out of Minneapolis–Saint Paul International Airport to be able to get through security, pick up a bottle of something from a small brewery in Minnesota, get off in Boston, and bring me a beer I'd otherwise never be able to try.
If you guys are interested seeing this update every day, there is a nifty Chrome extension for it.

https://chrome.google.com/webstore/detail/mortality-new-tab/...
Sure, as a general rule, but conversions from LLCs to C corps can get very complicated as well in short order, especially when there have been different types of equity issued to founders/employees (e.g. profits interests, convertible notes, etc.). If the cap table is sufficiently large, it can cause ballooning legal costs pretty quickly. Not outrageously so, but companies can expect at least a few thousand to get added to the bill.
Testing that function would be a matter of mocking out the database with a class that can emulate the type of failure that would trigger your exception.
Overclocking tools for Nvidia GPUs suck, I made my own
Whiteboard interviews should be re-framed. Instead of "what is the best method to sort through a list?", set a situation where two co-workers are having a casual chat. "I'm having this problem, I can't sort through this list, any ideas what I should do?"

That kind of discussion between co-workers happens all the time. You suggest ideas. Have you tried this? Yes, but it has that problem. Oh, so what about that other approach? And so on.

It's a lot less stressful than an interview where you are expected to find the right answer, and it's also much closer to your real job.
It really kind of depends on what you want to do with the SVGs. They can cover topics such as icons, animations, UI, charts, reports, and so on. Just about anything you can imagine using a vector image instead of a raster applies. Many javascript libraries already exist to cover many of the usual situations. You can look into those and play with them to figure out where your interests lie.

And this isn't limited to web technologies and browsers.
I'm not long on Uber either, for several reasons. But there exists a possibility that Uber's legacy could be that it served an important and pioneering role in the evolution of transportation and that is something that current employees should consider before they want to jump ship due to perceived brand popularity.
As someone of East-Asian decent, I totally get this. But I also can understand the counter-point: if you are joining a company of predominantly "anglo-saxon" peoples, does that company not have a valid concern that the people they are hiring are conducive with their current work process (i.e. communication, collaboration, etc.).

I understand your comment isn't advocating for what I am insinuating, but in general, I think the sentiment that companies need to adjust their culture for their candidates is problematic.
> What is the rationale behind this? Or how will this benefit existing citizens? Where do you draw the line for a cap on immigration, and why?

There was no rationale. You keep pointing at Australia etc as a desirable model, and I told you what you'd need to do to make your system more like those countries, and what the result of that would be.

In particular, those countries don't have quotas on skilled immigration. Well, not explicit ones - any point system establishes an inherent limit.

> I would say the first priority is to ensure this system is not being used to drive down wages, and not being used to abuse migrants.

I don't think there are many people who would disagree with you. As an ex-H1B, I don't see anything objectionable about the changes presented so far (and if I still were an H1B, I'd actually benefit from them).

Here are some nice charts here about who's using the system, and how:

https://www.axios.com/h1-b-salaries-2228205505.html

Note that what these numbers clearly tell is that it's not Google, Microsoft, Facebook etc that are a problem wrt wages. It's Tata, Infosys and similar sweat shops. Those are also the ones who get most of the H1B visa quota. Ironically, they're also the ones using H1B as a true temp worker visa - they rarely sponsor their employees for green cards.

In contrast, for most major tech company workers, H1B is a vehicle to green card and citizenship, and the companies themselves do encourage that, sponsoring employees and paying all filing and legal fees, because they are interested in retaining those workers long-term (and are paying well enough that they're not concerned that people would leave once they're no longer legally bound to the company).

So, imposing more stringent lower limits on wages would benefit the Googles of the world at the expense of Tatas, and would benefit people using H1B as immigration vehicle over temp workers.

> Family-based immigration must be done in a way to ensure that we are not creating greater demands on the economy. They should be able to support themselves and not contribute to the decrease in participation rate, and increasing unemployment.

Strictly speaking, family-based immigration already has such requirements. The sponsor must not only demonstrate sufficient minimum income to provide for the person they're sponsoring, but they're also required to sign a legally enforceable pledge making them financially liable for support of that person:

https://www.uscis.gov/green-card/green-card-processes-and-pr...

This remains in force until that person becomes a citizen, which would be at least 5 years after getting green card in most cases (you need 5 years of permanent residency to apply for citizenship normally; 3 if you're married to a citizen).

This all is very similar to Canada.

> This says that there should have some kind of entrepreneurial visa.

There are visas for investors, but they require considerable sums of money upfront. I don't think there's anything for people who are not self-funded in that manner, which likely accounts for most of the startups.
> How can we protect ourselves from something that is beyond the language and is not controlled by it? There’s no way to do it.

There are plenty of ways to do it. The most popular is probably to capture the Java nullability at the border when Java values enter Kotlin code. From that point on, your code is null correct and will never give you an NPE.

> The Smart cast to ‘Int’ is impossible, because ‘value’ is a mutable property that could have been changed by this time error is driving me nuts. I want to kill someone or break something.

Yeah, lash at the compiler for pointing out your code is incorrect, right? Easy solution: use a `val` (which should be your default anyway). Another solution, although less easy: write better code.
Trying to cover your state space with coarse-grained tests in database-backed applications can lead to slow tests suites that are laborious to set up/tear down, which is a barrier to fast build times in CI. This harms productivity both while writing tests and in deployment.

J.B Rainsberger says it best: https://www.youtube.com/watch?v=VDfX44fZoMc
>Out of all the branches of the space-time continuum, what's the chance that we are on the original one?

None, because there's an infinite number of branches. And every time someone travels back in time, it creates a new branch.

What'd be interesting is to do an experiment to disprove this: invent a time machine that allows traveling both backwards and forwards in time. Use it to send two people back in time. Person A goes first, and the person B warps back to a time an hour later in the same place, and tells person A a secret. Then person B comes back, then person A comes back an hour later. Have person A repeat the secret, and see if they met each other in the past. With a new universe created every time someone goes back in time, will person B go back to the same new universe that was created when person A went back in time, or will they go back to the original universe that person A tried to go back to, and which still exists without person A which would change the course of history there? Does person B create a new universe? Will person A have met person B, and will they have seen person B go back to the future before them?
That says more about you as a developer than SO. In just about any SO answer I find numerous things that are either wrong or bad advice. The difference between me and a lot of SO users, especially novices, is that they don't know a good answer from a bad one.

A lot of people on SO seem to be answering just for points, half the time, or more, they don't actually know what they are talking about all or have experience with what they are explaining; they have often literally just "researched" the question and now they condense a couple of sources into an answer. Without having a proper understanding of the subject.

SO is bad for the whole industry. And there is not much that is worse than a "developer" copying an answer off SO and putting it into a production code base, without even understanding the answer they just copied.
Automating our Sales Process
It should be "mathematically proven to physically impossible under this model/these assumptions".

Every math-based prediction about the real world will be based on two parts:

1) The world behaves like this model [up to our measurement accuracy].

2) The model implies this prediction.

Their claim would only be speaking to 2) -- that, under the model, you cannot reach absolute zero. The model can still be wrong.
That's a good point, about how when you're 20 you hardly remember much from 10+ years ago.

In that sense, my memory is excellent, now I can remember a lot from 20 years ago.

Yep, definitely aren't as sharp as when I exercise more. And come to think of it, there was a good 13 year period where I was cycling a lot just to get around and now I drive to work every day.

I don't think having a smartphone in my pocket helps either, I tend to pull it out and read HN for 30 second periods during the day, then lose track, somewhat, of where-and-what I was doing.
Yes there is a dev jar. We've removed the download for now because we are running our recent release to cloud through the QA process. Check back in a few weeks or contact us via the website and depending on what you are planning to use it for we can give you an early copy.

FaunaDB is closed source (with plenty of open source
companion code on Github) https://github.com/fauna
Google could use them on the phone, they just needed to PAY Sun just like everyone else, but of course they wanted to have the cake for free.
Well there's been several pretty negative pieces on the Guardian front page in the last month. OK they're left of centre, so will undoubtedly have a view on the sexism aspect of recent events, but it's not been just those aspects they reported.

I think most also got picked up by Metro.co.uk and the Daily Mail etc - like the CEO argument - so reporting is well outside SV. Not forgetting the whole #deleteuber thing. A couple of months back the only mention of Uber outside of HN, Tech Crunch et al was reports of the driver self-employment case or expectation of driverless cars.

What I can't guess is how influenced non-techies are from current events. It does feel like they've hit a certain mass that those negative events are now being widely reported in the mainstream.

I'm the wrong side of the Alantic to be well up on the SV jobs market, but as I say, were it me I'd be concerned by the apparent change in mood. I'd have been equally concerned by the change in mood, and endless bad press, just after Ratners CEO called one of their products "cheap crap" as a joke [0] - 12 months later Britain's largest jewellery chain was no more.

[0] https://www.theguardian.com/business/2014/aug/22/gerald-ratn...
Flight attendants rushed to help and poured a bucket of water on the headphones, but the battery and its cover had both melted and stuck to the floor.

http://spectrumfx.net/blog/lithium-battery-fires-why-not-wat...

Probably not a good idea to pour water on an electrical / lithium fire. I expected airplane personnel are now routinely trained to deal with battery fires.
Russian Agents Were Behind Yahoo Breach, U.S. Says
Well, fair enough, but then I'm interested in the Google Earth 3D-mapping tech :)
> It seems to me that the committee who designed this has been confusing what is happening inside the box (flex or not) with what is happening outside the box (inline or block).

That has nothing do do with "the committee who designed this", the issue has been inherited all the way from CSS 2's inline-block, which defines `display` as a single-value property altering both inner and outer display types.

> Those two behaviors should be orthogonal, IMHO.

Which is why Display Module Level 3 exists https://www.w3.org/TR/css-display-3/#the-display-properties.

However Display 3 is a Working Draft, and thus not available to flexbox (or grid), so until then they need an inline- prefixed "legacy" value.
> do they have competitors? Other lyrics sites look and feel like static html sites from the early 2000's

If I'm looking for song lyrics, and not some collaborative social information-exchange medium, then that's exactly what I want it to look like (and pretty much be.)

Genius is slow loading and slow scrolling and has bigger ad blocks than most lyrics sites. If I'm not specifically looking for annotations rather than mere lyrics, it's strictly worse Tha the competition.
Plenty of people get on airplanes with a bottle of water. Why not let them get on board with a bottle of local craft beer that they've bought after going through security? It would let them introduce their friends to beer/cider from another region.

I'm not talking about shipping cases of beer from San Francisco to Chicago and selling them at EWR. I'm talking about selling individual bottles at SFO and SJC.
>I think 'pro-gun' is a bit different....

One rule for me, another for thee
How to download turboc++
To avoid doing a Microsoft move on us that now enjoy the pain of writing not so portable Java code across official standar Java™ and Android devices, thus making a fork in the Java ecosystem.
I'm talking about regulation and those failures don't seem to be regulatory failures. I guess you could try to regulate to stop having data beaches but I think it would be too broad and largely ineffective anyway but in the case you regulated essentially every web app then a license might be more efficient than actually testing everything. I was thinking more along the lines of things that could cause physical harm (e.g. medical devices) where it makes a bunch more sense to test the device than test the engineers
For Android UI components specifically I usually just include the type in the name. The types can get a little long but when you need to have and operate on
userNameTextView
userNameTextInputLayout
you end up saving time when looking back
"Job hopping" doesn't look good on your resume.
I think this is part of why they've embraced microwave internet. I have webpass, owned by google fiber, and it's up to 300 mbps^ for under $50 a month. I think it speaks well to your point though: If I could get 10d/1u for $20/month, I totally would. I don't really use the internet that heavily.

^ usually around 100 mbps (100/100)
I just pulled my old dead-trees copy of the classic Fucked Companies book off the shelf to remind myself of the one I remembered dying in the first dotcom era:

https://m.imgur.com/dD4nOol
> They don't necessarily care about syntax errors or spelling errors, but they absolutely want working code.

I'm not sure how code with "syntax or spelling errors" qualifies as "working code." The fact that they don't care about those things is pretty much the exact thing I was trying to communicate.

Other things they probably don't care about: unimplemented placeholder functions (they might ask you to go back and fill those in if they thing it would be informative and there's time), or misremembered function/method names (though it's important to communicate that you know you don't remember).

I mean, obviously they do want code that demonstrates a well thought out solution to the problem. But no one expects that you could just copy it into a text file compile it, and have it run - that's what I meant when I said no one cares if you're writing working code.
Yeah. Everything I've read it's because they've lost the lobbying war with incumbents.

Incumbents (in those locations they are pausing) used their lobbyists, political connections, right of ways, existing contracts, etc. To block, delay and vastly increase the time and costs for Google. Driving Google to go wireless.

[edit] here in Austin (where they didn't lose the lobbying war) it's full steam ahead. They have been continually spreading across city. Dug trenches at coworker's house last week.
My gut reaction is always to wonder how a company this big can miss simple things, but I've worked for enough big companies to know how often critical elements of big decisions get delegated to a single person. You might think, 'how can a multibillion dollar company be so stupid' but it's really some guy named Bill who has 14 direct reports and can't even get enough server hardware unless he tells tall tales.

The soberest people in the organization don't get promoted often, and don't get their ideas approved because they are too conservative. They make small promises and say No a lot. Boring. It's always the loudmouth who goes off half-cocked that gets attention.
Yes. See, it works :)
The world's simplest facial recognition api for Python and the command line
> Games are a visual, interactive, skill-based medium; people who are less interested in these things will be better off with other media and that's fine.

I have a bit of a problem with this, because the most obvious group of people excluded from games is women (who mostly only play mobile games, which are interactive, visual, skill-based), and yet you seem to be implying that there is something "natural" about their aversion towards a visual, interactive, skill-based medium. I really want to fight against this argument of naturality, because it's been used countless times historically to exclude women from everything from politics to medicine and programming.

Surely if most "real gamers", for want of a better term, are not women, then that's the fault of the games, not the women? I think that's what Brie Code is fundamentally arguing about.
I want to improve on your metaphor-- I think that architects/construction crew is a bad one. Architects design on a house, but they also are very aware of the engineering constraints of how a building will stand, resist earthquakes, and generally is structurally sound. They learn how to do it in school, but when they work they tend to just use cheat sheets they get from wood & concrete suppliers. (source: my uncle is an architect)

I work with some designers who have _no idea_ how CSS works. Or they only have the vaguest of ideas. That's an architect who is handing off pretty drawings and the construction foreman is also doing structural engineering checks on the fly.

I don't need a designer who can write code full time, but I wish that all of them were forced to do a course in layout with css. Obviously flexbox is solving a lot of this pain, but I think it would still be beneficial.
The video is very well done imo. However, it's only a small part of the overall marketing strategy.

What kind of marketing did you do? e.g. what kind of coverage did you seek / get?

What kind of market research did you do? e.g. did you do user studies and get feedback?

How did you determine the selling price? e.g. did you determine whether it was too low (if customers are price insensitive, then you can increase profit by increasing price) or too high (if customers are extremely price sensitive, then you have to accept lower unit margins to increase total profit)
already on the front page... https://news.ycombinator.com/item?id=13876208
> like WebSockets

Does that mean simply using vanilla socket.io means the page will not benefit from this?
While I haven't read the contract, that is a definite possibility. Most applications that require an 'Oracle' (a trusted source of information i.e the bot) can be written in a way that a deadlock would occur if their service was down, for example. That being said, a smart-contract can be written to give refunds in the case of an expiration, disallow the maintainer from cashing his own pull requests (though he could make another account), and other logic like that.

It's very powerful; but when the smart-contract world interfaces with the unpredictable outside sometimes the logic doesn't line up.
Music makes curry 10% spicier, scientists find
> I think that's just a function of the fact that Kotlin's so much less mature all-round

You mean "old", not "mature". Scala is old and still pretty immature for its age

The Kotlin tooling and IDE support is certainly already way ahead of Scala's after just a year in existence in robustness and functionalities. And I'd rank the two compilers at about the same level in terms of maturity (Kotlin's is much faster than Scala's though).
Nvidia and Bosch team up to build an AI supercomputer for your self-driving car
From what I understood, Fiber wasn't a long term solution for Google. I think they anticipated that they could kick a American infrastructural movement into gear if they gave the other ISPs a real reason to compete.

I don't know if this is Google's response to those ISPs taking a different approach than they wanted, or if this is symptomatic of the company changing overall. Judging by the other ISP's marketing campaigns, competition doesn't seem to be the real message. That's a whole other can of worms.

I would venture to guess that given older company's paths, that it's the latter, and the problem is that they don't want to take big gambles like that; play a more conservative game.

It could also be a number of other factors. Maybe Google thinks Trump is looking to make good on infrastructural promises. It would be prudent of Google to capitalize on that momentum rather than spend their own resources.