skysight-inc/HackerNews huggingface dataset:
Absolutely amazing that's what you see. Tesla shareholder, friend?

His main complain is mandatory overtime, bad production flow, dangerous working conditions, frequent injuries, and management refuses to listen to feedback. In short, it's a dangerous irresponsible sweatshop from the 19th century.

Will moving the plant to Tennessee or Nevada help because you believe there are no federal labor regulations or safety considerations in those states?
Should be titled: Finding out how awesome Postgres is (the hard way)
UX is objectively measured. I don't know why people think it's subjective.
The article talks about more than mere code efficency.
3. It helps when speedreading/skimming, for me at least. Pullquotes done right can let me work out the gist of an article, such that I can subsequently decide if it's worth reading further.
Diversity at Vimeo
Makes sense, but how do child processes not have access to the secrets files?
How are we getting screwed? (and I agree that the salaries are pretty low compared to the other cities).

Also, the dollar being low doesn't help.
I love the text at the bottom:

> No ads! Instead, please support the ACLU
I still like the neat Pajek. Nifty little piece of software, unknown by most, but really powerful! Especially if you are into social network analysis. Who else uses it?

http://mrvar.fdv.uni-lj.si/pajek/
Solving the quantum many-body problem with artificial neural networks
If you want to skip directly to running code, these instructions (linked from the article) should get you to hello world. https://github.com/fauna/serverless-crud#installation
you could say the same about SF and LA. but how far are you willing to go? problem is for austin these areas are included in cost living considerations.
The average salary is 73k£. 84k£ is adjusted to the cost of living in SF.
Looks like the fact it automatically scales horizontally: with Aurora, you can only scale vertically (in terms of memory and compute), and DynamoDB requires you to manage throughput yourself (not a big deal; there are services to automatically raise and lower it based on usage).

Without interruption -for a minority of nodes-. Meaning it's using a quorum to achieve consensus. In the event of partition (which looks the same to the remaining nodes as a 'loss'), the majority side will still allow reads/writes. Meaning if you can't talk to the majority, you can't read/write; hence, not AP. If it maintains distributed consistency provided there's a quorum (Raft, Paxos, etc), it's CP.
If you look at what NIFs exist up to this point and where Erlang itself tends to use that mechanism, they are all for very tiny uses, like type checks and such. But that's probably precisely because they're too scary to use for anything very large. The existence of a provably-safe and practical mechanism for writing them may cause and/or require some changes in the ecosystem to account for the fact it's now possible to write NIFs that may take a long time to run.

I wouldn't be surprised that at least one of this library or the Erlang VM itself develop an official way to easily use a NIF to run a longer-running process safely. There hasn't been a need up to this point because there hasn't been a such thing as a long-running NIF.

At the moment, if you're looking at something that may take several seconds you're probably still better off coordinating something over a port to an external process or something. Or working with this project to make it feasible to run a long-running native process.

Trying to write a NIF that could somehow yield back and then be "continued" later would be a royal pain. Cooperative scheduling was enough of a pain when we were in the hundreds of processes mostly doing nothing on OSes; trying to use it on an Erlang server is probably just infeasible.
We built a simple iOS app with react native
Imagine this scenario.

You work on product A. Your VP of very important things declares that every product should use library L. Library L has been designed to incestously interact with product D and makes a bunch of assumptions about what the "working environment" should be.

Teams B and C have already made the transition, so L made some kludgy APIs to make B and C interaction possible, though it is maintained with low priority because everybody knows D is the money maker. Both B and C have a bunch of assumptions in common that A does not share, and they both had to compromise and emulate D environment to some exent.

You are given L binaries, a few toy examples of how to use the most basic functionality in L, and access to B codebase. L codebase does not use the same source control system, so you don't even know where to begin looking for their code.

Please keep in mind that your manager does not expect you to learn all the inner workings of L. Your priority task is to use L to support some new feature in A. You still have a number of other tasks to accomplish in A that are not related to L, and some of those might raise in priority with little or no notice.

Do you still think it is a good idea to just browse L code, without knowing how large (or well writen) it is?
The key part of that, that makes it obviously morally correct is:

> if it's necessary to do so

There is no road in the context. It's either sacrifice the small group, or save the whole - that's the entire proposition. If you remove the necessity part, that changes the equation entirely.
It is that bad. But there's huge variance - renting a 1BR in the mission is far cheaper than south beach.

You don't have to spend the "average".
I actually do believe it and that's why I reserved a model 3.

Maybe I just bought into their rhetoric, maybe. But I believe that the company's vision is more directed at sustainable transportation rather than profit.

