• 1 Post
  • 77 Comments
Joined 7 months ago
cake
Cake day: November 12th, 2024

help-circle


  • One way might be to flush it with a spoonful of 99% IPA[1], followed by some wiggling and then using a compressed air-can to push wind into it from one direction, causing the IPA and the dirt mixed with it to come out of some gap in the opposite direction.

    Since it is the Ctrl key (hoping it to be in the a corner as it usually is), you can tilt the keyboard such that the Ctrl key is on the bottom, then pour IPA on the higher corner of the key, such that it drenches the PCB under the key while flowing down and while you wiggle it. And then again, spray from the higher point, such that the exhaust is in the direction of the edges and corners, reducing the dirt that might transfer to other keys.

    However, you might want to check just in case the back is removable. That should make stuff easier as you then won’t require guessing which way the dirt solution might go in a closed box.

    Either way, keep it for a while after you do the thing and before plugging it in (right, you need to unplug it first), so that most of the IPA is evaporated before you start it up.
    Keyboards tend to be much simpler as compared to stuff like motherboards, so I’d guess using a hair dryer instead of compressed air should be fine too (just don’t turn on the heat).


    1. https://en.wikipedia.org/wiki/Isopropyl_alcohol ↩︎


















  • 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.