4 ms·
We do at my team. I do not work on the Backend side, but I help in designing the DB schema. Whenever I am thinking of new features to be developed, or when en
by andersonklando 1y ago
We do at my team.
I do not work on the Backend side, but I help in designing the DB schema.
Whenever I am thinking of new features to be developed, or when engineers are suggesting some features/approaches, looking at the ERD helps a ton. Onboarding is also easier.
We were using Lucidchart[1] until we reached the limit[2], so we found dbdiagram.io (which is just not the same).
[1] So far, it was the best of the market in terms of "canvas freedom"
[2] We are struggling with salaries, so we are saving everywhere
- reactordev 1y agohow many tables? is it manageable and interesting like trying to squeeze 2b records into postgres or what? Also lucidchart is just draw.io fyi - you don't need a license unless you need the file sharing aspect and I feel like it belongs closer to the code. I'm just generally curious what others' process is for this as the only meetings I've had in the last 5 years were who was getting cut.
- deleted 1y ago[deleted]
- andersonklando 1y agoIf I recall, Lucidchart allows up to 15 "shapes. > Also, Lucidchart is just draw.io fyi - you don't need a license unless you need the file sharing aspect, and I feel like it belongs closer to the code. No, it is not. I took the whole day to check what is available in the market, and concluded that Lucidchart UX is quite balanced.
- reactordev 1y agowell, they used to be - I just went and saw they sprinkled llms into it so yeah, now it's different. Diagrams.net aka Draw.io was what they were using...