They have worked really hard and brought in a lot of investment working towards an electric car. If Musk was truly profit driven he could have made a lot more money, a lot faster by directing his energy elsewhere.
When did you buy? I don't think you'd be able to achieve that today except in the shady parts of Oakland.
Yeah the company has a big purpose, but it's ridiculous to ignore something like this. Do you think a majority of the factory employees or even engineering employees, for that matter, care about the "big goal"? I assure you that they don't. Early on in the company, yes, a majority felt that way, but now its an established corporation trading $ for labor. If they don't care about their employees, many of them will go elsewhere, which isn't in Tesla's interest for the time being.
It's the business-as-usual attitude and acting as if nothing happened right after a catastrophic event that riles people up.

Transparency is fine. Eventually moving on is fine. But right now people are interested only in one topic when it comes to Gitlab.
AI Podcast: Bringing AI to Cybersecurity – Dr. Eli David, CTO Deep Instinct
It's pretty bad, but the list of contenders in "worst UI" is quite large.

It feels like they took some Photoshop files from a designer and gave it to their dev team and said "make this, I don't want to hear any complaints."
> VP of Engineering who asked me to code FizzBuzz on a whiteboard (no kidding)

I agree that a VP in a late stage interview should not be asking this of the candidate, but I will say that I recently had to hire a new team member, and FizzBuzz helped me to immediately weed out the candidates during the initial interview. I'm talking like 50% of the candidates, and one guy even asked if he could take it home and send me the code. Another acted like I was asking him to produce something for the company for free, before even reading the three lines of requirements, and then tried to back peddle when he did read them - of course, I was already holding the interview room door open for him by that time. All told, a FizzBuzz test in the initial round saved hours of my (and their) time.
maybe you should start a scholarship fund for them....you know, be the change you want to see and all that.
> It would be sensible to sacrifice the well-being of a small group in order to save the whole, if it's necessary to do so.

Your confidently declared decree of fact here suggests that you have some sort of god view that allows you to see all possible outcomes and interactions in all possible worlds.

It's also possible that sacrificing the people who actually know how to make things in order to facilitate profit and ego will lead to the annihilation of the society.
I could only try to clarify the same principles a bit more. Non-falsifiable and non empirically verified hypothesis does not amount for a science and constitutes a set of beliefs similar to religion among a community of its followers. As long as there is absolutely no way to reliably test or even measure, leave alone empirically validate anything, this set of beliefs is technically is a non-science and should be explicitly named as mere speculation.

My first comment was the claim that what we deal with is a socially constructed phenomena, similar to a religious belief or a mass-hysteria because it is a) cannot be tested and b) constructed by a certain social group. Technically, I do not see any contradiction in my claim.
Abandoning principles?. Why is it unethical to trade with neo-Nazis?
Please see this comment:

https://news.ycombinator.com/item?id=13605873

Nothing stops you from going full PFS.

In fact, you could even flip it around and let a shared notepad connected to the chat represent what you want to remember permanently, while the chat could remain ephemeral.

This makes for more accurate expectations and less risk of user error.
> My understanding is that if I still want to ensure that the Beam VM can continue to schedule all processes efficiently

It's worse than that, overlong NIFs can lead to scheduler collapse with your schedulers being put to sleep and stuck there.

> these NIFs shouldn't calculate forever, but return quickly to avoid blocking all other processes.

Recent BEAM (R17 and later) has the experimental feature of dirty schedulers which allows running long NIFs without risking scheduler collapse. There is one set of dirty schedulers for IO-bound NIFs and one for CPU-bound NIFs, they should be marked accordingly.

> I've no idea how big the overhead actually is, I'd be interested in a rough estimate. Is it small enough that I can just ignore it entirely?

https://news.ycombinator.com/item?id=10141945 and the linked article
https://medium.com/@jlouis666/erlang-dirty-scheduler-overhea... measure regular nifs at ~1.2µs and dirty nifs at ~10µs by default though they can be as low as ~3µs for core-bound schedulers and tuned wakeup options.
Webpack v2 Quick Start
His post election piece is the one I think back to most often:

https://theintercept.com/2016/11/09/democrats-trump-and-the-...
I'd suggest, make your first big goal to emit assembly, and use an existing toolchain to assemble and link. It gives you the opportunity to run your code much quicker.

if you can handle compilers, assemblers are a piece of cake. So you can add a flag to emit a .o instead of a .S when you get down to that level.

I've never actually written a linker, but when you're down at that level it's fairly obvious what needs to happen. There's some sort of binary prolog that indicates this is an executable. Then you have this table of symbolic names to offsets, you replace the symbolic references with actual numbers.

If you have something like a.o, b.o, and c.o, and a.o needs to call foo in c.o, it's kind of just sizeof(a.o) + sizeof(b.o) + offset(foo, c.o)

assemblers and linkers are kinda tough because they need to be perfect, but you don't have the hard algorithmic problems you have in compilers, like register allocation.

