skysight-inc/HackerNews huggingface dataset:
Are we're talking about a minimum wage for SWEs now? I mean what, specifically, are you suggesting? Employers can't hire people who bid lower?

Salary in the tech industry is a function of demand. Right now, for example, people with expertise in Machine Learning are in high demand. You can graduate with an MS or Phd in machine learning, form a startup with no product whatsoever, and get acqui-hired just because of the insane bidding war going on right now.

When I moved to SV in the 90s, at the height of the dot-com boom, kids fresh out of college were getting insane signing bonuses worth $10k or more. I knew people who would switch jobs every few months, just to collect freebies.

Perhaps it is different elsewhere, but here, tech workers are very highly privileged. Seeing people complain about a desk job that pays $100k+, weeks vacation, great healthcare and benefits, flexible working hours, compared to the utter suffering that's happening in the working class across this country just looks tone deaf to me.

Before we worry about the poor suffering tech workers, in their gentrified neighborhoods, in swanky cafes, facing stagnating nominal wages, how bout we consider the masses of people who missed out on the tech-utopia for the upper 10%, people who would like to move up the value chain, and have a right to compete for your job.

My mother worked as a cashier at Safeway before she died. Comparing my hourly wage as a SWE to hers is kind of obscene, and for the people I grew up with, seeing tech-bros complain about their current threatened position has got to look like people completely ignorant of how much privilege they have.
I think they have something that works, it's just difficult to make it into a product etc..
And people wonder why everyone goes for the startup lottery ticket
Airbnb teams up with developer to launch branded apartments
That seems likely to be true, coupled with the fact that wealth means greater selection in their entertainment.
Just apple notes for me. It's perfect as it syncs between all of my devices.
Show HN: Openbloc: playing with React, D3, SVG path animation and morphing
Cuil had great PR? When?

Color had marketing hype but as far as I could tell no-one outside of VC circles took it seriously.
Podcast episode explains how blockchains work
Wow, that's an amazing resource!

And I've always wanted to put Battle Chess on something modern :D

...oh, 404 dead link. Well, at least Archive caught it and Google does still seems to actually host the files: https://storage.googleapis.com/google-code-archive-source/v2...

Someone backed it up, too: https://github.com/linhlc/openbattlechess

But jeez, linkrot is going to be a huge fucking problem.
I agree with all of those notions. But again: Every retailer I connect already knows my name and email address (I have an account with them), and I pretty much talk/post about what I watch online publicly to begin with.
> Kyle’s testing found two new bugs: one in CockroachDB’s timestamp cache which could allow inconsistencies whenever two transactions are assigned the same timestamp, and one in which certain transactions could be applied twice due to internal retries. Both of these issues were fixed.

Source: https://www.cockroachlabs.com/blog/cockroachdb-beta-passes-j...

If you're speaking to "Linearizability violations such as stale reads can occur when the clock offset exceeds CockroachDB’s threshold." from section 2.1 in Aphyr's analysis[0], this too is touched upon in the post above:

> loose clock synchronization is necessary [...] to guarantee serializability. CockroachDB servers monitor the clock offset between them [...] although this monitoring is imperfect and may not be able to react quickly enough to large clock jumps.
All CockroachDB deployments should use NTP to synchronize their system clocks [...] the default of 500ms (increased since Kyle’s testing, when it was 250ms) to be reasonable in most environments, including virtualized cloud platforms.

[0]: https://jepsen.io/analyses/cockroachdb-beta-20160829
If the Ferrari could any day start up and tell you that it would drive away if you could not pay the price difference down the line and leave you with no car because it found someone else who would pay market value, I think you might in fact think twice about buying it at discount.
Yes, but that assumes you're not competing with anybody. If you are, then why shouldn't you put your incidental "extra-curricular" credentials up front?
That is incorrect. The SEC regularly pursue people for insider trading [1]. It's one of the things that's normally pretty clear cut and hard for politicians to lean on.

