skysight-inc/HackerNews huggingface dataset:
While the times are definitely changing, a lot of people are still very averse to finding a new workplace.

This means that even at a 1% raise per year, some people will stick around for decades. One of the best developers at one of the companies I worked for was exactly that kind of person.

For the company this means a large amount of extra profit year in year out.

The odds of you saying "Nevermind, I'm out" when they don't budge from a 2% raise are from the employers side pretty low. The odds of a new hire saying "Nevermind, I'm out" when unwilling to budge on salary negotiation is a lot higher.

Hence it becomes easier to give some additional leeway in that situation. Also if companies already have a large workforce, giving a raise to all current employees is a whole lot more expensive than giving more money to all new hires.

Lastly, there has been plenty of research that has shown that salary is not that big of a predictor of whether people stick around or leave in any given year. Whether that research is also true for software developers is up for debate, but it is what most companies rely on.

Lastly an anecdote, I was told by a manager once that if I wanted to get a significant raise, I could quit and come back as a contractor or "Senior Developer" after 6 months. At that time I was considered a junior, and promotion to senior was only possible after 10 years experience internally.
Compensation data from companies like Radford comes with three challenges

1. Your internal leveling scheme for SDEs needs to have been sorted out. External titles like "senior" are pretty meaningless, so one reasonable solution is mapping SDEs to an internal numerical tier so you can differentiate between "senior" and actual "senior".

2. Radford data comes with a trillion job titles. You need to identify the relevant ones and how your internal tiers map to them.

3. In markets where compensation is exploding (Seattle a few years ago), compensation data is a trailing indicator of what market rates you need to pay for new hires. You get fresher, but noisier, signals from candidates who reject your offers and from your personal network.
Accidental Ghost Kitchens Pervade as Restaurants Struggle to Reopen
This is the best resource I found that really explain what this whole electricity stuff is.
I spent years at in engineering programs and none explain as well as it is by William.
A lot of companies have budgets allocated to salary increases, so raises are capped. Why that’s the case I have no idea.

It’s also strange to me that companies aren’t willing to give a nice raise to an engineer, say from 150k to 180k but are completely fine with hiring a replacement at 180k.
My experience (I have been involved in salary/bonus/raise decisions) is usually salary is set based on the necessary amount to secure the engineer, which usually means at least their previous salary + compensation for taking the risk of a new environment with new people. I should note that I've mostly worked with small companies where these decisions are somewhat ad-hoc and non-standardized.

Raises and bonuses are based on how much can keep the engineer motivated and prevent them from looking for new work (I don't want to sound too cynical here, I think when it comes to measuring how much someone deserves in a raise/bonus is essentially how much it takes to keep the engineer providing this level of work, more or less) (based on management's assessment, and often constrained by general salary policies).

That's how I approach these discussions in broad terms, although keeping an engineer motivated and preventing them from looking for new work are not simple things to analyze
Yes absolutely. As with the exceptions on iOS (Netflix is outside the iOS payment system) i suspect it's a case that certain apps are large enough that kicking them off the store for not paying the 30% tax isn't feasible.

>Developers offering products within a game downloaded on Google Play or providing access to game content must use Google Play In-app Billing as the method of payment.

https://play.google.com/about/monetization-ads/payments/
I’m just finishing Eiger Dreams, what a great book! I wish Krakauer would write more recent mountaineering books.
I agree. Why do we even call it a "privacy policy"? It's more of a waiver.
This, most of the dangerous mistakes are just gags.

IIRC Mehdi admitted on reddit that the one time he really screwed up and was genuinely scared was when the Jacob's Ladder fell on him[0].

[0] - https://youtu.be/lT3vGaOLWqE?t=467
There is a lot more to the DNS protocol and packet structure than you are aware.

DNS tunneling is a well-known exfiltration technique which can place data inside of DNS request packets. There are several methods of placing the data in the request packet. In such a case the DNS query might appear as a benign request for IBM.COM's ip address.
I like this project a lot (and use it ocassionally in my PhD). I've tried this full profile Rietveld-esque tool [0] before, and it works pretty well for being so simple (at least from a UX point of view).

What I would like to see (and would program myself if I was a better programmer and knew more of the math and physics behind XRD) is a libre search-and-match program, using a peak database (in reality, multiple databases for different X-ray sources) constructed from the CIF files in COD.

[0] http://cod.iutcaen.unicaen.fr/
Real Life Customer Retention Strategies That Work in a Recession
But Goodhart's law applies to anything that's measured at all (it originates from the world monetary policy), even if it can be measured vey accurately.

https://en.wikipedia.org/wiki/Goodhart%27s_law