Also, if you limit yourself to a small subset of x86, you can pretty quickly verify correctness using existing tools, then make toy versions of your assembler and linker. Adding more instructions only means touching the assembler.

You can do it!
That's not nearly as common as you might think--among other things, it's a good way to ruin a several thousand dollar fursuit. (The best analogy I've heard is "Yes, there are furries who have sex in fursuits, but probably not more than people who have sex in space suits."[1])

The furry fandom is much less inhibited than general society--members tend to be willing to discuss sexual topics in a way that most people aren't. (This probably also accounts for the higher incidence of homosexuality[2], since it's not felt to be something that needs to be hidden.) However, the vast majority of furry-related sexual expression (as opposed to two people who happen to be furries having otherwise non-furry sexual relations) comes in the form of various types of media--published stories and images, but also private roleplay. In this regard, pet names based on animals are absolutely a part of "furry sex", certainly more so than dressing in animal suits during the act.

1: http://www.adjectivespecies.com/2015/08/29/yiff-murr-sex-in-...

2: https://doi.org/10.1163/156853008X323376; poorly-formatted PDF at https://archive.org/details/pdfy-vF2uQGRhrwdL1oe3. "...they are less likely to be heterosexual compared to other males in the study."
Probably not. It's a TLS connection -- if someone can lie about the contents of the DMG, they can lie about the hash too. How would it help?
If UX was fully objectively measured, wouldn't Gitlab, Github, and Bitbucket all look and feel the same?
Bender was a scab in Season 3 Episode 6.
At some stage the IRS is going start start taxing these benefits in kind (its easy money going begging) odd that they don't already as its easier to collect than going after dual nationals overseas

I could see Trump ordering this as retaliation
If someone has enough money, they can lease/buy an entire building (say a 50 apt building in NYC, Seattle or wherever) and let people live in those apartments (for $1/month in rent or something like that). This doesn't need to be a camp or tents in some remote place. This way people can live in those apartments with their families. In cities like NYC, rent is most normal people's biggest expense.

All it takes is just one rich person (there are many in tech) who believes in the idea (or some variation of it) and it can be done.

That said, I was mostly thinking of young/single people when I wrote it. People with kids have more challenges
I mean, really: after figuring out after the fact that five out of five backups were malfunctioning - go here to read our secret to managing 160 employees remotely?

