home.social

#erd — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #erd, aggregated by home.social.

  1. europesays.com/hu/87621/ Cikkeink és a lakossági felháborodás hatására távoznak Érd és Budapest határából az akkumulátoriparhoz kötődő cégek #akkumulátoripar #budapest #érd #HU #Hungarian #Hungary #Magyar #Magyarország

  2. **Ngày 45: no-prompts** | Nền tảng chạy trên PostgreSQL, thiết kế ERD & hệ thống ORM riêng đã hoạt động. Hiện còn bất ổn, cần rút gọn code và nâng cấp cơ sở hạ tầng. Kế hoạch triển khai ERD Editor trên framework đã xây dựng, hướng tới phiên bản 1.0 vào tháng 2. #TechUpdate #SaaS #PhátTriểnPhầnMềm #PostgreSQL #Terraform #ERD #ViệcLàmIT

    reddit.com/r/SaaS/comments/1qp

  3. Mô hình hóa ERD giúp nhận diện các mẫu lặp lại: BaseAnalyzer, BaseStore, BaseDialect có cấu trúc tương tự. Hôm nay tập trung vào API: định nghĩa, endpoint, kiểm soát truy cập – cũng là "định nghĩa, lưu trữ và truy cập dữ liệu". Ứng dụng cấu trúc ERD giúp tối ưu trừu tượng hóa. Vấn đề lớn nhất: khiến Claude Code tuân theo mẫu này một cách nhất quán.
    #Abstraction #ERD #API #SoftwareDesign #LậpTrình #ThiếtKếHệThống #MãNguồn #DevPattern

    reddit.com/r/SaaS/comments/1qi

  4. The time I used diagramming for success

    I had a project idea in my head that seemed too complex to work on until I tried diagramming it.

    The idea was a multipurpose CRM-like action/account system thing. I think it might best be described by my first diagram.

    I mean, just look at that nonsense. How was I supposed to make a database that handles that? It is the kind of nonsense that gets called “Enterprise” and costs eye-watering piles of cash to keep working.

    That was where diagram 2 came in. Having identified groups and entities, it was possible to restructure to something approaching third normal form.

    Thus, I made this:

    All of that complicated referential business logic boiled down to a fairly simple data logic.

    The moral of the story is this: If you have an idea that refuses to be wrestled into a neat or functional shape in your head, write down whatever you have. Lay it out as logically as you can. Often, in the process of writing it down, you will find that the problem can be tamed. The process of writing it down forces you to be clear about everything. Writing it down forces you to process one bit at a time.

    The result is often greater clarity.

    In my case, I feel ready to start planning the data API layer with what should be some fairly efficient database abstraction.

    Sure, I’m going to have a few strange-looking UNION SELECT statements, and more LEFT JOIN and INNER JOIN than normal but I will also have optimised indexes for those selects and joins. Which means that it will not stress my database.

    Also, I can use write and read replication to scale my idea.

    Please share your thoughts on this with me.

    Syndicated to: #DataLayer #Database #diagram #ERD
  5. The time I used diagramming for success

    I had a project idea in my head that seemed too complex to work on until I tried diagramming it.

    The idea was a multipurpose CRM-like action/account system thing. I think it might best be described by my first diagram.

    I mean, just look at that nonsense. How was I supposed to make a database that handles that? It is the kind of nonsense that gets called “Enterprise” and costs eye-watering piles of cash to keep working.

    That was where diagram 2 came in. Having identified groups and entities, it was possible to restructure to something approaching third normal form.

    Thus, I made this:

    All of that complicated referential business logic boiled down to a fairly simple data logic.

    The moral of the story is this: If you have an idea that refuses to be wrestled into a neat or functional shape in your head, write down whatever you have. Lay it out as logically as you can. Often, in the process of writing it down, you will find that the problem can be tamed. The process of writing it down forces you to be clear about everything. Writing it down forces you to process one bit at a time.

    The result is often greater clarity.

    In my case, I feel ready to start planning the data API layer with what should be some fairly efficient database abstraction.

    Sure, I’m going to have a few strange-looking UNION SELECT statements, and more LEFT JOIN and INNER JOIN than normal but I will also have optimised indexes for those selects and joins. Which means that it will not stress my database.

    Also, I can use write and read replication to scale my idea.

    Please share your thoughts on this with me.

    Syndicated to: #DataLayer #Database #diagram #ERD
  6. The time I used diagramming for success

    I had a project idea in my head that seemed too complex to work on until I tried diagramming it.

    The idea was a multipurpose CRM-like action/account system thing. I think it might best be described by my first diagram.

    I mean, just look at that nonsense. How was I supposed to make a database that handles that? It is the kind of nonsense that gets called “Enterprise” and costs eye-watering piles of cash to keep working.

    That was where diagram 2 came in. Having identified groups and entities, it was possible to restructure to something approaching third normal form.

    Thus, I made this:

    All of that complicated referential business logic boiled down to a fairly simple data logic.

    The moral of the story is this: If you have an idea that refuses to be wrestled into a neat or functional shape in your head, write down whatever you have. Lay it out as logically as you can. Often, in the process of writing it down, you will find that the problem can be tamed. The process of writing it down forces you to be clear about everything. Writing it down forces you to process one bit at a time.

    The result is often greater clarity.

    In my case, I feel ready to start planning the data API layer with what should be some fairly efficient database abstraction.

    Sure, I’m going to have a few strange-looking UNION SELECT statements, and more LEFT JOIN and INNER JOIN than normal but I will also have optimised indexes for those selects and joins. Which means that it will not stress my database.

    Also, I can use write and read replication to scale my idea.

    Please share your thoughts on this with me.

    Syndicated to: #DataLayer #Database #diagram #ERD
  7. The time I used diagramming for success

    I had a project idea in my head that seemed too complex to work on until I tried diagramming it.

    The idea was a multipurpose CRM-like action/account system thing. I think it might best be described by my first diagram.

    I mean, just look at that nonsense. How was I supposed to make a database that handles that? It is the kind of nonsense that gets called “Enterprise” and costs eye-watering piles of cash to keep working.

    That was where diagram 2 came in. Having identified groups and entities, it was possible to restructure to something approaching third normal form.

    Thus, I made this:

    All of that complicated referential business logic boiled down to a fairly simple data logic.

    The moral of the story is this: If you have an idea that refuses to be wrestled into a neat or functional shape in your head, write down whatever you have. Lay it out as logically as you can. Often, in the process of writing it down, you will find that the problem can be tamed. The process of writing it down forces you to be clear about everything. Writing it down forces you to process one bit at a time.

    The result is often greater clarity.

    In my case, I feel ready to start planning the data API layer with what should be some fairly efficient database abstraction.

    Sure, I’m going to have a few strange-looking UNION SELECT statements, and more LEFT JOIN and INNER JOIN than normal but I will also have optimised indexes for those selects and joins. Which means that it will not stress my database.

    Also, I can use write and read replication to scale my idea.

    Please share your thoughts on this with me.

    Syndicated to: #DataLayer #Database #diagram #ERD
  8. Phát triển ERD Editor phiên bản 1 bằng React Flow – cho phép tạo bảng, định nghĩa cột và xem cấu trúc trực quan. Giao diện còn đơn giản nhưng đang được cải thiện từng bước. #ERD #DatabaseDesign #ReactFlow #SaaS #Developer #ThiếtKếCơSởDữLiệu #LậpTrình #CôngCụPhátTriển

    reddit.com/r/SaaS/comments/1q4

  9. Bist Du wirklich fit in der #Modellierung von #Datenbanken? Dann sollte diese Übungsaufgabe mit schwachen Entitätstypen, abgeleiteten, eingabepflichtigen, mehrwertigen und optionalen Attributen Dich nicht schrecken. Mit einer Beispiellösung, weil man vieles eben doch nicht auf Anhieb findet. (Aus der Abteilung: How far can u push it?). #ERD #Relationenmodell #Normalisierung #informatikEdu oer-informatik.de/db-modellier

  10. Bist Du wirklich fit in der #Modellierung von #Datenbanken? Dann sollte diese Übungsaufgabe mit schwachen Entitätstypen, abgeleiteten, eingabepflichtigen, mehrwertigen und optionalen Attributen Dich nicht schrecken. Mit einer Beispiellösung, weil man vieles eben doch nicht auf Anhieb findet. (Aus der Abteilung: How far can u push it?). #ERD #Relationenmodell #Normalisierung #informatikEdu oer-informatik.de/db-modellier

  11. Bist Du wirklich fit in der #Modellierung von #Datenbanken? Dann sollte diese Übungsaufgabe mit schwachen Entitätstypen, abgeleiteten, eingabepflichtigen, mehrwertigen und optionalen Attributen Dich nicht schrecken. Mit einer Beispiellösung, weil man vieles eben doch nicht auf Anhieb findet. (Aus der Abteilung: How far can u push it?). #ERD #Relationenmodell #Normalisierung #informatikEdu oer-informatik.de/db-modellier

  12. Нотации в работе бизнес-аналитика: какие выбрать и зачем они нужны

    Одно недопонимание на встрече может стоить вам недель переделок. В этой статье рассказываем, какие визуальные нотации помогут бизнес-аналитикам и командам понимать друг друга без лишних ошибок. Простые схемы и диаграммы, которые ускорят работу и сделают процессы понятнее для всех: от заказчика до разработчика. Узнайте, как выбирать и применять BPMN, ERD, Sequence Diagram и User Story Mapping в реальных проектах.

    habr.com/ru/articles/940154/

    #bpmn #erd #нотации #sequence_diagram #user_story_mapping #визуализация_процессов #бизнесанализ #коммуникация_с_командой

  13. Нотации в работе бизнес-аналитика: какие выбрать и зачем они нужны

    Одно недопонимание на встрече может стоить вам недель переделок. В этой статье рассказываем, какие визуальные нотации помогут бизнес-аналитикам и командам понимать друг друга без лишних ошибок. Простые схемы и диаграммы, которые ускорят работу и сделают процессы понятнее для всех: от заказчика до разработчика. Узнайте, как выбирать и применять BPMN, ERD, Sequence Diagram и User Story Mapping в реальных проектах.

    habr.com/ru/articles/940154/

    #bpmn #erd #нотации #sequence_diagram #user_story_mapping #визуализация_процессов #бизнесанализ #коммуникация_с_командой

  14. Нотации в работе бизнес-аналитика: какие выбрать и зачем они нужны

    Одно недопонимание на встрече может стоить вам недель переделок. В этой статье рассказываем, какие визуальные нотации помогут бизнес-аналитикам и командам понимать друг друга без лишних ошибок. Простые схемы и диаграммы, которые ускорят работу и сделают процессы понятнее для всех: от заказчика до разработчика. Узнайте, как выбирать и применять BPMN, ERD, Sequence Diagram и User Story Mapping в реальных проектах.

    habr.com/ru/articles/940154/

    #bpmn #erd #нотации #sequence_diagram #user_story_mapping #визуализация_процессов #бизнесанализ #коммуникация_с_командой

  15. Нотации в работе бизнес-аналитика: какие выбрать и зачем они нужны

    Одно недопонимание на встрече может стоить вам недель переделок. В этой статье рассказываем, какие визуальные нотации помогут бизнес-аналитикам и командам понимать друг друга без лишних ошибок. Простые схемы и диаграммы, которые ускорят работу и сделают процессы понятнее для всех: от заказчика до разработчика. Узнайте, как выбирать и применять BPMN, ERD, Sequence Diagram и User Story Mapping в реальных проектах.

    habr.com/ru/articles/940154/

    #bpmn #erd #нотации #sequence_diagram #user_story_mapping #визуализация_процессов #бизнесанализ #коммуникация_с_командой

  16. Генерация диаграммы «Сущность-Связь/ Entity-Relationship» с помощью Laravel

    Laravel ERD (Схема сущность/связь) Автоматическая генерация диаграмм базы данных под ваши сущности в Laravel

    habr.com/ru/articles/841774/

    #ERD #Database #php #laravel #package #composer

  17. Генерация диаграммы «Сущность-Связь/ Entity-Relationship» с помощью Laravel

    Laravel ERD (Схема сущность/связь) Автоматическая генерация диаграмм базы данных под ваши сущности в Laravel

    habr.com/ru/articles/841774/

    #ERD #Database #php #laravel #package #composer

  18. Генерация диаграммы «Сущность-Связь/ Entity-Relationship» с помощью Laravel

    Laravel ERD (Схема сущность/связь) Автоматическая генерация диаграмм базы данных под ваши сущности в Laravel

    habr.com/ru/articles/841774/

    #ERD #Database #php #laravel #package #composer

  19. @RuthMalan

    Check research on #ReadinessPotential #RP
    Event-related desynchronization #ERD
    Integration to bound models #ITB

    The Neural Bases of Motor Awareness
    #WilliamJames Prize 2023
    #ElisabethParésPujolràs
    #ASSC26 lecture
    youtu.be/watch?v=ZA9lqzBDugo

    Feeling ready:
    Neural bases of prospective motor readiness judgements
    w/ #KarlaMatić #PatrickHaggard
    doi.org/10.1093/nc/niad003

    Using a Veto Paradigm to Investigate the Decision Model of Libet-style Experiments
    Shum et al
    osf.io/preprints/psyarxiv/wsn4

  20. @RuthMalan

    Check research on #ReadinessPotential #RP
    Event-related desynchronization #ERD
    Integration to bound models #ITB

    The Neural Bases of Motor Awareness
    #WilliamJames Prize 2023
    #ElisabethParésPujolràs
    #ASSC26 lecture
    youtu.be/watch?v=ZA9lqzBDugo

    Feeling ready:
    Neural bases of prospective motor readiness judgements
    w/ #KarlaMatić #PatrickHaggard
    doi.org/10.1093/nc/niad003

    Using a Veto Paradigm to Investigate the Decision Model of Libet-style Experiments
    Shum et al
    osf.io/preprints/psyarxiv/wsn4

  21. @RuthMalan

    Check research on #ReadinessPotential #RP
    Event-related desynchronization #ERD
    Integration to bound models #ITB

    The Neural Bases of Motor Awareness
    #WilliamJames Prize 2023
    #ElisabethParésPujolràs
    #ASSC26 lecture
    youtu.be/watch?v=ZA9lqzBDugo

    Feeling ready:
    Neural bases of prospective motor readiness judgements
    w/ #KarlaMatić #PatrickHaggard
    doi.org/10.1093/nc/niad003

    Using a Veto Paradigm to Investigate the Decision Model of Libet-style Experiments
    Shum et al
    osf.io/preprints/psyarxiv/wsn4

  22. @RuthMalan

    Check research on #ReadinessPotential #RP
    Event-related desynchronization #ERD
    Integration to bound models #ITB

    The Neural Bases of Motor Awareness
    #WilliamJames Prize 2023
    #ElisabethParésPujolràs
    #ASSC26 lecture
    youtu.be/watch?v=ZA9lqzBDugo

    Feeling ready:
    Neural bases of prospective motor readiness judgements
    w/ #KarlaMatić #PatrickHaggard
    doi.org/10.1093/nc/niad003

    Using a Veto Paradigm to Investigate the Decision Model of Libet-style Experiments
    Shum et al
    osf.io/preprints/psyarxiv/wsn4

  23. @RuthMalan

    Check research on #ReadinessPotential #RP
    Event-related desynchronization #ERD
    Integration to bound models #ITB

    The Neural Bases of Motor Awareness
    #WilliamJames Prize 2023
    #ElisabethParésPujolràs
    #ASSC26 lecture
    youtu.be/watch?v=ZA9lqzBDugo

    Feeling ready:
    Neural bases of prospective motor readiness judgements
    w/ #KarlaMatić #PatrickHaggard
    doi.org/10.1093/nc/niad003

    Using a Veto Paradigm to Investigate the Decision Model of Libet-style Experiments
    Shum et al
    osf.io/preprints/psyarxiv/wsn4

  24. "Order a year's worth in advance" ?
    ---
    RT @ChemistDruggist
    NHS England has urged patients to set up electronic repeat dispensing (#eRD) ahead of #Easter holiday #pharmacy closures

    bit.ly/3FIsdpD
    twitter.com/ChemistDruggist/st

  25. "Order a year's worth in advance" ?
    ---
    RT @ChemistDruggist
    NHS England has urged patients to set up electronic repeat dispensing (#eRD) ahead of #Easter holiday #pharmacy closures

    bit.ly/3FIsdpD
    twitter.com/ChemistDruggist/st

  26. "Order a year's worth in advance" ?
    ---
    RT @ChemistDruggist
    NHS England has urged patients to set up electronic repeat dispensing (#eRD) ahead of #Easter holiday #pharmacy closures

    bit.ly/3FIsdpD
    twitter.com/ChemistDruggist/st

  27. "Order a year's worth in advance" ?
    ---
    RT @ChemistDruggist
    NHS England has urged patients to set up electronic repeat dispensing (#eRD) ahead of #Easter holiday #pharmacy closures

    bit.ly/3FIsdpD
    twitter.com/ChemistDruggist/st

  28. The #DuckDBPro Tools beta available to our Pro sponsors soon will have #DuckDB #ERD view as promised!

    Sign up to get notified when you can use this feature with access to our private beta release repo later this month! 👇

    💖💰 ⤑ github.com/sponsors/RandomFrac

    #Pro #SQL #DataTools

  29. The #DuckDBPro Tools beta available to our Pro sponsors soon will have #DuckDB #ERD view as promised!

    Sign up to get notified when you can use this feature with access to our private beta release repo later this month! 👇

    💖💰 ⤑ github.com/sponsors/RandomFrac

    #Pro #SQL #DataTools

  30. The #DuckDBPro Tools beta available to our Pro sponsors soon will have #DuckDB #ERD view as promised!

    Sign up to get notified when you can use this feature with access to our private beta release repo later this month! 👇

    💖💰 ⤑ github.com/sponsors/RandomFrac

    #Pro #SQL #DataTools

  31. The #DuckDBPro Tools beta available to our Pro sponsors soon will have #DuckDB #ERD view as promised!

    Sign up to get notified when you can use this feature with access to our private beta release repo later this month! 👇

    💖💰 ⤑ github.com/sponsors/RandomFrac

    #Pro #SQL #DataTools

  32. The #DuckDBPro Tools beta available to our Pro sponsors soon will have #DuckDB #ERD view as promised!

    Sign up to get notified when you can use this feature with access to our private beta release repo later this month! 👇

    💖💰 ⤑ github.com/sponsors/RandomFrac

    #Pro #SQL #DataTools

  33. is an entity-relationship diagram generator.

    erd takes in a textual schema with associated list of relationships and generates a graph displaying the connections. The input schema is a list of entities, each with a title and a set of keys. The relationships connect entities with one of four cardinalities. erd automatically positions entities and allows for entities and keys to have custom formatting.

    Website 🔗️: github.com/BurntSushi/erd

  34. #erd is an entity-relationship diagram generator.

    erd takes in a textual schema with associated list of relationships and generates a graph displaying the connections. The input schema is a list of entities, each with a title and a set of keys. The relationships connect entities with one of four cardinalities. erd automatically positions entities and allows for entities and keys to have custom formatting.

    Website 🔗️: github.com/BurntSushi/erd

    #free #opensource #foss #fossmendations #database

  35. #blockchain #ERD Grande nouvelle pour @[email protected] 🇷🇴 ! Ses équipes ont travaillé dur, et, notamment grâce au soutien de @[email protected], la phase "The Genesis" est imminente ! @[email protected] fera notamment partie des nœuds validateurs. @[email protected] 👇 journalducoin.com/blockchain/e

  36. #blockchain #ERD Grande nouvelle pour @[email protected] 🇷🇴 ! Ses équipes ont travaillé dur, et, notamment grâce au soutien de @[email protected], la phase "The Genesis" est imminente ! @[email protected] fera notamment partie des nœuds validateurs. @[email protected] 👇 journalducoin.com/blockchain/e