1,455 reputation
714
bio website
location San Francisco Bay Area
age
visits member for 2 years, 4 months
seen Aug 28 at 23:54

Follow me on Twitter @randallecook!


Aug
15
revised JS design pattern/algorithm for avoiding duplicate redraws in a fairly coupled system
put mention of a useful comment into the main answer so people will notice it
Aug
14
comment JS design pattern/algorithm for avoiding duplicate redraws in a fairly coupled system
I added another approach: an event queue. I'll add more as ideas pop into my head.
Aug
14
revised JS design pattern/algorithm for avoiding duplicate redraws in a fairly coupled system
added event queue approach
Aug
14
revised JS design pattern/algorithm for avoiding duplicate redraws in a fairly coupled system
expanded answer
Aug
14
answered JS design pattern/algorithm for avoiding duplicate redraws in a fairly coupled system
Aug
14
answered 1 class model or 3 class models? 1 for each - UI, Hardware API Library, and Database
Jul
30
answered Architecture for application-wide diagnostic-gathering tool?
Jul
30
answered Modeling Associations
Jul
29
comment How should data transfer between a client and a web API for normalized data be designed?
The batch model is different. This is sometimes called pagination, and in this case it is fine to bundle multiple instances of identically structured data into a list that is returned all at once. If that's the case with option 1, it looks more attractive. If it more of a network of related fields (like in a fully normalized RDBMS), then it is less attractive.
Jul
29
comment How should data transfer between a client and a web API for normalized data be designed?
Don't think of it as a generic API. Remember that the goal of an API is to provide an interface between two systems. It succeeds when it is optimized for facilitating the information or control transfer between those two systems, not necessarily when it is easy to program or follows an internal data model. Now don't go too far: it may be that the internal structure of your data is optimal for information transfer, in which case change nothing. But if it isn't, do what works best for the interface between the systems.
Jul
29
comment Creating system diagrams for a small app
The most important thing is that there is a connection between the detector (assuming that is what is connected to the COM port) and the computer. Assuming the purpose of your diagram is to present the overall architecture of the system, then I don't think the specific use of the COM port (versus USB or WiFi or ethernet or whatever) is relevant to the overall system function, so I would leave it out. If the purpose is to guide assembly of the system, then it should be left in as the use of the COM port is critical information in that context.
Jul
29
comment Creating system diagrams for a small app
Some external devices have special shapes that should be used, e.g. a cylinder for a database, or a cloud for the internet. But if it has a good, descriptive text label, you can't go wrong with a simple rectangular box. :)
Jul
29
comment Creating system diagrams for a small app
Yes, there are certainly conventions you can follow in terms of how each component is drawn in the diagram. Just imitate what you see in other professional diagrams, like in books, for instance.
Jul
29
answered Creating system diagrams for a small app
Jul
29
revised Creating system diagrams for a small app
fixed grammar
Jul
29
suggested suggested edit on Creating system diagrams for a small app
Jul
29
comment How should data transfer between a client and a web API for normalized data be designed?
Intriguing question! +1.
Jul
29
revised How should data transfer between a client and a web API for normalized data be designed?
expanded answer
Jul
29
answered How should data transfer between a client and a web API for normalized data be designed?
Apr
22
awarded  Yearling