Nah... no thank you. I think I will get my management advice from a company that is not totally broken. I don't care how transparent you are, or how remote-worker friendly you are, if you can't do the basics right. You are in the data storage business! Shut down the company and refund the money to the investors.
Towards a Semantic Language of Mathematics
The author of 'Hyperbole and a Half' also gives a fantastic explanation (the whole blog post is well worth a read, http://hyperboleandahalf.blogspot.com.au/2013/05/depression-...):

"I remember being endlessly entertained by the adventures of my toys. Some days they died repeated, violent deaths, other days they traveled to space or discussed my swim lessons and how I absolutely should be allowed in the deep end of the pool, especially since I was such a talented doggy-paddler. I didn't understand why it was fun for me, it just was. But as I grew older, it became harder and harder to access that expansive imaginary space that made my toys fun. I remember looking at them and feeling sort of frustrated and confused that things weren't the same... I could no longer connect to my toys in a way that allowed me to participate in the experience.

Depression feels almost exactly like that, except about everything."
Have you looked at the Go toolchain at all? I don't know much about it, but they implemented their back ends in a manner that is much smaller than LLVM and GCC. And it sounds like the architecture of the compiler is significantly different.

I watched this talk and it was pretty interesting:

https://www.youtube.com/watch?v=KINIAgRpkDA

https://talks.golang.org/2016/asm.slide#1

If I am understanding right, the claim is that they have a single assembly language for ALL GO architectures, based on something Ken Thompson wrote in the 90's for some National Instruments (?) chip. He actually says that all assembly language looks the same now.

I was sort of surprised by that claim. I would like to hear a critique of this from other compiler writers. Does the fact that Go uses a single assembly language make the code slower? I imagine taking advantage of target-specific knowledge is useful, but I don't know how much.

LLVM has this pretty elaborate TableGen system to express target-specific knowledge.

He also makes the claim that they will be able auto-generate a new backend from the PDF description of the architecture. And he says somewhere that they reduce a lot of the work to simple "text processing" (symbol manipulation) and didn't require opening up any processor manuals.

I can see how arithmetic and bitshifting is the same among all architectures. But I would think that even loads and stores have differences, at least if you want to use the processor efficiently. But he says everything kinda looks the same.

Also, another thought is that compiling to WebAssembly might be simpler than native executables?
Requirements were to allow internal and external teams the ability to CRUD a small set of resources using multiple programming languages, OS, and include command line scripting ability.

Direct access to our HIPAA/IRB database instances are based on white-lists - most internal and all external teams are prohibited from direct database connections. So for those groups, there is no possibility of any SQL access to schemas.

We use API keys with a shared secret (like AWS) to sign REST requests. If internal and external groups need to work together to jointly CRUD some resources for a specific project, they can share an API key dedicated to that project.

There was also a push to switch from an app-centric view of data management to an API-driven approach serving hypermedia (collection+json). That worked conceptually, but most API users ignore the embedded hypermedia links. I find that too bad, as those links make generic API consumption clients much more resilient to change - following a link embedded in a response rather than relying on POST to a well-known URI is a useful abstraction.
Finland heard you, President Trump. It's America First, but can we be 2nd?
Given the fact that every college in the country enacts affirmative action, it's apparent that non-whites and women would have no problem getting into the IT field. And given the fact that over 60 percent of people graduating college today are women, that tells me that it's just not a field they're interested in. I don't see why that's a problem.
You're assuming management is unaware of the problems, and is of their own intention wanting to fix the problems.

That's not necessarily the case. Managers often get bonuses for achieving goals that are only possible by treating workers poorly.

Until there is negative reinforcement for that (union walkout), there's not much motivation to change things.
"behaved poorly"? Care to give an example?
Do you have any 'good' sources on other complaints about working conditions? Honest question, quick google search gives me a number of results but nothing that seems to have meaningful follow-up of any sort.
Could you explain what the objective quantification of UX is?
Our impression was that when Databricks released the billion-rows-in-one-second-on-a-laptop benchmark, readers were pretty awed by that result. We wanted to show that when you combine an in-memory database with Spark so it shares the same JVM/block manager, you can squeeze even more performance out of Spark workloads (over and above Spark
's internal columnar storage). Any analytics that require multiple trips to a database will be impacted by this design. E.g. workloads on a Spark + Cassandra analytics cluster will be significantly slower, barring some fundamental changes to Cassandra.
Is this 52 hours / state? or does it cross license between states?
"Whooptydoo, but what does it all mean, Basil?"
One way is to revisit your old code, as you get better you'll see ways to improve it that you just didn't know before.
> It seems very calculated.

Union organization is very calculated. It has to be because union opposition is also very calculated, especially when it's done lawfully. It's calculated because there are very specific protocols that have to be followed that may or may not be enforced by laws with sharp teeth (depending on the state). This makes it very sensitive. Also, public relations is a significant part of the playing field. The company and the union are trying to use it to both bolster and gauge support.

With all that said, I wish the best for both parties in coming to an agreement where workers can safely and efficiently build cars that will eventually replace most gas powered cars with all its moving parts with EV cars with minimal moving parts.
Your point is extremely well presented. I see that those with no counterargument resort to downvotes, because that is all that people of small minds and reasoning can do, downvote.
...which is why unions depend on customers organizing a boycott.
He's the founder, so I guess it is a marketing post.
Definitely this. Saving 50% of a SF salary will beat saving 50% of a Toronto salary by a ridiculous margin. This was a huge part of why I decided to try to find a new job in SF instead of taking the first Toronto offer I had lined up after graduation.

I'd also like to see a comparison of the 90th and 10th percentiles of salaries to get a sense of the salary ceilings and floors in each region.
https://news.ycombinator.com/item?id=13609762
>Tesla is doing is much bigger than the individual. The company is at a crucial moment, they're about to scale up for their first consumer priced car.

How so? What is it that they're doing that is so special, beyond what Ford, GM, Toyota, Fiat, VW Group and a multitude of others are doing? They're building electric cars. All of them. Why do people think Tesla deserves "special snowflake" status?
I live in a Detroit suburb. Currently work there as well but know plenty of people that work downtown. Easy drive to downtown but there are plenty of jobs in very nice suburbs. The city is also nicer than you think. Still fairly rough but improving every day.
4 of my roommates work at Tesla and they all either underreport their hours by about 20% (work 60/week, report 50) or complain about their direct reports leaning on them to do so. It's really toxic! Tesla should be able to do well without stealing from their imported Canadian interns.
Ask HN: Best resources to get acquainted with the startup ecosystem in NYC?
What resources would the HN community recommend to best acquaint oneself with the startup scene in New York City? What are the best avenues to meet and connect with entrepreneurs for someone who is brand new to the area?
Judging from the Wikipedia article on blind wine taste tests [1], I'm not sure they're all that reliable.

[1] https://en.m.wikipedia.org/wiki/Blind_wine_tasting
Functions with parameters in a () is already in Perl 5. Search for subroutine signatures.

http://perldoc.perl.org/perlsub.html#Signatures
We detached this flagged subthread from https://news.ycombinator.com/item?id=13609988.
Honestly, I'll take that over the phone robot telling me "we care about your call" for the 152nd time. At least they're being honest that way.
Why don't you think I'm being serious?

I stated that I'm conflicted and seeing both sides.