• 3 Posts
  • 50 Comments
Joined 2 years ago
cake
Cake day: July 25th, 2023

help-circle



  • Personal experience, obviously:

    1. enforce time limits on apps (like 45 min messaging/social per day), e.g. using built-in tools => frees a lot of time
    2. streamline communication, i.e., do not be available 24/7 for mail, chat, etc. Instead, define time windows to check and answer your channels
    3. Use some Pomodore timer [1] to focus on specific tasks for a few hours. Minimize distractions as far as possible in that time window.
    4. Sleep. Working tired is a black hole for time management.
    5. Do sports/seek nature to keep the stress level down.
    6. Plan honest to your capabilities, sometimes the 80% solution will do (yes, this can be hard to accept)
    7. A simple hand-written checkboxed ToDo list per day is helpful, take 5-10 minutes to compile it before your day starts.

    [1] Goodtime


  • There were several incidents (ref. 1), but in particular Fukushima in 2011 changed a lot, as it was a modern type of power plant.

    It reignited discussions regarding safety and (under the impression of 9/11) fears that nuclear power facilities could be targeted by terror attacks.

    With current regulations new reactors can cost some 20 to 40 billion, making it one of the most expensive sources of electrical energy. Costs for decomissioning are significant as well. Both building and decomissioning costs are typically passed on to tax payers.

    Also, permanent storage of used burning rods is hard, nobody wants nuclear waste buried in their neighborhood. Given its half life of ~240 000 years, it may also be difficult to communicate its dangers to future generations (ref. 2).

    The currently most common sources of burning material (Uranium) stem from - large parts - politically controverse regions and may in sum last some estimated 80-100 years, quite short given some 10-20 years of construction time per plant.

    This is not talking about thorium and salt reactors, but technical challenges and costs seem to be limiting for these technologies, in particular as long as the default infrastructure exists.

    edit: the ‘new’ types are more complex and not suited for weapons in general.

    1: https://en.wikipedia.org/wiki/List_of_civilian_nuclear_accidents?wprov=sfla1

    2: https://www.youtube.com/watch?v=PUXwrWMS-x8









  • Apologies for being too cryptic/jargon. Pro tip: a real-life mentor can adapt to your level on-the-fly, if available.

    Maybe this introduction helps a bit to get an overview - from the context I expect you are on JavaScript or related.

    It’s often hard to grasp why packages or techniques exist unless you ran into the problems that motivated the solution yourself.

    In this case, it’s all about filtering by the severity of log messages (debug level). If the level is high, your app will show tiny bits of information. These do not need to show for every user, except if they want to enable it (via techniques like a switch/flag, environment variable or a config file).

    Config files or profiles are often used to enable/disable code parts in production or to configure how often scheduled jobs should be triggered and so on.

    Depending on your level of expertise logging stuff via the console may be just fine for the moment. In particular if you are the sole developer. Once you’re annoyed by your own logs, incrementally replace the ‘prints’ with a library that feels comfortable or well-documented.