HN user

francesca

1,493 karma

doritos

Posts124
Comments74
View on HN
monimiller.com 2y ago

Can I call myself a data engineer if I don't know Python?

francesca
3pts0
www.inngest.com 2y ago

Queues Aren't the Right Abstraction

francesca
25pts17
www.osohq.com 2y ago

Google Zanzibar for the Rest of Us

francesca
3pts0
www.osohq.com 2y ago

Build a comprehensive testing pipeline for authorization code

francesca
1pts0
www.osohq.com 2y ago

Is Polar Turing Complete?

francesca
3pts0
www.osohq.com 2y ago

We Turn Authorization Logic into SQL

francesca
2pts0
www.osohq.com 2y ago

Managing Authorization Data in Microservices

francesca
2pts0
www.osohq.com 2y ago

We Built a VS Code Extension with Rust, WebAssembly, and TypeScript

francesca
1pts0
www.osohq.com 2y ago

Implementing Attribute-Based Access Control (ABAC) in Node.js

francesca
2pts0
databaseengineering.substack.com 2y ago

Why database changes are hard

francesca
4pts0
www.osohq.com 2y ago

But Why Authorization Models?

francesca
4pts0
ui.osohq.com 2y ago

Show HN: The Oso Modeler

francesca
2pts0
www.osohq.com 2y ago

The Venn Diagram of Application and Authorization Data

francesca
2pts0
perform.beehiiv.com 2y ago

The Science of Slumps

francesca
1pts0
www.inngest.com 3y ago

Inngest raises $3M seed to build the reliable workflow platform for every dev

francesca
54pts35
www.osohq.com 3y ago

Authorization logic: why it's hard

francesca
3pts0
jlythcotthaims.substack.com 3y ago

How Did You Feel About the People Lost at Sea?

francesca
2pts0
www.osohq.com 3y ago

Authorization for the Next Billion Developers

francesca
3pts0
snyk.io 5y ago

Demystifying HTTP Request Smuggling

francesca
3pts0
engineering.mongodb.com 8y ago

Farewell, Solaris

francesca
113pts53
engineering.mongodb.com 8y ago

A MongoDB Engineering Response to the Anti-Diversity-Effort Manifesto

francesca
4pts0
medium.com 8y ago

MongoDB Performance Issues – Fact or Fiction

francesca
17pts2
www.bloomberg.com 8y ago

First Facebook TV Episodes Are Said to Be Ready for Mid-August

francesca
1pts0
primitive.io 9y ago

Primitive: Code in Virtual Reality

francesca
1pts0
www.mongodb.com 9y ago

Integrating Twilio, and AWS SES with AWS Step Functions

francesca
2pts0
www.mongodb.com 9y ago

Live Migrations, Queryable Backups and More AWS Regions in MongoDB Atlas

francesca
39pts13
www.mongodb.com 9y ago

Twilio and AWS SES with AWS Step Functions

francesca
3pts0
www.mongodb.com 9y ago

Maximizing MongoDB Performance on AWS Sign Up for MongoDB Atlas

francesca
1pts0
www.mongodb.com 10y ago

Announcing MongoDB 3.2

francesca
4pts1
www.cockroachlabs.com 11y ago

Hello World

francesca
332pts98
Merlin Bird ID 1 year ago

I love this app. I let it run in the background when I walk my dogs at home and when I'm traveling and it is amazing how well it connects me with the world around me.

Hi all! one of the makers of Oso Golf here :)

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!

Oso | https://www.osohq.com

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/

The connection of psychedelics to capital efficiency and growth is wild to me - I do love Matt Levine's newsletter and I feel that part of this commentary was satirical in order to make a point.

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).

Thanks for posting this. I always wondered why Jessica wasn't a bigger part of the YC story that so many people told.

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.

The biggest flaw in the piece is "This means that Elasticsearch and Kibana will no longer be open source software."

The SSPL is an open source license. It's just not the license that can help Amazon make money.

For someone who is "into the humanities" you ignore the fact that the Frankfurt school were some of the first who were actively rejecting this posturing towards reason. The "Dialectic of Enlightenment" is a treatise on the problems of rationality. It was written pre-WW2, as Hitler came to power. And it was quite correct in that this obsession with brunt progress was a fire that caused the Third Reich to rise up. It's very similar to what's happening right now, so please don't muddy up this discussion by saying that it's all witchcraft because it makes you sound like you are just spewing Ben Shapiro.

I'd offer to go out to coffee or lunch with this person, open up and ask if you could be of help. Just opening the door might be helpful. If the person isn't doing well, they are most likely getting feedback from their manager, or feel it in some way. If you open up and show you care, you set yourself up as someone who matters to this person, and then you set yourself up for giving candid feedback. I recommend reading everything by Kim Scott on this. It has helped me https://www.radicalcandor.com/

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.

MongoDB | Developer Advocate | Palo Alto | ONSITE, Full Time

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

_This code is written in optimized C++ and is very fast._

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.

WeWork did a great job of capitalizing on the move to smaller more agile companies. I don't think that "startup hype" is going to die. It's cheaper than ever to start a company and the market for tech companies is excellent right now. It's not easy to do, but getting $1-3MM in funding is accessible to talented people and once they get that in the bank, they're not going to open an office-- they're going to WeWork. This is huge for their business and it also enables the creation and maintenance of small companies who want to do things lean until the build a market and revenue stream (or maybe in some cases, adoption to drive further venture investment).

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.

I think the reason why it sucks is because engineers don't write job specs -- recruiters do. And a lot of recruiters don't take the time to really learn about how and why engineers move from company to company. Often they don't attract the highest quality talent because they attract talent that is "just right" and they don't try harder to make their recruiting better.

While I do think this move is a valiant one, I don't believe that it will, in and of itself, build better practices and help Microsoft build better software. Open source is very hard to do right, and if you're a company that doesn't have open source in their DNA it could pose a huge challenge to building positive relationships with your developer community. If you're a big corporation like Microsoft, you have tons of people with their eyes on you at all times. Everyone can read and criticize your code.

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.

Question for the OP

"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