Great idea!
https://michaelbensoussan.com - personal website
https://touslesmemes.fr - FR politician quizz game (who said what?)
1,896 karma · joined September 28, 2009
I'm the VP of engineering in a mobility company operating in Europe and in the US. email: mickey at hey
If you pass by Paris and want to have a drink shoot me an email.
https://michaelbensoussan.com - personal website
https://touslesmemes.fr - FR politician quizz game (who said what?)
I've looked at Turso before and this is exactly what came to mind. I do see some use cases where it could work, but for most real-world applications, this is an absolute red flag that shouldn't be overlooked.
You can check our offers https://fr.getaround.com/careers.
Otherwise, my experience is that if you specify it during the 1st call or in your application there's a good chance it's accepted.
It's not about how much you work.
I've been working hard at times, I still do from time to time but I never impose it to anyone. And when I'm in one of these periods when I push myself I do extra care of not showing it; not pushing code out of normal hours, not sending slack or emails,...
Because even showing you're doing it is already a step in the bad direction, it normalizes it, and ultimately create this hustle culture.
About Getaround Europe:
We are on mission to remove car ownership in European dense cities. We believe cars should be shared.
* We're a ~50 people P&E Team
* We have tons of challenges; pricing recommendations, ranking, connected cars that needs to be ultra reliable (it needs to replace your owned car), we provide APIs to different typologies of partners,...
* Our technology stack includes: Ruby On Rails, React, dbt, MySQL, Redis, Python, Snowflake, Heroku, AWS ECS
* We have a big monolith with small dedicated services for specific class of problems
* We write about our culture and the way we write software at https://getaround.tech
Please apply at https://uk.getaround.com/jobs
We use Google for oauth, map and geolocation APIs for which we pay thousands of dollars every month and all my interactions with them have been very painful.
I remember when we asked for a meeting to discuss price raise on Google Maps APIs; The raise was ~100x for us. They came with the head of the local market and 4 people. Basically told us to fuck ourselves and that from now on we'd have to be billed by a reseller instead of being billed by Google. And then they spent an hour trying to convince us to move from AWS to GCP. I had the impression I was at a car dealership.
This is just an example out of many so even if I don't have direct experience with GCP I'm not keen to try.
I've been managing the AWS company account and the collaboration with AWS for the past 7 years. And while not everything is perfect, my experience was great overall and I would do it again.
Datadog is too expensive because of the number of hosts we have. So we're thinking of eventually going to a hosted InfluxDB setup.
But we also want to revisit other hosted solutions. Does someone have some experience with using Cloudwatch + Grafana? I've used Cloudwatch many years ago and it was clearly subpar to something like Influx. Is is better nowadays?
But it has a big learning curve and setup & maintenance are very costly. I don't understand why most orgs are moving to k8 considering this. When talking to my peers I often see numbers like 6 months to 2 years full migration with a very small added value - at least for 90%+ of the companies using it.
It usually boils down to attracting talents and keeping them excited trying the new shit.
Everyhting goes through S3 because Snowflake storage is on it.
dbt is amazing, we began using it a month ago and it already transformed the way our data team work. It really is a value multiplier for everyone. Data engineers are happier because they don't need to write and maintain data transformations, analysts are happier because they can maintain their own SQL pipelines & the whole company is happier because we now have a great documentation tool to explore our data.
We also are big fans of Snowflake, make operating a data warehouse a breeze.
Then, we use a mix of Redash & Tableau for reporting.
Redash for static reporting (open to the whole company) & Tableau to create more complex data tools we expose to some internal teams; Marketing, Risk, Finance ...
I'm not affiliated - not even using their product.
We believe shared cars are a better way to move around, offering more flexibility and more convenience.
We are already the #1 car rental marketplace in Europe, and we believe the adoption will be 100 times larger in just a few years.
We are present in several countries, have great mobile apps, and kickass hardware. And we're just getting started.
Take a look at our engineering blog - https://drivy.engineering
Please apply via the above link and mention Hacker News!
I think the whole point was to help generate a few very long json files (http://docs.grafana.org/reference/dashboard/#dashboard-json) but in the end I had way more fun with this new concept!
We are already the #1 car rental marketplace in Europe, and we believe the adoption will be 100 times larger in just a few years.
We are present in several countries, have great mobile apps, and kickass hardware. And we're just getting started.
We're looking for Backend, Full-Stack, Reliability and iOS engineers.
Take a look at our engineering blog - https://drivy.engineering https://en.drivy.com/jobs
Please apply via the above link and mention Hacker News!
Ping me if you want to know more.
We believe shared cars are a better way to move around, offering more flexibility and more convenience.
We are already the #1 car rental marketplace in Europe, and we believe the adoption will be 100 times larger in just a few years.
We are present in several countries, have great mobile apps, and kickass hardware. And we're just getting started.
We're looking for Backend, Full-Stack and iOS engineers.
Take a look at our engineering blog - https://drivy.engineering https://en.drivy.com/jobs
Please apply via the above link and mention Hacker News!
> I like you enforce the commit/ticket relationship. Is this purely an agreed process or do you use other measures to keep things consistent? E.g. we typically add the ticket ref to each commit but at times that gets omitted.
We're not enforcing it but we might in the future if the team grows and this gets out of hands. At the moment we're just reminding people that they should and it works great so far.
> Would you mind expanding a bit on the things you enforce for each of your releases?
It's still early but so far we check:
- it's not friday afternoon, we want to avoid as much as possible to have issues on the weekend
- it's not out of office hour - we're still all on the same time zone
- there's no lock (we can lock the release in case something goes wrong)
- there's no schema migration. If there is we remind you how to safely migrate schema and who to ping if you have a doubt (usually it should have been caught at the PR review)
- there's someone from the ops/core team around (connected on slack)
- that there's no translations missing for our main languages (french/english)
- + we do a few sanity checks like that our master staging is healthy (release means promoting our master staging)
edit: also I forgot but this is the shipit I'm talking about https://github.com/Shopify/shipit-engine
Completely agree, that's why we instrument our releases so we can easily see what's deployed by service and environment.
> Then there is the issue of linking the Git release/tag with the corresponding changes, say from a ticketing system such as Jira. That can be helpful to communicate changes to other people within the organization and to users.
Each commit is related to a ticket, helps generate a changelog. We enforce a lot of things in each of our release. We have an internal release tool heavily inspired by shipit from Shopify. We have the concept of soft/hard checker to make sure it won't break or that you aware of what could break with the current diff.
> How do you define dependencies for releasing new versions to service? Likely going to happen at some point when you have non-trivial changes to services.
As I said we instrument our releases and can easily track how changes affects our performance/bugs.
We also try a lot not to release non-trivial changes in one big release by doing stuff like release part of the changes behind a feature flipper first or route only a part of the traffic to the new code path, ...
Then we don't have dozens of different services deployed and we're still a relatively small team (~20) so I'm pretty sure I don't have the full picture just yet :)
A Slack notification could do it. Or do you want to correlate deployments with other metrics?
In this case we instrument our deployments into our monitoring stack (influxdb/grafana) and use this as annotations for the rest of our monitoring.
We can also graph the number of releases per project on different aggregates.
We believe shared cars are a better way to move around, offering more flexibility and more convenience.
We are already the #1 car rental marketplace in Europe, and we believe the adoption will be 100 times larger in just a few years.
We are present in several countries, have great mobile apps, and kickass hardware. And we're just getting started.
We're looking for Backend, Full-Stack and Data engineers.
Take a look at our engineering blog - https://drivy.engineering https://en.drivy.com/jobs
Please apply via the above link and mention Hacker News!
We believe shared cars are a better way to move around, offering more flexibility and more convenience.
We are already the #1 car rental marketplace in Europe, and we believe the adoption will be 100 times larger in just a few years.
We are present in several countries, have great mobile apps, and kickass hardware. And we're just getting started.
We're looking for Backend, Full-Stack and Data engineers.
Take a look at our engineering blog - https://drivy.engineering https://en.drivy.com/jobs
Please apply via the above link and mention Hacker News!
We believe shared cars are a better way to move around, offering more flexibility and more convenience.
We are already the #1 car rental marketplace in Europe, and we believe the adoption will be 100 times larger in just a few years.
We are present in several countries, have great mobile apps, and kickass hardware. And we're just getting started.
We're looking for Backend and Full-Stack developers.
Take a look at our engineering blog - https://drivy.engineering https://en.drivy.com/jobs
Please apply via the above link and mention Hacker News!
We believe shared cars are a better way to move around, offering more flexibility and more convenience.
We are already the #1 car rental marketplace in Europe, and we believe the adoption will be 100 times larger in just a few years.
We are present in several countries, have great mobile apps, and kickass hardware. And we're just getting started.
We're looking for Backend and Full-Stack developers.
Take a look at our engineering blog - https://drivy.engineering
Please apply via the above link and mention Hacker News!
Even with Poltergeist I used to debug a slow test suite with it's `--proxy-server` option.
You can fire up mitmproxy and see the requests flowing in real time. You can even modify them or replay them.
Also we're only considering onsite candidates for junior positions.
We believe shared cars are a better way to move around, offering more flexibility and more convenience. We are already the #1 car rental marketplace in Europe, and we believe the adoption will be 100 times larger in just a few years.
We are present in several countries, have great mobile apps, and kick-ass hardware. And we're just getting started.
We're looking for Backend, Full-Stack and Data/Ops Engineers.
Take a look at our engineering blog - https://drivy.engineering
Please apply via the above link and mention Hacker News!
We believe shared cars are a better way to move around, offering more flexibility and more convenience. We are already the #1 car rental marketplace in Europe, and we believe the adoption will be 100 times larger in just a few years. We are present in several countries, have great mobile apps, and kick-ass hardware. And we're just getting started.
We're looking for someone who is not only well versed in Android development, but also has a strong understanding of good UX. Link to the job offer - https://www.drivy.com/jobs/57caa312-85cc-4ab2-b0ba-0402affc5...
We're also looking for Backend and Full-Stack developers.
Engineering Blog - https://drivy.engineering
Please apply via the above link and mention Hacker News!
I would say this used to be true in 5.5 and before but it's less and less of an argument. 5.6 and 5.7 bring a lot of features like JSON or geospatial. Here's a list of the new feature of 5.7: