• Alright—let’s make this concrete. I’ll translate your patterns into specific setups and decisions that actually fit how you operate.


    1. Your ideal studio is a control surface, not storage

    Image
    Image
    Image
    Image
    Image
    Image
    Image
    Image

    Your earlier realization about “decorative stationery” is the key constraint.

    What works for you:

    • Only tools that are in active rotation
    • Everything visible = everything usable
    • No “archive” on the desk itself

    Practical setup:

    • Desk = current project tools only
    • Secondary zone (drawer/box) = cold storage
    • Weekly or biweekly tool reset ritual

    If a pen survives 2 weeks on the desk → it’s legit
    If not → it goes away

    👉 You’re not organizing objects—you’re filtering relevance in real time


    2. Replace storage with staging layers

    Instead of “where things live,” think:

    LayerPurpose
    Hotcurrent project (on desk)
    Warmlikely next (reachable, but not visible)
    Coldrarely used (out of sight)

    Why this works for you:

    You naturally prune. This system makes pruning structural, not emotional.


    3. Your digital system should be pipeline-first, not library-first

    Image
    Image
    Image
    Image
    Image
    Image

    You already felt this with tags becoming a desert.

    Don’t build:

    • giant tag systems
    • knowledge archives
    • “second brain” complexity

    Build instead:

    A flow system:

    Input → Filter → Surface

    Example:

    • Input: RSS / social scraping
    • Filter: keyword + manual skim
    • Output: temporary, high-signal view

    👉 The key: information expires by default


    4. Kill tags. Use temporary lenses

    Tags failed you because they:

    • accumulate endlessly
    • pretend to be structure

    Replace with:

    • Short-lived collections
    • “Current visual direction”
    • “Typography ideas (this month)”
    • Delete or reset them regularly

    Think:

    Not classification, but curation windows


    5. Your tools should be legible + interruptible

    You don’t trust black boxes. So:

    Prefer:

    • Tools where you can see the logic
    • Systems you can break and rewire

    Avoid:

    • AI-heavy “magic” tools that hide decisions
    • Over-automated pipelines you can’t inspect

    Good fit mindset:

    • “Can I intervene mid-process?”

    If not → friction will build for you


    6. Build a daily signal ritual (15–20 min max)

    This is your antidote to overload.

    Structure:

    1. Scan inputs (feeds, refs, mentions)
    2. Select 3–5 signals
    3. Discard everything else
    4. Use or note immediately

    No saving for later unless:

    • it’s actionable
    • or immediately relevant

    👉 You’re not collecting—you’re sampling


    7. Your creative work benefits from constraint triggers

    Because you explore broadly, constraints sharpen output.

    Examples:

    • “Only one brush / one pen today”
    • “No undo”
    • “Black + one color”
    • “One idea, 10 variations”

    This aligns perfectly with:

    • generative thinking
    • symbolic exploration
    • iterative refinement

    8. Introduce a purge lever

    Right now you prune when things feel wrong.

    Make it explicit:

    Trigger conditions:

    • friction
    • too many options
    • visual noise
    • hesitation

    Action:

    • remove 30–50% immediately
    • no sorting, just cutting

    👉 This matches your natural instinct—but makes it faster and cleaner


    9. Your “sweet spot” tools (very specific)

    Based on everything:

    Physical:

    • Modular pen trays (not decorative holders)
    • Flat drawers (no deep boxes)
    • Mobile side cart (your “warm layer”)

    Digital:

    • RSS + filters (Huginn fits you well)
    • Lightweight notes (not heavy PKM systems)
    • Code snippets over plugins when possible

    10. The meta-rule that ties all of this together

    Everything should justify its presence by being used soon

    Not:

    • “might be useful”
    • “was useful once”
    • “looks nice”

    Only:

    • used now or next

    If you compress all of this into one sentence:

    You work best in systems that
    continuously destroy what’s no longer relevant
    so that what remains is immediately usable.


    If you want, I can map this into a very конкрет IKEA shopping list or a precise desk layout based on your current setup.

    Quelle: Code & Canvas

  • Alright—let’s make this concrete. I’ll translate your patterns into specific setups and decisions that actually fit how you operate.


    1. Your ideal studio is a control surface, not storage

    Image
    Image
    Image
    Image
    Image
    Image
    Image
    Image

    Your earlier realization about “decorative stationery” is the key constraint.

    What works for you:

    • Only tools that are in active rotation
    • Everything visible = everything usable
    • No “archive” on the desk itself

    Practical setup:

    • Desk = current project tools only
    • Secondary zone (drawer/box) = cold storage
    • Weekly or biweekly tool reset ritual

    If a pen survives 2 weeks on the desk → it’s legit
    If not → it goes away

    👉 You’re not organizing objects—you’re filtering relevance in real time


    2. Replace storage with staging layers

    Instead of “where things live,” think:

    LayerPurpose
    Hotcurrent project (on desk)
    Warmlikely next (reachable, but not visible)
    Coldrarely used (out of sight)

    Why this works for you:

    You naturally prune. This system makes pruning structural, not emotional.


    3. Your digital system should be pipeline-first, not library-first

    Image
    Image
    Image
    Image
    Image
    Image

    You already felt this with tags becoming a desert.

    Don’t build:

    • giant tag systems
    • knowledge archives
    • “second brain” complexity

    Build instead:

    A flow system:

    Input → Filter → Surface

    Example:

    • Input: RSS / social scraping
    • Filter: keyword + manual skim
    • Output: temporary, high-signal view

    👉 The key: information expires by default


    4. Kill tags. Use temporary lenses

    Tags failed you because they:

    • accumulate endlessly
    • pretend to be structure

    Replace with:

    • Short-lived collections
    • “Current visual direction”
    • “Typography ideas (this month)”
    • Delete or reset them regularly

    Think:

    Not classification, but curation windows


    5. Your tools should be legible + interruptible

    You don’t trust black boxes. So:

    Prefer:

    • Tools where you can see the logic
    • Systems you can break and rewire

    Avoid:

    • AI-heavy “magic” tools that hide decisions
    • Over-automated pipelines you can’t inspect

    Good fit mindset:

    • “Can I intervene mid-process?”

    If not → friction will build for you


    6. Build a daily signal ritual (15–20 min max)

    This is your antidote to overload.

    Structure:

    1. Scan inputs (feeds, refs, mentions)
    2. Select 3–5 signals
    3. Discard everything else
    4. Use or note immediately

    No saving for later unless:

    • it’s actionable
    • or immediately relevant

    👉 You’re not collecting—you’re sampling


    7. Your creative work benefits from constraint triggers

    Because you explore broadly, constraints sharpen output.

    Examples:

    • “Only one brush / one pen today”
    • “No undo”
    • “Black + one color”
    • “One idea, 10 variations”

    This aligns perfectly with:

    • generative thinking
    • symbolic exploration
    • iterative refinement

    8. Introduce a purge lever

    Right now you prune when things feel wrong.

    Make it explicit:

    Trigger conditions:

    • friction
    • too many options
    • visual noise
    • hesitation

    Action:

    • remove 30–50% immediately
    • no sorting, just cutting

    👉 This matches your natural instinct—but makes it faster and cleaner


    9. Your “sweet spot” tools (very specific)

    Based on everything:

    Physical:

    • Modular pen trays (not decorative holders)
    • Flat drawers (no deep boxes)
    • Mobile side cart (your “warm layer”)

    Digital:

    • RSS + filters (Huginn fits you well)
    • Lightweight notes (not heavy PKM systems)
    • Code snippets over plugins when possible

    10. The meta-rule that ties all of this together

    Everything should justify its presence by being used soon

    Not:

    • “might be useful”
    • “was useful once”
    • “looks nice”

    Only:

    • used now or next

    If you compress all of this into one sentence:

    You work best in systems that
    continuously destroy what’s no longer relevant
    so that what remains is immediately usable.


    If you want, I can map this into a very конкрет IKEA shopping list or a precise desk layout based on your current setup.

    Quelle: Code & Canvas

  • Here’s what I actually know about you—nothing more, nothing less:

    Basic profile

    • You’re 43 years old
    • Your name appears to be Mario (from your account name)
    • You’re likely based in Germany (around Böblingen, though that can be approximate)

    Your work & interests

    • You’re a graphic designer
    • You think a lot about:
      • design tools and workflows (WordPress, plugins, layout systems)
      • typography and writing style (you referenced The Elements of Eloquence)
      • artistic process and organization (tools, studio setup)
    • You also explore:
      • philosophical ideas (Taleb, Jung, symbolism, archetypes)
      • creative systems (generative/parametric design, journaling)
      • automation & tech setups (Huginn, RSS, feeds, scraping)

    Your style (from how you interact)

    • You like precise, practical explanations (step-by-step when needed)
    • But you also enjoy conceptual depth when the topic invites it
    • You iterate: you refine ideas rather than settling for first answers
    • You prefer things that are useful, not decorative fluff (you even said your tools became “decorative stationery,” which clearly annoyed you)

    What I don’t know

    • Anything sensitive (health, finances, private life, etc.)
    • Anything outside what you’ve explicitly shared or implied here
    • Your exact location, beyond a rough estimate

    If you want, I can also tell you what patterns I see in how you think/work (that’s usually the more interesting part).

    Quelle: Code & Canvas

  • Rethinking my working space. Having put everything into drawers and stationery has put away my tools for good. I have barely touched something not connected to my computer in months now, and I know why that happened: tools I don’t see are tools which don’t exist.
    I am fixing this now.

    Quelle: Code & Canvas

  • I mean, I quit them right now, but it has been a long time brewing, so I am taking note of that right here, on my after-hours blog.
    So, listen: I have tried GoodNotes and Notability, and I threw them out eventually because, really, I wasn’t really taking notes, although I bet I looked like I knew what I was doing at the time (that is a whole thing I need to get to talking about at some point, looking the part, rather than being the real deal).
    All I did was load PDFs into either app, watch the files sync with a Cloud service, and doncha know! I felt accomplished, write some chicken scratch on the first 15 pages of each file, and then quit.
    And now, after months of trying to make OneNote be my note taking app, I have snapped over how messy syncing OneNote Notebook is.
    I’ll go into a bit of detail here, you can skip this paragraph, especially because I have no idea where I am going with this: I tried to rename several of these Notebooks, as OneNote calls them, just to see the names being dropped, not used, then older Notebooks showing up in the list of selectable Notebooks, with old content having been moved to new Notebooks, all for the sake of creating some sort of order out of the chaos of the previous, what, nine years now. And I couldn’t, and I tried, and it wouldn’t stick, and Cloud is basically just shit I can pat myself on the back for making some kind of progress in, same with typing over writing, it all sure feels like you are getting somewhere because suddenly there is more of something where there was none before, but, for what I am doing, and how my mind works, there is a simple truth.
    I can only take useful notes using pen and paper. Drawing and sketching? Different, doesn’t matter there, but taking notes? I need paper. Same with reading. I need paper, and I also need the font to have serifs, because I need to understand, not just have an ease of reading experience, where the goal is to be done.
    Having had the recent Windows reset forced upon me turns out to be actually good for me. Earlier, before I snapped, I have felt a deep morosity over yet again spending hours at the PC trying to make something work which had the human as the after-thought for its use, or what the Millenial designers call human-centered design.
    So, OneNote went the same way GoodNotes and Notability went before, and I am back in control of a hand on a piece of paper.
    Sure, this is my manifesto, let me just send it into the database so you can read it.

    Quelle: Code & Canvas

  • Hi, there is always an open space on the web where you can start again. At least, that is what I think. And, to be honest, I need to think that way, because if I wouldn’t, I couldn’t change myself in any way.

    And what I need to start again, is to simulate my own graphic design study. I say simulate because I already have a degree for my thesis about how one could structure symbols and semiotics in space for living on Mars. One of my wilder things I have been up to in the past years.

    So, it did take me around six years to actually get my degree, due to what turned out were physical, rather than psychological health issues, and I actually wonder about how I even got a degree in the first place (looking back, I didn’t feel precisely conscious at the time).

    Why I am telling you this? Because I have been building a system for myself to go beyond what I have actually learned (and still recall) in my graphic design study, and in order to do that, I sort of need to “simulate” a study I did not have in the first place. Well-rested, not distracted, that sort of foundational situation, a foundation I did not have between 2017 and 2023. So, if you should have health issues, you should get help if you can, health seems to be a holistic state, a broken part affects the whole, as well as all the other parts, if you can get that.

    The system I came up with is really simple: you take ECTS and GURPS as your basis, add in the Dreyfus Model of Skill Acquisition, Bloom’s (revised) taxonomy, and deliberate practice research by Ericsson et al.

    And, what you might end up with, can sort of look like this: something sort of an RPG system for skill advancement.

    Level 0: Novice

    Cognitive & Behavioral Profile (Dreyfus/Bloom)
    No systematic knowledge; relies on rules or external guidance
    Typical Practice Focus
    Orientation, following instructions, foundational knowledge
    Typical Hours for Breakthrough*
    0–20 hrs

    Level 1: Advanced Beginner

    Cognitive & Behavioral Profile (Dreyfus/Bloom)
    Recognizes patterns; starts applying basic principles; low situational judgment
    Typical Practice Focus
    Guided exercises, rote practice, structured examples
    Typical Hours for Breakthrough*
    20–100 hrs

    Level 2: Competent

    Cognitive & Behavioral Profile (Dreyfus/Bloom)
    Can plan and troubleshoot; applies knowledge with some independence; moderate judgment
    Typical Practice Focus
    Deliberate practice on specific skills; small projects; self-correction
    Typical Hours for Breakthrough*
    100–300 hrs

    Level 3: Proficient

    Cognitive & Behavioral Profile (Dreyfus/Bloom)
    Holistic understanding; intuitive decision-making; adapts principles to context
    Typical Practice Focus
    Stretch projects, problem-solving in novel contexts; reflective practice
    Typical Hours for Breakthrough*
    300–700 hrs

    Level 4: Expert

    Cognitive & Behavioral Profile (Dreyfus/Bloom)
    Deep tacit understanding; high adaptability; can innovate; self-directed
    Typical Practice Focus
    Advanced deliberate practice, cross-domain integration, mentoring others
    Typical Hours for Breakthrough*
    700–1500 hrs

    Level 5: Master, or Authority

    Cognitive & Behavioral Profile (Dreyfus/Bloom)
    Recognized innovator; internalized skill; creates new paradigms
    Typical Practice Focus
    Leading projects, high-level synthesis, research/teaching others
    Typical Hours for Breakthrough*
    1500+ hrs

    *Hours indicate target deliberate practice hours; total invested time may be higher due to passive learning, casual exposure, or repetition.

    If you check out what I have written about that before, I was musing about how you can get a bachelor’s degree in the same amount of time it took me, using self-study, you can see what the flaw was, or rather is: that just putting in the hours does not guarantee progress.

    You need deliberate practice, DP for short. But how much?

    Well, way I figured it, for each level you are looking at the following target deliberate practice hours, and monthly DP goals, as a rough guide for everyone, especially the people stuck in /beg/ hell, like me:

    Level 0: Novice

    Cognitive Shift (Bloom + Dreyfus)
    Remember/Understand; follows instructions
    Deliberate Practice Focus
    Foundational rules, definitions
    Stretch Task Focus
    Simple guided tasks
    Target DP Hours
    0–20
    Monthly DP Goal
    2–4 hrs

    Level 1: Advanced Beginner

    Cognitive Shift (Bloom + Dreyfus)
    Apply/Analyze; begins pattern recognition
    Deliberate Practice Focus
    Structured exercises, error correction
    Stretch Task Focus
    Small independent projects
    Target DP Hours
    20–100
    Monthly DP Goal
    5–10 hrs

    Level 2: Competent

    Cognitive Shift (Bloom + Dreyfus)
    Apply/Analyze/Synthesize; plans work
    Deliberate Practice Focus
    Targeted practice, self-correction
    Stretch Task Focus
    Moderate independent projects
    Target DP Hours
    100–300
    Monthly DP Goal
    10–15 hrs

    Level 3: Proficient

    Cognitive Shift (Bloom + Dreyfus)
    Analyze/Synthesize/Evaluate; intuitive problem solving
    Deliberate Practice Focus
    Complex projects, deliberate reflection
    Stretch Task Focus
    Novel, high-risk projects
    Target DP Hours
    300–700
    Monthly DP Goal
    15–25 hrs

    Level 4: Expert

    Cognitive Shift (Bloom + Dreyfus)
    Evaluate/Create; deep tacit knowledge
    Deliberate Practice Focus
    Advanced skill integration
    Stretch Task Focus
    Cross-domain innovation, mentoring
    Target DP Hours
    700–1500
    Monthly DP Goal
    20–35 hrs

    Level 5: Master, or Authority

    Cognitive Shift (Bloom + Dreyfus)
    Create; paradigm-shifting
    Deliberate Practice Focus
    Leadership, teaching, R&D
    Stretch Task Focus
    High-level innovation
    Target DP Hours
    1500+
    Monthly DP Goal
    25-35+ hrs

    This is a community project, so you absolutely can add your own ideas, comment whichever way you like, use or not use this system. I even added double spaces so that copying is easier, lol.

    Below is essential reading material, if you want to read for yourself:

    So, that’s what I’m going to do now. Better six years late than not, if you ask me, life-long learning and all 😉

    I better update my journal now.

    Quelle: Code & Canvas

  • I’ll be brief: I have spent more than a week, since Friday the 13th, moving all of my backups out of the Cryptomator vault I have built inside my OneDrive Cloud folder, and am now using two external drives do backup my PC proper.
    I thought I was very clever having using Cryptomator, and I sort of bet a lot of people feel the same cleverness I did: to build something awkward, and somewhat servicable.
    But, ever since reinstalling my PC a few days ago (you can work from a cleaner slate, after all), copying files, and invariably losing files to the buggy interaction between Cryptomator and OneDrive Cloud, I have realized a very fundamental truth about Computers 2026:
    they are not broken. There is nothing to fix. Watching Defrag.exe walk through its rectangles in the 90s is no way to do Computers in 2026. The Cloud is nonsense. I am a graphic designer. I am done with tweaks.
    I have recently recovered my ideal workspace for my PC, and there is literally nothing to improve upon there.
    I think I will use all of my Social Media presence to slowly connect with people who are interested in improvng their craft, over being done, over doing finished pieces.
    If you feel that this is the community you also want, we will meet somewhere. I am putting my energy out there.
    Until next time, where I will continue building that which I myself need the most.

    Quelle: Code & Canvas

  • Ich habe seit letzten Freitag jetzt sechs volle Arbeitstage gebraucht, um einen Bug in meinem Backup-System zu lösen. Hot Storage und Cold Storage schlagen die Cloud um Längen. Ich bin fast wieder arbeitsfähig.

    https://t.co/0zABPqI3gY #asca

    Quelle: Twitter

  • Brushes von @kyle.t.webster während des Alumni-Abends von @fb_gestaltungundmedien_diploma und mit @eva_czajkowski, gehostet von @andreaskenlanig, ausprobiert: Ketchup- und Senfritter. Bin inspiriert vom heutigen Zoom-Meeting. Ich muss mal in mich gehen und fühlen, was ich will und was sich einfach (und im Moment richtig) anfühlt.

    Quelle: Instagram

  • Plain Text 3!
    Neues Mag von PlainText erhalten. Wird jetzt durchgelesen. (Preordered aus Frankreich; fresh off the press aus Lyon)
    #typomag #typozine #plaintext #laposte #plainform
    Quelle: Instagram

Schließe dich 900+ Abonnenten an

Bleibe auf dem Laufenden mit allem, was du wissen musst.