OTOH maybe quality exists as a qualitative concept but can't be measured -- then you just do pass/fail (like colleges have dropped letter-grades during the Zoomdemic).

What I'm saying is that "shallower" coders, who are motivated by the extra pay, may be more willing to align their concept of quality with the interests of the organization, while self-motivated coders will have their idiosyncratic or fashionable ideas.

When shopping around for a team to make a web app for my startup -- no technical requirements, we were feeling the market for price first -- we got a $$$ proposal for using PHP and Laravel, and a $ proposal for using AngularJS. I regret that decision; it cost us at least a year of time-to-market.

The original team quit (they worked for a trusted friend of our "business cofounder") because they weren't really experienced in web dev and their opportunity cost was off the roof - they were crack coders that did all kinds of different projects. Then we decided to hire someone (with good references) as a consultant and manage him ourselves. Dude was apparently capable but couldn't be screamed into using off-the-shelf components rather than rewriting and refactoring constantly. He eventually flaked on us, got too many projects and we weren't fun anymore I guess. Finally we found a small company online. By all appearances the new team hates being around computers but can be managed by Trello and feature branches. Web dev is a bore, but it's a living, and not everyone manages to make a living out of their surfing passion.
Sure, if you want to get a billion issues reported that are caused by outdated versions of the linters.
It's still a balance between compensation, interesting challenges, and good work environment. You can provide less of one if you provide more of the others, or less of two if you provide much more of the other.
You should pay them market rates to replace them (ie, much higher than you currently are). Yes, you should also foster their need for growth and learning, but that's because it's an investment in their productivity.

Investing in engineer's productivity, and paying them what they're worth, turns out that's all it takes.
> - the decentralised app requires the creation of a list of the "infected", which is synced to everyone

I don't think it works that way.

Here the requirements on privacy which became the accepted base for the German app:

https://www.ccc.de/en/updates/2020/contact-tracing-requireme...
One time I was day-dreaming while riding and realized too late that I was about to run a red light. I instinctively panic-braked and came to a stop right in the middle of the intersection. Fortunately there was no traffic around, but that one still haunts me to this day.
You Need to Prioritize Page Experience on Your Website
I mainly write embedded software rather than web stuff. I will say that the hardest to read and maintain embedded code I've ever had to work with was structured to use asynchronous chains of callback functions. It can get bad enough that you just can't fix a bug without dousing it with gasoline and lighting it up. Not to say that such patterns can't be used effectively, but maybe your former co-workers had some previous emotional trauma!
So what if underage slave labor is employed? Share holder value #1.
Boycott WWDC everyone. Trillion Dollar companies don't play by the fair rules.

Apple Music on Android requires its own payment details to avoid Google Play's 30% cut. Apple has accused Match, Epic, and Spotify of wanting a 'free ride' while taking one themselves.
> How come every time I switch jobs I get a 30-40% raise.

I see this frequently. I have a question: how many times have you done this? Don't you hit a limit at some point fairly quickly?
Roman Legionary – professional heavy infantry of Roman Empire
I wouldn't be surprised if a small part of the story is just that you only hear about big bumps from colleagues when they leave.

I've gotten 20-30% raises before but I'm not going to go around and tell people that at my current job.

However, if I find a new job and get a big pay bump, I'd be more likely to mention the pay bump (especially if I'm trying to soft-poach them :-) )
It's a learned behavior. It benefits employers to have employees squabbling with each other over pay rather than uniting and saying, "We'd like to talk with you, together, about pay". For some reason, the US in particular has a hard time with this.
I also wouldn't be surprised if there seasonality in medical care, like people receive worse care certain days, for some reason.
It's kind of odd that GitHub is asking people to pull an image from a Docker account that most people won't recognize (admiralawkbar/super-linter), as opposed to an official GitHub one.
Not sure if this is supposed to be a marketing plug or generate discussion?

Either way, the company would’ve been better off making a blog posting and posting HQ images of what they can do. The images on the site kind of suck and you have to go digging
anchoring and information asymmetries (+ information hiding). they're everywhere and especially all over labor markets. where there is information, it's thinly dispersed and often of dubious quality. anchoring is an easy heuristic to fall back on in those kinds of situations (on both sides).

plus, margin contribution is basically impossible to determine on an individual level, and wages therefore devolve into fundamentally political arguments (as in, expressions of power and influence).

you're expecting a (more) rational market response, when the labor market is anything but fair, free, and transparent, and coerced into that form over centuries by those in power.
I've heard argument pretty often, usually as rationale for the policy decisions taken by the Obama administration. Its flat wrong in the case of DACA.

Congress has acted as a deliberative body and discussed wide-ranging immigration reform packages several times over the last two decades. They couldn't come to an agreement specifically because the legislature's makeup correctly reflects the disagreements among their respective constituents.

