skysight-inc/HackerNews huggingface dataset:
> You're shifting the responsibility from yourself to a different entity for the choices you're making. The single safest thing you can do while using the web is to simply be aware of what you're clicking on, and what sites you visit.

This seems like a fundamental misrepresentation of how malware is distributed, and how privacy is compromised. People are responsible for the sites they choose to visit. They're not responsible for what those sites serve them, because they can't evaluate it until it's already been served. I don't know what a page will serve me until I visit that page. I can't.

Holding people responsible for whatever content they're served on a page is the same sort of "suck it and see" logic we rightly rejected with "by opening this package, you have consented to the terms of this license". It's a concept that's fundamentally incompatible with informed agreement.

If you want to hold people responsible for clicking "crack DRM now!" ads on the Pirate Bay, fine. But malware doesn't necessarily require outbound clicks, and doesn't necessarily come from dubious sites. Forbes locked out adblockers and served malware through their ad network. Xfinity, the NYT, ebay, Youtube, the Atlantic, and a dozen others major sites have served malware. Newegg, British Airways, and probably Ticketmaster were hit by Magecart, which infected even users with adblockers running.

Why do I disable Javascript? It's not because I don't think I'm responsible for my safety online. Precisely the opposite - it's because I'm not relying on other parties! Magecart was running on major sites two months ago. Adblock, an up-to-date browser, and responsible surfing didn't keep people safe, but uBlock did. A framing where users are accepting any code that ever appears on any site they visit is a framing where we all ought to abandon the internet outright.
Please take a look at o_wilson's posting history, as I have found another link to a plagiarized article on Medium, and the situation doesn't pass the smell test.
How does that help when WiFi is also microwave?
1 watt corresponds to an in-use phone. Heavy data use. Even a call has much lower power. Unless the phone is actively doing something, the cell pings are very brief and use very little power.
I have done this, but it can be harder to manage. Watch you don't burn yourself out.

Mentoring someone inside your org, but outside your immediate team is often a better option because the motivations are clearer and the individual is getting inputs from you, their manager, their team, other individuals in the broader org.

When it's someone completely outside it can be much harder to understand the motivating factors, reinforce learning, ensure follow through etc. As a result, scoping the mentorship and building up a successful relationship is harder.

Example: You meet someone looking to build non-trivial sites with Django to make a career switch. If you discover they are deficient in Python, do you go down that rabbit hole, or stick to only Django? Unless you and they are really motivated things can break down quickly.

Inside an org you might have the option of supporting that person talking to their manager about taking a formal training course. Of course you can suggest similar to a random individual at a meetup, but the follow through often isn't going to the same extent.
There are a solid group of people who seek out jobs with no agile and no meetings. No source control is a bit out there, I don't want code reviews, but I do want to be able to rely on the source code for what's running on prod to be in the repo within some reasonable time (before it gets to prod is better, but after is ok too, as long as its consistent).

Edit to add:

> hiring developers because 1) Glassdoor reviews are bad 2) compensation is small 3) work is frustrating 4) you don't learn anything from colleagues

