On the whole this essay seems to be making a deliberately slippery argument. It wants to redefine "bureaucracy" to suit its purposes while also maintaining all existing pejorative connotations of the term.
Maybe in other places on the internet, sure, but I was referring mostly to the code-of-conduct-gated development communities that pretend not to discuss politics while allowing specific viewpoints above others.
I can see a difference between light-hearted speculation about an imaginary crab's gender and saying that non-gender-binary people don't exist. Can you think of any reason why one of these might be allowed, while the other might not be?
I guess I can't, because they're both political statements. Politics is either allowed or not. I assume, however, you have some reason in mind, by how you phrased the question.
Interesting - well, honestly, not sure how anything wouldn't be political if discussing a crab is politics.
Not that that's necessarily wrong - I'm definitely sympathetic to the argument that the personal is political. But that argument would justify more technical communities taking political stances, not fewer.
Discussing a crab is not politics, but attributing to it a non-existent gender is intentionally contrary to most people's social beliefs (especially outside of the SV bubble) and is thus political. Calling it a normal boy or girl isn't.
If, however, some community members wish to do that, they open to others the option to speak their minds on the topic, including stating that such an action ought not to be taken because no such gender exists. Contrast this with how most "codes of conduct" are written: they would permit community members to speak in favor of such a decision but not against it, as doing so would be "hateful", "bigoted", or "exclusionary".
My first reaction was: why is a non-gender-binary crab mascot considered "political"? I'm assuming this came up incidentally in the context of its name and pronouns?
By this implied definition of political, more or less any human social interaction is political in the broader view.
It’s one example out of many where rust users bring a political topic (and yes, post-gender queer theory stuff is political) into a discussion where there’s no reason to do so except to leverage the discussion as a platform for boosting your political belief. It’s very unprofessional, very counterproductive, and a huge turn off for people who don’t have the same fringe politics.
You're right that it's primarily a social issue, but people will always try to use the state to enforce their social beliefs, so they become political. See New York City's ordinance that can cause those who won't use a made-up "pronoun" to be fined [0], undoubtedly a use of force by the state to enforce a certain set of beliefs.
I've been using this for a small project and the feature set is far more comprehensive than anything else I've seen in Rust. In comparison to Juniper, it has much better support for subscriptions in particular. Its creator has been amazingly productive and continues to add features almost daily.
Came here to ask how it compares to juniper. Juniper has been the one part of my stack of crates that's made async difficult for a while now. Building a rust app with full futures support from top to bottom has huge benefits, but support on juniper has been slow in coming (a lot of existing code to move along with it), and the main error being GraphQLError<'a> with a lifetime and no impl of std::error::Error has been a huge nuisance to deal with.
That said, constructing the resolvers with the `#[juniper::graphql_object` macro has been incredibly easy. They used to use some clunky DSL, but since the move it's been great. Don't think I'd consider moving if async-graphql isn't as strong on that, but I won't really know until I try both.
We are looking for an engineer to help deploy bleeding-edge cryptography. You will have the opportunity to develop new cryptographic products and see them move from academic papers to operational systems with hundreds of thousands of users. In particular, we are looking for people to help us build ECDSA-based products using multi-party computation and zero-knowledge proofs. This role comes with significant autonomy and responsibility.
We are a team of 35 people, 100% remote. Our tech stack is primarily Elixir (for backend), Rust (for cryptography), and Typescript, React, and GraphQL (for frontend and mobile). We value diversity and welcome talented people from all backgrounds.
Our company is remote first (no physical office, co-founders spread across the world), and one frequent point of feedback we get from new hires is that working for a company with a 100% remote culture is quite different than working remotely for a company with existing physical offices. When you are working from a distance with an otherwise co-located team, it is easy to miss out on important information, and interacting socially with coworkers (a challenge for any remote position) becomes even harder.
Btw, we are hiring. Stack is Elixir, Rust, Typescript, React, GraphQL, and we have many challenging/interesting problems! https://jobs.lever.co/nash.io
You’re describing a distributed organization, not remote. Distributed assumes no home base, no HQ, nothing. Everyone works from home or a co-working space.
SV is staunchly apposed to remote, I can’t even imagine their opinion on distributed.
I live in SV, and while I wouldn't say hiring remote employees is common, it is becoming much more so. Staunchly opposed doesn't sound correct given the other founders I interact with.
Our goal at Nash is to make trading, holding and interacting with cryptocurrencies safe and accessible to everyone.
We are looking for an engineer to help deploy bleeding-edge cryptography. You will have the opportunity to develop new cryptographic products and see them move from academic papers to operational systems with hundreds of thousands of users. In particular, we are looking for people to help us build ECDSA-based products using multi-party computation and zero-knowledge proofs. This role comes with significant autonomy and responsibility.
We are a team of 35 people, 100% remote. Our tech stack is primarily Elixir (for backend), Rust (for cryptography), and Typescript, React, and GraphQL (for frontend and mobile). We value diversity and welcome talented people from all backgrounds.
We are looking for talented people to help us build and secure infrastructure for the cloud-based components of our distributed, non-custodial exchange. If this sounds like your skillset, or even sounds like something you'd like to learn to do, we'd love to hear from you! We are a small team (about 30 people) and our main hiring goal, whatever the position, is to recruit more brilliant, humble people. We work primarily in Elixir and TypeScript for our core services.
A few notable things about the company:
* We employ people from more than 14 different countries. Everyone is remote, including the founders. Pluralities of the team are in the US and Europe.
* We are well capitalized and raised money from both traditional VCs and the public. We launched the first ever public sale of a regulated security token in Europe, NEX (Nash Exchange).
* While we are building a consumer focused non-custodial (often called "decentralized") exchange, we believe strongly in regulatory compliance and have acquired the necessary licenses to operate trading and payment services in the US and Europe.
* Some keywords for people scanning through: elixir, rust, cryptography, distributed system, kubernetes, blockchain, security token, bitcoin, ethereum
We are looking for talented people to help us build and secure infrastructure for the centralized/cloud-based components of our hybrid decentralized exchange. If this sounds like your skillset, or even sounds like something you'd like to learn to do, we'd love to hear from you! We are a small team (about 30 people) and our main hiring goal, whatever the position, is to recruit more brilliant, humble people. We work primarily in Elixir and TypeScript for our core services.
Hey Ethan! I saw this post and was wondering if production experience is required for the backend position. Elixir is the dream language for me to use professionally, but I've only used it outside of work (hackathons, etc). I do use Clojure and Haskell at work though.
