1,493 karma · joined December 11, 2011
Authorization is a challenge for everyone, but has been solved by no one. As the people who wake up thinking about authorization each day we created Oso Golf, a game to help educate the developers about authorization.
We built the first iteration for this game for GraphQL summit, as a fun way for developers to learn Oso’s policy language. Attendees got really into the game, hanging out at our booth for upwards of 30 minutes to solve this with their friends.
So we got some feedback on the game and built it out into 9 “holes,” just like a Golf course, each hole teaches you a different principle of authorization modeling. We’re opening this up to the community today and are excited to see what you think!
[1] https://www.nyc.gov/site/cchr/media/pay-transparency.page
Oso is building authorization for the next billion developers. We are building the product in Rust, which we think is both a good design choice for our use case and a fun choice for the team. I recently joined the team and absolutely love the culture and I'm inspired by the talented engineers I get to work with :) Current open roles:
- Engineering Manager (NYC) - Software Engineer (NYC or Remote) - Developer Experience Engineer (NYC or Remote) - Head of Engineering (NYC)
All open roles - https://www.osohq.com/company/jobs A bit more about Authorization: https://www.osohq.com/academy Our Slack community: http://join-slack.osohq.com/
I feel like Silicon Valley's psychedelic era is like a strain "tech bro" wellness culture (often referred to as "biohacking"). And just like wellness culture it's really hard to distinguish something that is helpful in small doses vs. something that becomes a gratuitous lifestyle (like drinking charcoal or putting jade eggs somewhere you shouldn't).
This line stood out to me in particular: _It's not just because she's shy that she hates attention, but because it throws off the Social Radar. She can't be herself. You can't watch people when everyone is watching you._
No matter what you get acknowledged for I think it's so important to always be yourself but to know what makes you strong is so challenging.
Elasticsearch is open source. the SSPL is open source. It just can't help Amazon make money.
The SSPL is an open source license. It's just not the license that can help Amazon make money.
If this person's poor work is impacting yours, tell your manager. If this person's poor work is impacting your team, address it with their manager. If they come to you for advice on their performance, then give them feedback.
I am the hiring manager for this role Seeking Developer Advocate to help support the MongoDB community. You have written software and know first hand how powerful it can be to solve human problems. You love Open Source technology and community building. You enjoy creating compelling presentations and blog posts to educate your peers. Celebrating human accomplishment is something you do naturally and you get energy from creating relationships.
Language/Stack agnostic, but helpful if you have expertise in one or more of the following: Node.js, Go, Python, AWS, Azure, Google Cloud, Kubernetes, Docker.
Interview process: Technical interview, on-site interview w/ stakeholders, coding/writing challenge.
to apply: https://www.mongodb.com/careers/job/583167 or francesca [at] mongodb [dot] com
Can you elaborate?
_but we're shooting for performance levels where you (as a user) might not even be able to measure the difference._
Benchmarks are almost always skewed towards the preferred workload of the DB (they're like science experiments, the result is heavily biased). How are you ensuring this isn't the case with your benchmarks?
Also what are you benchmarking against? I'd like to see one against Aerospike.
I've seen WeWork do great things for companies in NYC by just giving them a place to work and a community to work with.
Still, WeWork is not just another. They are actually a next-generation Real-Estate company! WeWork makes it clear that working is not just about your desk. It's also about your environment, the other people you interact with, the events that come to your space, the coffee you have (and in the case of WeWork, the architecture and design of your floor!). This is very cool for the future of company/working culture.
Also, being open source means being open and transparent about release cycles and roadmaps, which takes a lot of effort and initiative. I do think Microsoft can do that if they build a solid team of technical community evangelists, but otherwise, they will be swimming against the stream.
"we’re not exactly running a standard MongoDB instance here. Our dev team is very familiar with Mongo, we’ve squeezed quite a bit of performance improvements out of it over the years" --> Curious to know what was done to see those performance improvements. Thanks for the information