Of these, only one is important -- compensation; pay more and people will be willing to put up with a frustrating work environment. Especially if "no meetings" means no meetings. (unlike where i currently work where "no meetings wednesdays" means everybody has room on their schedule on wednesdays, which means that's where the meetings are scheduled)
Ledger | Senior Software Engineer, Software Engineer, Embedded Application Engineer | Paris, France | ONSITE

We build crypto-security solutions related to the blockchains with our unique technology: Blockchain Oriented Ledger OS (BOLOS). We provide this OS in 3 products:

- Cold storage Hardware Wallet solution for BtoC: Ledger Nano S (https://www.ledger.com/products/ledger-nano-s)

- Software and Hardware enterprise-grade Wallet: Ledger Vault (https://www.ledger.com/pages/ledger-vault)

- IoT security in a blockchain: We have a partnership with Engie (energy company) to log green energy production in a blockchain to ensure its tracability (https://www.ledger.fr/2018/10/10/engie-and-ledger-partner-to...)

We have 3 open positions:

- Senior Software Engineer, Scala, with some experience in Cassandra or ScyllaDB (https://ledger.welcomekit.co/jobs/senior-software-engineer_p...)

- Software Engineer, Scala and/or Python (https://ledger.welcomekit.co/jobs/vault-software-engineer_pa...)

- Embedded Application Engineer, IoT (https://ledger.welcomekit.co/jobs/embedded-application-engin...)

Backend Stack: Scala (Finatra, CatsIO, fs2.Stream) and Python 3 (Flask), ScyllaDB.
Infra: AWS, Ansible

Competitive salary and benefits, stock options, location in central Paris (75002)

You don’t need to speak French to join us, we all speak English. We offer French classes to non French speakers.

Email me at jean dot champemont at ledger dot fr with your resume and mention HN.
I don't think it should be a mystery to management why employees hate working at their company.

Maybe you can help them figure it out by explaining that working at company X is miserable and enumerating the reasons why, in specific and actionable detail. Then the HR person who conducted the interview can duly note your thoughts down and file them away, never to be seen again, as the gravy train keeps rolling, but you will have honestly done your best.

Congrats on your escape, and best of luck at your new job. Employment is a business relationship; don't feel like you owe company X anything.
>>I don't think this is true at all.

It's not true that anonymity increases the difficulty of enforcing certain classes of laws?

I never said enforcement becomes impossible or that the risk for those contravening the laws goes to 0%.

>>Besides: coordinating activities requires identity. Either you have true anonymity, in which case trust is nigh impossible even with smart contracts

With cryptography and immutable and persistent programs you can have trusted agreements without trusted parties.

>>or you have pseudonymity with stable identities to allow reputations to form, meaning that once the identity is pierced all of that person's actions are traceable.

It's possible that the pseudonym doesn't get linked to any real world identity, but yes pseudonymity is a much less effective defense against a tracker than anonymity.
Why do you feel that way? Economically, you provide expertise and time and in return they provide you a salary. What feelings are causing you to continue to think that you owe them something?
link: http://www.3blue1brown.com/essence-of-linear-algebra-page/
> Those people couldn't get work

Wasn't it revealed that most on the list continued to work in Hollywood under pseudonyms?

I mean, certainly denying work was the intent of the list, but...
> then you need to take the integrity of that data set very seriously or be at serious risk of credential replay attacks.

This is no more true in my technique than in session tokens. You have to invalidate session tokens carefully, most simply using serializable database transactions. You can do the same with the blacklist.

People also put session tokens in memory, and your concern about caching and consistency applies equally in that context. The blacklist is in some ways easier to manage because it is not sensitive like a session token. It's more difficult in other ways, but IMO harder to get wrong.
The post states:

>"When your username and password are entered on Google’s sign-in page, we’ll run a risk assessment and only allow the sign-in if nothing looks suspicious. We’re always working to improve this analysis, and we’ll now require that JavaScript is enabled on the Google sign-in page, without which we can’t run this assessment."

Is the idea that an actual browser will be able to have a fingerprint whereas a bot would not? Is the check for a javascript a way to short-circuit responding to a non-browser based request? It wasn't clear to me.
This is incredibly fatalistic.

Why can't technology be created with human nature in mind? Forms of democracy with checks and balances became so dominant because it acknowledged the deficiencies in human nature.

We can certainly blame companies for producing bad/harmful technology just like we can blame forms of government for producing bad outcomes for its citizens.

---

On a side note, based on influence and entrenchment, comparing FAANG companies to governments actually seems more appropriate that I initially thought.
> There's no place for 'sexual harassment' culture, period.

First of all, they appear to be firing / asking people to leave in the standard corporate way. Yes, it's common to pay people to leave to avoid a lawsuit. Might not be pretty, but it's the reality we live in. I agree that should probably change, but walking out is not really impacting the company at all.

Which brings me to the point, leaving does impact the company. If massive numbers of engineers quit, that'd actually cause way more pain than taking a walk around the building.

Finally:

> If your employer started murdering people in the streets outside your office, would you just pack up and find a new job?

Not even close to the same level, but yes I'd leave. I'd also probably report them to the police. Why the hell would I stay there?
I've worked in organizations that promoted engineers into management, rather than bringing in outside managers or managers without engineering backgrounds. For highly engineering-driven orgs this can make a lot of sense, and depending on how it's done and the people involved, it can produce great results.

However: when those managers hold on to their engineering responsibilities, their teams suffer for it. There's a negative stereotype among engineers that managers don't do anything anyway, so maybe the team just needs a designated engineer to play manager in order to go to meetings, approve days off, etc.- the bookkeeping parts of management, but not the managing parts of management. There's a perception that the other engineers on the team are super self sufficient, what do they need a manager for anyway?

Often these managers would be allowed to continue doing engineering as a motivator- they didn't really want to be managers in the first place, let's just let them keep doing their thing and throw some more money at them and everybody will be happy. But it really feels like an antipattern.

Working on different teams where managers didn't do any coding was a breath of fresh air. I didn't know what I was missing. Managers can do the most good by focusing on things that allow their engineers to be as focused on their work as possible, and as unblocked and undistracted as possible. It makes a huge difference. It doesn't matter how incredibly self-sufficient an engineer is...if they get stuck doing a bunch of extra non-engineering stuff because their manager doesn't manage, their work and happiness will suffer for it.

So, at least based on my own experiences, I've come to see teams where the manager still has engineering responsibilities on their own team as a red flag. Anecdotal and highly contextual to where I've worked, but that's been my experience.
This seems like exactly what I as an app developer do NOT want. Basically this is my app that may break every 2 to 6 weeks as the Chrome team changes stuff outside my control. With Electron I ship on a version of Chromium I know my code runs on. With Cario today it works, tomorrow they deprecate an API, push an update to Chrome and my app breaks. I'd prefer to get a new version of Electron behind the scenes so I can fix any things that come up and then later push a new version.
>I'd like to know how you envision this happening

Botnets of fake social media accounts for starters. You think if they are currently manipulating political elections they won't ever try and use similar tactics to tank a company?

China: "Google give us user data!"

Google: "No way!"

China: "PLA Unit 61398, hurt the Google! Make accusations! Lots of accusations! Many many many accusations!"

----

China: "State media, run articles about how the evil uncivilized Google makes a hostile environment for female/gay/green cardigan wearing employees!"

---

China: "Movie studios, make this romantic comedy but be sure to vilify a company identical to Google!"

---

China: "People's Worker, scour the internet for any controversial quote from any corporate member of Google, great, yes, that! PLA Unit 61398, have an account 'discover' this quote and use the botnet to get it trending!"
> Instagram isn't really a competitor with Facebook

Of course it is. Facebook is losing certain demographics to Instagram. If they were separate companies, Facebook would be under far greater shareholder pressure.
You do a chromosomal analysis on everyone before you use a gendered pronoun to describe them? Because you can't tell what their chromosomes are just by appearance.
No, the poster said: "unless you're a C++ hacker you can't actually work with most of it." That strongly implies COM. The Windows APIs are C.
They were created to be uncensored versions of existing websites. (I don't think there're any examples of Gab limiting left views.)

It happened that the existing websites were censoring far-right viewpoints.

So...by default the predominant users were far right.
CGI was used in Spirited Away (afaik), but in very limited quantities. You pretty much can tell the scenes when you see them.

Miyazaki retired like a dozen times, nobody believes him anymore. The last one was the last year or 2016, iirc.
I liked these translations[1], I see there have been a couple of recent others, but I haven't read them yet.

1: https://www.goodreads.com/book/show/552708.The_Book_and_the_...
Exactly why I quit managing altogether. One can code or one can manage, but doing both means both are compromised.
Location: Brazil
Remote: Yes, remote only
Willing to relocate: No
Technologies: mostly Python, but always hacking with other things
Résumé/CV: https://www.linkedin.com/in/iurisilvio/
Email: iurisilvio@gmail.com

Worked as CTO for one company from the begining and it was acquired by a big local retailer. Now doing consulting for local companies.
I'm not sure if you have a very strange friend group, but I've never heard someone express a similar opinion.
Steven Pinker talks about this in his book Better Angels of our Nature. Ending the habit of personal eating knives was part of the "civilizing process" that drastically reduced the murder rate in Europe, because people stopped walking around armed quite so much.
Even Android was bought, when you think about it.
skip the advice. "replace upper management with professional" is unlikely to happen.
This isn't something to worry about unless you're using your phone for 9h a day and have boosted the power output beyond the legal limit. Even then there isn't an explanation as to how it would cause cancer.
"We don't let managers code where I work."

"...ended up with managers who slowly lost their technical skills and essentially fossilized, and couldn't make rational tech decisions"

There's a connection here. A technical manager can't make reasonable tech decisions unless they do some tech work, but perhaps we just need to be more clear that what you want is a pure project manager to check off boxes.

I think a good tech manager still respects a bottom up approach most of the time, but should have enough experience to push back when the group is steering in the wrong direction. A generic project manager isn't going to do that.
> JWTs are a silver bullet, but it's nicer than rolling your own signing scheme.

you can use HMAC to sign session cookies as well, the issue isn't about signing.
Agreed. The "secrecy" thing is just hyperbole from New Scientist. What LIGO are doing with their data is completely standard practice in the community.
Rather than trying to change company policies about harassment, why aren't they trying to change the law?

A company shouldn't be the one to decide if harassment is or is not okay.
If Apple is getting this kind of performance out of their CPU/GPUs, especially the "Xbox One X level performance" they mentioned about their iPad Pro, curious if they'll turn Apple TV into a gaming console.
As others have said, don’t give advice - they don’t care. If they cared they would have taken steps to address things by now. Just keep it cordial but tight lipped.
We've killed it.
I think people should be able to swing back and forth; manager for a year or two, engineer for a year or two. I don't believe everyone can be happy with a prescriptive path to follow -- I can't only be one or the other for the rest of my life. I like leading, mentoring, and developing teams. I also have strong inclinations towards inventing solutions and developing the future generation of technology.

I think businesses need to be able to adapt people to different roles and be comfortable moving people around and let them change over time. Otherwise we'll have people hopping off to new companies every few years as we tend to and taking all of their domain knowledge with them.
They can't get close enough to you to matter. The way to think of this is to imagine a bubble around each person's phone. Just like a bubble gum bubble, the bigger it gets, the thinner it gets. So if its dark pink when it is emerging from your lips, it is transparent by the time it is 6" in diameter.

The energy of the cell phone transmitter is spread out further and further as you move way, and because the 'bubble' is both taller and wider, each meter (about 3') you step away from the phone, the signal is 1/distance^2 less powerful. So 2 meters away, 1/4 as powerful, three meters, 1/9th etc.

I like the Tokyo subway image, and others have gone to the trouble of computing people densities[1], if you take their number of 7 people per square meter as a good maximum, then 100 people divide into 7 person groups and you get a box that is about 4 meters on a side (12' x 12'). You're only getting 10% of the energy from the phones that are 3 meters away.

[1] http://www.elsi.jp/en/blog/2015/11/blog1126.html
It was also used in limited form in Princess Mononoke.
comma.ai | engineers | San Francisco | onsite | full-time

OPEN SOURCE SELF DRIVING CAR https://github.com/commaai/openpilot

Our stack is largely Python, with some C/C++ and JS(React). Primarily looking for a firmware engineer and a lead openpilot engineer with a physics or math background.

Reach out with a GitHub or LinkedIn to givemeajob@comma.ai
Gratis versus Libre: Free as in Books
TakeShape, a headless GraphQL CMS | Developer Advocate, Software Engineering, DevOps, Product Management, UX Design, Customer Success | REMOTE OK

Serverless Lambda Stack on the backend. React on the front.

https://www.takeshape.io/careers/
Facebook is responsible for most of the world's social networking, so as a consumer, I'd rather not dictate how it wants to run its shop.
It's always been my daydream to work with a company like this and serve my country.

At my current job I joined because it directly helps people as well by helping them shed off debt they cannot handle. We all do what we can to help others. Kudos to you!
Totally agree on the QA side, you need to see first hand what’s coming out of your team to understand where your team is at.
feel free to delete any comments you dont like
Moovweb - https://hire.withgoogle.com/public/jobs/moovwebcom

Engineering is the lifeblood of a great tech company. That is why we hire the best engineers, no matter where they live. We believe small teams work best and fastest, allowing individual engineers to have the biggest impact possible. We hire engineers who learn fast, have great technical judgement, a bias toward shipping and passion for software. We value these characteristics above expertise in a given domain or with a specific language.

We do most of our work in JavaScript (webpack/babel/ES6/ES7/React), NodeJS and Go. We are also heavy users of AWS Kinesis/EMR, ElasticSearch, c3/d3.js, Vagrant, Travis CI, Puppet, Ruby/Rails and AWS.

Moovweb does big things. We autoscale thousands of servers and serve billions of pages per month. We push the limits of what can be done with the front-end of the web. We created a full customer-facing analytics platform on AWS and two Sass libraries: Libsass, the most popular engine for the Sass CSS pre-processor, and gvm, which is rvm for Go.
> which I believe are cancer-causing for anyone living in the immediate area due to the power they radiate.

I downvoted you because there is no evidence of this. You also state they wiull "use more power" but power output is regulated by the FCC.
Just because OSI wasn't formed as a legal entity until 1998 doesn't mean that the people involved weren't around and involved in those earlier discussions of "open source". All OSI did was formalize what was in common usage. And sure, you can cherry pick a few exceptions where individuals used the term in different ways. That has little or nothing to do with contemporary usage.

And in today's vernacular (dating back to at least 2000 or so) the de-facto definition is the OSI definition. A few lone-wolf dissenters don't change that.
I can see the point of trials: as the article says, people told to lie will act very differently from people who want to lie, and a bunch of real-world data versus some lab data is surely going to improve it. I am not convinced that there is nothing about a person that gives away, at least in a good number of cases, whether someone is lying.

I'm just wondering if it's too much to hope that they'll base the decision whether to implement it beyond the trial on data and not on marketing.

And there is of course the argument that it should be possible, albeit with a lot of effort and/or a reasonable punishment, to break the law. (If this was impossible, we'd never get out of regimes we don't agree with, and with the advance of technology I'm afraid we're heading somewhere where a small group is actually able to oppress a huge number of people.)
Vi's site is down from the onslaught.

In the meantime, enjoy the ever-classic Fizz Buzz Enterprise Edition:

https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
First of all, your index's title is "Home | Antheon"; you are not providing enough information so the engines could push you up to their top index results.

Also, how can you expect an engine, a bot, a crawler, name it whatever you like, to find you with description "Antheon"? You need to describe your niche within 300 characters the most, no more.

Another problem I see with your website's code is that you are not providing a single H1 or H2, like at all; you provide only two H3 tags.

Engines like Googlebot looks for 1) a title, then 2) for a description and 3) for H1-H6, starting with H1 as its highest rule of header priority for validation.

There are many things you should validate as standard SEO practices.

Whoever did this, from desginer's point of view is good; simple, yet elegant and straight to the point.

But from a developer's point of view...I give it a 26 to 38 out of 100.
There are artificial ways to stop ocean acidification as well ... but yes, we'll have to manage a lot of things.