I was reading this discussion about designing a database structure:
I asked a question but I think I’m being disruptive, so I’ve started this new thread. I’ll link here from there.
When I saw the question, I imagined the answer would be a diagram and from that diagram, a representation in code would appear. Does that ‘diagram happen’ in the heads of the people who replied or do you skip straight to code? Would you if the question was more complex?
I’m a very visual thinker and I’m beginning to suspect that current web developers aren’t. I’m interested because in my last job as an analyst in an Agile team, my stakeholders loved UML diagrams and they were useful in discussions and to highlight differences in understanding but the devs didn’t care enough about them, so didn’t tell me when things had changed. As I’ve yet to find a 2-way UML/code conversion tool that works well enough, I don’t know how to avoid that situation in future.
I do imagine in my head how different tables are going to interact with each other but not the diagram. I normally go straight into designing Database schema.
I find database diagrams really complex. I took an Open Uni module on Database and couldn’t finish it all because of these diagrams.
I can imagine diagrams being really helpful for complex databases. Do you think that they are as useful for even smaller databases as larger ones?
Sorta. When I do database modelling I have a concept in my head; I can see how the data fits together. I can then “serialise” that diagram into an entity-relationship diagram or some SQL DDL commands or whatever.
And off we go…