1. https://www.sec.gov/news/pressrelease/2016-212.html
Right, but we know there are all kinds of reasons people quit jobs quickly. The question is probably whether someone legitimately "overqualified" is any more likely than anyone else to leave in a particular timeframe.
>>it's not even racism

>>work experience outside Australia gets discounted as "not real work".

I mean, that might not be the strict definition of racism, but it essentially is.
I remember Cuil when it launched. Ex-Google people starting a next-gen engine. They had the right credentials and everything.
It's ironic seeing this hosted at Facebook, the land of "young people are just smarter".*

*The infamous quote from Zuckerberg
>The "traditional understanding" of getting an applicant to your job that is over qualified is that they are just trying to get a paycheck while they look for something better.

Is the solution here to bias the "overqualified" candidate's compensation in equity rather than salary? If the company thinks that salary x is too low and may tempt the person to leave, put the employees skin in the game to stay with more equity. This seems like a potential solution.
The problem is that many interviewers don't know how to suss out a good engineer. So they just ask questions that Google and Amazon ask. And that's why you spend half of your interview pre-optimizing contrived algorithms down to O(n) when the probability of the startup ever running code at scale is very small.
In general older developers have a higher 'monthly nut' (as do older folks in general). This is obviously a generalization, but things like saving for retirement and housing costs are higher the older you get.

Of course, it is up to the employee to determine if they can handle their expenses on the salary granted to them. However, just as an employer may look at something like commuting time and say to themselves "wow, they're going to commute for 2 hours, that's going to be tough", an employer can look at someone who is older and assume more expenses and say "wow, they might be digging into savings, that's going to be tough".

Now, that should be just one factor of the hiring equation. And someone may be interested in transitioning fields, doing a startup, have a trust fund, live well below the normal standard of living, etc, etc, and may be ok with the salary.

