It was us who scorched the sky…

MAICA - klingt in der Tat etwas wurstig

Nachtrag: Vielleicht wird es aber auch schlicht der Magenta AI call ASSistant

You seem trustworthy.

[The Gamers, 29:50]

Great.

asking that machine to improve writing is like asking a blender to improve a salad

A counterweight grows as people learn to reappreciate the acerbity of art and words. The ring is poisonous and must be destroyed, but it can unite.

I think the pink ones didn’t fare so well in evolutionary terms.

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

Look at the stars for a while.

Da haben sie letztes Mal wohl nur den Strohwels erwischt… an die wahren Hinterwelse kommt man ja so gut wie nie ran.

T+5 Jahre: Bremen verbannt als letztes Bundesland KI-Chatbots aus Schulen

deleted by creator

This one, I guess.

“The latest generation of ‘calculators’ (German synonym: computer), 16 colors, on a ‘solid plate’ (syn: hard drive) including mouse.”

“You should wait - it’s half the price in six months”

by Uli Stein

It’s all about damn good coffee.

The sequel’s plot is somehow weak with a couple of cringe moments. Given the twist is revealed in part one, the movie expresses one of many solutions to what should be free roaming of your own thoughts after the first film.

Sequels can be awful at destroying the ‘blew my mind’ effect in general by streamlining a great, open idea to a specific plot I guess.

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.

The question mixes up tests and logging. You are referring to logs.

Use a good logging package. It will allow you to distinguish at least (possibly with verbosity levels)

• trace
• debug
• information
• warning
• error

In production, configure the log level to be info-level or above, everything below will be hidden.

Lower levels can be useful for debugging automated tests. Possibly via a flag in production as well.

Yes, and in fact, the complete jetbrains toolbox works fine on Linux. Setup is commonly done by simply unzipping an archive.

Remmina is nice to manage remote access, see https://remmina.org/

I heard negative criticism of rustdesk in terms of security, can anyone confirm or refute this?

Frescobaldi as a front-end for Lilypond is quite nice as well