Not-a-bug / working-as-intended.
Lab-cultured meat is caught up in red tape
> It may be in a culture lacking enforcement of minor rules results in more people feeling free to transgress rules that actively benefit them, but that is a second order effect.

Not just that, but for example, it will leave distaste in the abiding workers mouths. "I came here every day, respect the dress code, and that lazy bastard does not?".

So, don't really make rules that take much effort to enforce, or leave more open interpretation for small things, "common sense".

I don't know the answer, but a lot of minor things makes a big bad thing.
I feel like much of the debate about this topic focuses on how corporations hide what they are doing to us, and reforms would focus on making the language easy to understand like a nutrition label. However, if that reform passes, all that will happen is that all major corporations will in lockstep offer nearly the same terms and force us to take them.

The problem isn't their sneakiness, it's their power. You can't even begin to conceive of a possible solution to this that won't be undone within a few years without asserting popular control over the decisions of a corporation.
Forcing Apple to make their operating system work the way you want them to is like forced speech or forced labor,

Legally, it's nothing even remotely like forced speech or forced labor. It's simply the application of neutral laws intended to foster commercial activity by prohibiting anticompetitive activity, such as that engaged in by Apple in running its app store.
Outdated version could simply be counted as nonexistent, then a new version would be installed "as needed".
The straight and boring answer is budgeting.

Either the system allows for it, or it does not.
Deno 1.1 Released
Very exited about this!

Schedule is not published yet, but according to the organizers [1], it will be, hopefully soon.

[1]: https://forum.nim-lang.org/t/6428#39774
much easier to dodge ineffective HR (whether by their own incompetence or organizational inertia) and insecure managers by jumping ship (and optionally asking for a life raft if you want to come back)
Fault <> hypocrisy.

You can be blameless and still be a hypocrite. Is Apple at _fault_ for this action? No. Corporate entities are gonna corporate entity. Does this reek of hypocrisy? Yes.
Ask yourself, did you provide a 40% increase in value in the last year compared to the year before? Probably not.
For another company, that possibly desperately needs a new employee, you might have the value that without you the added income will be zero, with you... More then that.
Note its not strictly-speaking necessary to learn any linear algebra to "understand" quantum computing, there is a very simple but universal set of string-rewriting rules.

I realise for this audience most people wouldn't get much from it, but I find these rules useful for explaining quantum theory without annoying and fluffy analogies to high school students. You can find the rules in my book _Q is for Quantum_ - Part I which covers quantum computing is a free download on the book website (and the rest will be if I ever get around to producing a corrected pdf, bleh, but if you read part I and don't want to pay for the rest let me know and I'll get it to you...)
> It’s also strange to me that companies aren’t willing to give a nice raise to an engineer, say from 150k to 180k but are completely fine with hiring a replacement at 180k.

This is literally the story of my professional life.
> You could do the same thing with the application binary itself and have them compare hashes.

This is not scalable to software updates, which happen much more frequently than (long term) key updates.
With hashes you would need to publish a new hash for every update, but with public keys you're fine.

> You could get the same benefit from publishing only the hash of the software on the separate server. The signature is redundant, and is in fact worse than the hash because it introduces private key compromise as an attack vector.

