• 0 posts
  • 10 comments
Joined 3 years ago
Cake day: June 11th, 2023
  • Look what I just did:

    "In a real-time kernel, the trouble with using print_k (or similar logging functions) often revolves around potential disruptions to real-time performance. Here are some key issues:

    1. Blocking Behavior: print_k may block if the output buffer is full, leading to unpredictable delays in real-time tasks.

    2. Interrupt Context: Using logging functions within interrupt handlers can lead to priority inversion, causing lower-priority tasks to block higher-priority ones.

    3. Latency: Printing can introduce significant latency, which is detrimental in real-time systems that require deterministic timing.

    4. Context Switching: Frequent logging can increase context switching overhead, impacting overall system performance.

    5. Overhead: The computational overhead of formatting and outputting strings can interfere with time-sensitive operations.

    For these reasons, it’s typically recommended to use alternative methods, such as circular buffers for logging, or to minimize logging in real-time contexts.

    "

  • I don’t know about you, but I always get a bit of that puzzly feel when I am confronted with unstructured data that I need to process and maybe evaluate statistically.

    So if you want to turn this into money, maybe a few basic online learning resources on statistics should get your foot in the door with employers. Then think of which companies in your area might have to deal with raw data (think lots of customer interaction, or also environmental agencies, insurance companies, man, gotta be lots) and just apply to your dream company even if they have no offers posted. Often there are open positions they don’t advertise. And a programmer with statistical knowledge (don’t be humble) and initiative should usually find some attention.