But as an employer, hiring, you aren't just looking at what the employee is saying now, but trying to figure out if/when they'll be moving on (and picking someone who will be less likely to do so is just human nature--that's why job hoppers are looked down upon by some companies).

That said, how can you combat that? (I'm in my early 40s and am terrified of this.)

* start your own company

* consult

* don't job hop, settle into a company

* keep your skills up to date

* be productive enough to justify the extra money (be a true 'senior' developer)

* move into management, again, a higher leverage area.

I don't know, maybe there are other ways.
Why would the pylons need to move? You can essentially have tube sitting on top of the pylons (which I expect could have ~50 degrees of contact area). You could even have it sitting on rollers between the pylons and the tube.
I've spent some time experimenting with React D3.js and SVG animations for a new version of my personal website. This is a WIP but I figured I might post it if it's of some interest for people working in this space :)

the code is there: https://github.com/blaze33/openblocv2/tree/master/src
Back in the day, I remember using Glide wrappers to run the UltraHLE emulator on non-3DFX hardware. Now, a lot of older games need a DirectX shim to fix various issues (palette and some kinds of slowdowns, especially).
On instagram, It is easy for an account to come out of nowhere in hashtag promotion.

Just like I was explaining it can basically bake in followers while private. An account can go from 0 - 10,000, or 20,000 pending followers almost overnight, but more practically in a week's time. This won't register on any analytics site.

The account can accept as many of the new followers as it likes (this takes time though) and can make a new post and stack it with hashtags while private. The post will begin getting a lot of likes in a short time span, and then the profile can go public.

For maximum efficiency, this should still be in conjunction with at least one other campaign, still funneling new followers in while the account is public. The post will go to the popular section of every hashtag except the most popular hashtags, as well as trend in the explore section for many users who don't follow you yet.

Given the way that campaigns work, using stories and tags in photos, these should mostly be human followers.
I'd hire in a second anybody who's thought this hard about how to critique their own code.
I'm seeing this now. I'm 48 and have applied to over 100 jobs. I have an MBA and have been well-qualified for every one of the jobs I've applied to, or else I wouldn't have wasted my time. I've had about 5 legitimate responses. I know it's not my resume, or much else. Age is just about the only answer, or not being able to afford me because I'm "over-qualified" which makes me wonder why they're advertising for the position, if they don't expect to hire a qualified candidate.
It's true that if you always do the same kind of programming work, you might get bored and this can negatively affect productivity (in terms of raw speed)... But on the plus side; your code will likely be of very high quality and will almost definitely save the company a ton of money in the medium and long term.

So yeah I think that calling someone 'overqualified' is a poor excuse.

Startups love code monkeys that can churn out features quickly; they're often willing to sacrifice huge medium-term benefits for small short-term benefits but that's idiotic. From my experience, it only takes about 3 to 6 months for technical debt to become a major problem so unless you expect your startup to have an exit in the next 3 months then you really should not accept any short term solutions at all.
The first fake account is impressive because it links to a real Facebook account. Don't they have any kind of verification?
I had a similar experience in high school. I took a "Technology" elective class where most people were just playing Warcraft III because the teacher didn't really care what we did. I don't remember him actually teaching us anything.

A few of us spent the time working on our own real-time strategy game written in Java and using Anim8tor for 3d models. By the end of the year we had a map, artwork, and some network code to allow multiplayer. You could place buildings, select units, move, attack, etc.

My friend found the source on an old USB drive a couple years ago and we were able to get it running again. Some of the code was hilariously bad, but we were both impressed that we had been able to get that far and that it worked since we didn't really know what we were doing. Fun times :)
Even the SF city has been unbelievably smoky the last couple of days.
How did you get to bragging about one's education/experience? Or that someone needs to control their ego?
> Okay, we'll bookmark this for the future. Amtrak estimated a HSR/"bullet train" from D.C. to Boston would cost ~$151 billion. Since LA to SF will only be two stops, and we can assume Amtrak estimated at least 4 (Philly and NYC) let's bring the number down closer to $100 billion to make it even.

You're starting with the wrong number. The $151B number is Amtrak's estimated cost for it's "shoot for the stars" plan. Its basic NEC stretch plan is effectively 4-track corridor (shared with commuter rail) from DC to Boston, with new stations and new inner city track being laid in Philly and Baltimore, two new Hudson River tubes and a new station annex in NYC, among other less notable improvements. I don't recall if the "abandon current Connecticut track and instead go from NYC along Long Island and tunnel under the sound" plan is in that tier or the next one. The stretch tier is somewhere in the region of $70B.

The reach for the stars tier is "do all that, and then build a parallel 2-track dedicated HSR track from DC to Boston." That's $150B. Which means building dedicated track from DC to Boston is only $80B. The estimated full buildout for CAHSR (including San Diego and Sacremento) is around $80B, as I recall.
The general notion seems to be that when you implement a service like this, you know it will be exploited to some amount, but that the amount will be negligible compared to the percent of well-behaved users.

The DMA/MA disconnect/reconnect method can actually be used to share movies permanently too, since each title remains on both sides when you disconnect, and a connection shares all your titles across both ways. Say you connect Vudu to MA today, and six months later, you can disconnect them, and use your MA account to share with another Vudu account, and your Vudu account to share with another MA account. Six months after that, each of those can split off and share with others... Add the fact that there's four retailers and this is extremely exponentially gameable. My hope/assumption is that Disney bothered to develop some sort of way to look out for abuse, but they might just be assuming it won't be commonly exploited.
Folks,

Thanks for raising the issue - we have fixed the mailing list (google groups) so now posting is allowed even for users that haven't yet joined the list.

For completeness:

- This is the mailing list archive https://groups.google.com/a/symphony.foundation/forum/#!foru... (fairly new, but we can't wait to see your traffic)
- To subscribe to the list just email plexus-interop+unsubscribe@symphony.foundation

We will follow up with a much more comprehensive set of technical information, but in the meanwhile all docs are hosted at https://symphonyoss.github.io/plexus-interop/.
Oh goodness. Monopolizing your time is part of the value of driving, for me - it gives me something to do while I'm waiting to arrive at my destination!
Storage and Networking != SWE, and these surveys cover a much wider ground than particular tech hub job markets, and do not adjust for purchasing power parity/cost of living.
And, if that's the case, what's the best way to approach said developers to ask if it might be made available for some kind of preservation?

There are a lot of old games that I'd like to see the code for, at least for curiosity's sake.
I’m not quite sure Uber ever intended for their drivers to be able to own $900,000 homes (that’s about what a $4k mortgage would get you with 20% down). To me that smacks of a very rigged game with some sort of agenda behind it.
Hey @zeveb, I appreciate the response!

But the grandparent actually mentions the short-lived approach, and is asking about cases where you want to have longer-lived tokens. And where you still want to be able to revoke them.

Stateless tokens can definitely speed things up. But if you end up needing to add state back into the equation for revoking tokens, then I'd argue that most web apps would be better off sticking with the much simpler mental model of non-stateless tokens. That is, until they decide that their lowest-hanging performance fruit is the extra validation work, and that it's worth complicating their architecture to remove it.
What was the relationship between you and the person who gave that advice?
No licensing shenanigans - as per our bylaws https://symphonyoss.atlassian.net/wiki/spaces/FM/pages/11797... we currently only accept contributions under the Apache license v2.
If taxi companies produced marketing material like this and promoted it in cities where they wanted to fight off Uber, they’d probably have a much easier time.

That was entertaining and sickening all at once.
But the point is that the pay is the same for the younger person and the older person.
$10 regular price is well spent.

http://store.steampowered.com/app/285330/RollerCoaster_Tycoo...

https://www.gog.com/game/rollercoaster_tycoon_2
software dev is too outsourcable for unionization to make sense. Also, real engineering professions are protected by licensure requirements and furthermore, their labor by nature of the discipline cannot be shipped out. Software is too global and portable to protect like that. So, lets enjoy the good times while they last.
A couple of things:

1. I don't see how that applies to the analogy of higher maintenance costs.

>if you really want/need a job that doesn't require your education and experience, then you can't brag about your education and experience that is irrelevant.

2. That is a double edge sword. If one removes expertise to pretend to be junior, then they are vulnerable to a junior who inflates their resume to appear more competent.

3. Also, putting your past experience isn't bragging, it's, as you said, honesty.

It's good business to (all other things being equal) hire the best person you can find at the price you can afford. To do anything otherwise is nonsensical. I can't think of a good business reason not to.

Having said all of that, I'm so glad I haven't had to use a recruiter in nearly 20 years. It sounds like a cluster out there.
Hopefully in the next few releases Kubernetes as well will be able to give pods unique cryptographic identities that can make securing individual nodes even easier.

Projects like cockroachdb are one of the key use cases we keep in mind when we look at how Kubernetes can evolve to make apps more secure by default.
One option is to modify each of the utilities so that it doesn't have a full representation of the whole tree in memory. I doubt this is feasible in all cases, though for something like 'git status' it should be doable.

If the tree object format was required to store its own path, then you wouldn't be able to repeat the tree a bunch of times. The in-memory representation would be the same size, but you would now need that same number of objects in the repository. No more exponential fanout.

But that would kind of defeat the purpose of Git for real use cases (renaming a directory shouldn't make the size of your repo blow up).
You could just lie about the gap.

And to do it without lying you can remain perpetually employed at the random consulting firm you coincidentally founded.

MANY OF YOUR EMPLOYED PEERS HAVE DONE THIS
Mostly arrogance that stemmed from the belief (unfounded or otherwise) that they knew more than others and therefore can refuse to do certain (usually unpleasant) tasks or order people around.

For example we had an analyst join the business intelligence team recently, and unlike everyone else on the team she has a masters in finance as well as many many years of experience. She refuses to run financial forecast reports for the executive team because she thinks such tasks are below her, and that others should run them instead. Really nice girl otherwise, but just terrible to work with.
None? You seemed to have touched mostly on consuming CSV and safe ways to do that and suggested XLSX - I'm just adding that digesting CSV safely isn't our biggest issue, it's getting vendors to use something other than CSV and unfortunately that is typically out of most people's control.
Whenever I see analogies all I can think back to is Dijkstra saying how theyre a good sign of medieval thinking. We shouldn't resort to analogies; They obscure case specific information.. or in other cases also allow us to draw parallels that aren't very apt to the case at hand.
In fact the more general N-body problem is perhaps one of the most classical uses of high order Taylor methods, in particular for studying the long term stability of the solar system. Here is a paper from 1993: http://adsabs.harvard.edu/full/1993A%26A...272..687L. Rigorous error analysis of Taylor methods for ODEs goes all the way back to Moore's original work on interval arithmetic in the 1960s; in the early 2000s Makino and Berz developed so-called Taylor models which combine rigorous error bounds with accurate long-term propagation of changes due to perturbations in the initial values (see http://bt.pa.msu.edu/index_TaylorModels.htm); they used it to study the dynamics of the solar system among other things. R. Barrio and others have published several papers about reliable solution of ODEs using Taylor methods; leading to the development of the TIDES software. See several references listed on http://cody.unizar.es/tides.html. In particular the paper https://doi.org/10.1016/j.amc.2004.02.015 from 2005 investigates using variable order Taylor series with extended precision for the solutions of dynamical systems. The paper http://dx.doi.org/10.1155/2012/716024 from 2012 is specifically about obtaining periodic solutions of dynamical systems using a high order Taylor method with multiple precision arithmetic.

Actually, I made the first comment after I checked the second author's earlier paper https://arxiv.org/abs/1109.0130 where they essentially made the claim about inventing "CNS" as the first-ever reliable technique for long-term solutions of dynamical systems, without referencing any of the earlier work I mentioned above.

However, I just checked the actual text of this new article on the three-body problem (through sci-hub) and there the authors do cite the earlier work I mentioned above, giving proper attribution to others for the basic ideas behind what they call "CNS"! So all is actually well, and the peer review presumably did work (or the authors found out about the earlier work even before writing the new paper). It is just the press release that is misleading, as usual.

To answer your question, I'm not really familiar with the research on the N-body problem, so I can't say why or whether no one tried looking for periodic solutions in this way before. Perhaps no one actually thought of it, or they didn't try since they didn't expect to find anything, or they didn't have the computational resources, or they just couldn't figure out the details of how to do it (which the present authors did, and deserve credit for). Again, I was not trying to downplay the significance of this work, and finding new applications of existing methods (and making even tiny improvements along the way) is how science progresses. It also happens all the time that methods get rediscovered/reinvented independently.
"Disparate Impact" is not about fairness. It is about non-arbitrariness. Factors that are demonstrably job related for the position in question and consistent with business necessity are considered a suitable legal defense.
Rose McGowan Lashes Out at Amazon CEO Jeff Bezos in Twitter about Weinstein
maybe so, but i found it helpful
> ... we are more enlightened.

We have always believed that.
It also narrows the number of use cases you have to account for which gives google time to flesh out the platform one use case at a time - something the consumer market simply wouldn't tolerate
Yup. Was written about 20 years ago. I'm an amateur.
The course of technology strikes me as useful, but this paragraph particularly resonates:

True AI has the genuine potential to render the great mass of people not just superfluous but an outright burden. There will be no reason, in a politico-economic sense, for most of them to exist since neither their labor nor their vote will empower the ruling class. There will no longer be anything to stop the powers-that-be from reproducing and extending the "solutions" that have repeatedly occurred throughout human history across many times and circumstances: from Stalinist Russia to the pogroms of medieval Europe to the Khmer Rouge to the Rwandan genocide and on and on.