Similarly to the issue I mentioned above, this introduces a hassle because the hash will change every time you update the software, which means you will need to update it. In addition, the system serving the hash/key should have some additional safeguards for updating it (because it's somewhat more sensitive), making the update probably more cumbersome.
Could you clarify what attack is possible with keys that is not possible with hashes?
The point is that lately Apple has been applying their own rule that disallows payment workarounds resulting in a few of high profile (for HN) cases. On the other had it seems Apple itself is using the same type of workarounds for their apps in other platforms (Google's in this case).
The App Store is different than in your example. In your example, I could put up a store myself called Toilet Paper Warehouse, and probably be successful in that town given that nobody else sells the toilet paper consumers desire. Whereas if the App Store is Walmart, then the iPhone is the town, but the town has a law on the books that says "No stores except Walmart can be in this town!". Consumers don't get the toilet paper they value, and Walmart can control the supply. In exchange, Walmart makes sure that nobody sells toilet paper with poison ivy on it, and guarantees that residents will have to go to the bathroom less than if they sold non-Walmart toilet paper.

The problem is that the iPhone itself isn't a monopoly. You can buy an Android phone that can access any store and install any app you want, so monopoly law doesn't apply (in the strictest sense). Now, one could say that you shouldn't have to move towns just because your favorite toilet paper isn't sold. But as it stands today, you have to, as I understand it. (With that being said, Apple, start acting right.)
The GitHub terms of service[1] have a pretty good format. However, the summaries are often too vague -- they describe the type of content instead of summarizing its contents, so it's still possible to hide unsavory details. For example, section R2, on assignability, is grossly imbalanced.

I co-authored the Snowdrift.coop terms of service[2], which we adapted from GitHub -- we could not afford legal review and figured GitHub has enough lawyers to make sure the CYA language included was thorough enough to cover us pre-launch (we will get legal review before processing payments for outside projects). There was some legalese we'd prefer to remove but didn't feel comfortable without legal counsel, but the summaries are non-binding so we rewrote many of them to be more descriptive. Curious what you think!

On the privacy policy[3] side, we agreed with you -- if our policy was long or complicated enough that a summary was necessary, we were doing something wrong. So we just described all the ways we collect personal data, in "If you X, we will Y" format. For example,

> If you create a Snowdrift.coop account, we store your email address and use cookies to keep you logged in.

I wish more sites had policies like this, so that "long and unreadable policy" would become more of a red flag.

[1]: https://help.github.com/en/github/site-policy/github-terms-o...

[2]: https://snowdrift.coop/terms

[3]: https://snowdrift.coop/privacy
Top Venture Capital Firms in the Bay Area
The roles of arrogance and loophole finding has changed recently. Apple (2020) has become Microsoft (1998) and Microsoft (2020) has become Apple (1998).
Although, not exactly what you're hoping for, there's a good documentary on the history of electricity called "Shock and Awe - The Story of Electricty".

It sometimes helps me understand better if I get some context on things, how people were thinking before it was discovered, what kinds of hyptothesis and experiments led to another and such.
This is very cool - it looks like you have a substance that looks and feels a bit like ceramic clay -- but when fired, it becomes true silica glass!
Column: UC notches a win in its quest to save scientific publishing
I'd like to see default linter settings that scan code for problematic words like 'master' that cause harm and silence black voices.
"Privacy Czar's warning: this product sells your data to third parties."
Yes. You calling other people for virtue signalling is a form of virtue signalling in itself.

Don’t you realize how ridiculous and useless this argument is?
Tqdm Multiprocessing
Needs V Wants.

I need shelter but it only costs so much to full-fill need. Then if I'm get paid sufficient salary to cover all my needs then wants decides the utility of the next marginal dollar. If the value doesn't align with my want then I don't care. As you get older you realize your time is finite and you want to enjoy what you do if you have the opportunity to make such a decision.

So if a job pays 20% more but requires more overtime or more stress then I'll pass.
I don't understand the military implications. The US has had long range missiles and defenses that are effective with stuff from the 80's and 90's. If China somehow got complete control over TSMC to the point they no longer supplied the US, it doesn't take much to sabotage the factories. If not missiles, then using spies, or attacking the systems that run the factories. This seems like a fragile advantage. Advanced chips don't even give you advantages in cyberwar.

Even if this triggered a longer conflict, the US could just buy through other countries that can buy from TSMC. Or just start using consumer off-the-shelf stuff. I'm fairly certain my gaming PC could guide a missile. There's lots of data centers in the US to pull from too.

If we lose all access to buying chips tomorrow, how does that affect our weapons?
We need to stop using android and iOS and move to pinephone and librem
Actually, there seems to be an exception that sounds relevant here:

> Developers offering products within another category of app downloaded on Google Play must use Google Play In-app Billing as the method of payment, except for the following cases:

> . Payment is solely for physical products

> . Payment is for digital content that may be consumed outside of the app itself (e.g. songs that can be played on other music players).
The reason why you can easily pursue those things now is because you optimized for money earlier.

It still is about salary. Except now you can self-actualize since you got the more base pleasures out of your system earlier.
==On the other hand, we need some way to prevent people from just installing their own platforms.==

Is this inherently true? Isn't it just another form of market competition?
I mean, fair enough, everyone has their personal opinions on style. But these battles can end up with the losing side leaving the company. This was a net loss on both sides: I lost income & a job I otherwise enjoyed while the team lost the key AWS expert that took months to originally fill.

Ironically, a team is probably more likely to lose competent people in such a scenario because they are the ones with many opportunities. A former manager of mine was more than happy to fast track my hiring to my current role.
I think that many artists serve as a counterexample to this sentiment. Many of them, even ones who eventually become famous, pursue activities without a care of who pays attention and without an end goal. They simply explore and seek out expression, where it almost seems to coming pouring out of them by necessity, obsession, or some combination thereof.

Some artists are so prolific, it can be mind boggling. Artists are not given enough credit for their work ethic.

There are plenty of artists who would make something, e.g., a movie , even knowing someone wouldn't see it.