• 10 Posts
  • 930 Comments
Joined 7 months ago
cake
Cake day: November 12th, 2024

help-circle

  • I have an old case that takes a PSU at the top.
    I bought a PSU made for being at the bottom, and placing it in their meant giving it the CPU heat in its intake. It felt like it would burn up any minute.

    I took some used aluminium cans, cut them up using expensive scissors (~5x the price of normal scissors, in turn, it won’t go bad, cutting plastic boxes and aluminium sheet) and made a frame to mount the PSU on the top, instead of inside the case.

    The wires had to go around, making it a partially open case, but it worked. No feeling of imminent fire hazard and the PSU was exhausting air at a relieving temperature.









  • From what I think, a CAD application with just a good enough base UI and proper support for different levels of precision is enough.

    Then scripting support can be added (maybe Python, like Blender does) and then the technology teams of the respective departments can manage making scripts for whatever requirements they might have.

    Of course it might not give the good looking UI and maybe even lack the in-viewport annotations (also, pretty renderings for materials) for those extra features that stuff like Revit provides (which is specialised for buildings as compared to plain AutoCAD), but it would do the job, which, from what I have seen, is what people look for as a first. The pretty graphics are just an extra.

    On the other hand, it might be possible to provide some sort of an API to the scripting language, to add annotations and textures as properties to the in-viewport elements and maybe even some presets for viewport widgets, which might be utilised with scripted logic. Any more than that, and it would warrant a proper plugin, made in the source language.




  • It will depend upon other things you might want to do with it in the future.
    If you want the record to stay “correct” in the future, you might want to have a separate entry for nationality information, which will be a 1-to-1 mapping with the other table you make for it. Why? …

    • in the nationality information, along with the country code (for which you want to allow 3 character codes for forward compatibility), the date at which the the information was given in the form
    • if possible, also include the date at which the nationality was provided (as in, provided to the user by the nation)

    This should help determine what kind of change may occur in case of changes in the political landscape in the future, without you requiring to re-ask the form-filler.


    Inspired by https://flightaware.engineering/falsehoods-programmers-believe-about-aviation/
    And I am going to consider this stuff every time I make a database schema.

    Stuff in the real world is subject to change, so instead of only storing the provided data as you asked for, make a ledger for events. And someone submitting a forms, will be another event.

    This way, you get the flexibility to verify the provided data in the future, using information that you will have in the future, but don’t have at the time the data was provided.

    Of course, this is only needed if it is needed.