Indeed

anime irl

https://v.redd.it/6x6b34b634mg1/CMAF_1080.mp4

My first edit is probably a year, how did I do?

We bought into the dream. The smart home nirvana where lights adjust to your mood, coffee brews itself, and the thermostat *knows* you're coming home. We invested in every sensor, switch, and hub. We spent hours scripting routines, linking platforms, and debugging. And after all that? We mostly just automated frustration. Turns out, there's one thing our smart home systems consistently lack: common sense.

**Quick Take**

*   **Over-automation is a trap.** It often adds complexity, not convenience.
*   **Context is king.** Automated rules struggle with human nuance and unexpected situations.
*   **Start small, solve specific problems.** Don't try to automate everything at once.
*   **Manual overrides are non-negotiable.** You *must* be able to easily bypass any automation.
*   **The "why" matters more than the "what if."** Focus on real pain points.
*   **Maintenance debt is real.** Smart homes demand ongoing attention.
*   **The human element is invaluable.** Intuition and quick adjustments are hard to code.
*   **Simplicity wins.** A few reliable automations beat a hundred flaky ones.

## My Setup / Context

My journey into home automation started innocently enough about five years ago. I was captivated by the idea of a truly "smart" home – one that anticipated needs, saved energy, and just *worked* in the background. My setup grew from a few smart bulbs to a sprawling network encompassing almost every room.

We're talking:
*   **Lighting:** Dozens of smart bulbs, light switches, and dimmer modules across the house.
*   **Climate:** A learning thermostat integrated with temperature sensors in multiple zones.
*   **Security:** Door/window sensors, motion detectors, cameras, and smart locks.
*   **Entertainment:** Smart TVs, soundbars, and voice assistants linked to media playback.
*   **Blinds:** Motorized shades on several windows.
*   **Small appliances:** Smart plugs for coffee makers, fans, and humidifiers.

I dabbled with a couple of major brand ecosystems before settling on a more open-source hub as the central brain, trying to bring everything under one roof. The initial investment in hardware and the countless hours spent configuring was driven by pure enthusiasm and the promise of a seamless future.

## Where Common Sense Went Missing

The promise of a smart home often overshadows the messy reality of living in one. Our greatest misstep wasn't in choosing the wrong tech, but in assuming the tech could replace basic human judgment.

### The "If This Then That" Trap

Most automations are based on simple logic: *If X happens, then do Y*. This works great in controlled environments. Houses, with people and pets, are anything but.

Here's where my "smart" home routinely fell flat:

1.  **Motion-triggered lights:** Sounds brilliant, right? Walk into a room, lights come on. Perfect. Until you're sitting still, reading a book, or watching a movie, and the lights abruptly plunge you into darkness because you haven't moved enough in five minutes. Or your cat strolls past the sensor, triggering the bathroom light at 3 AM. The system lacks the common sense to know if the room is *occupied* or just has *motion*.
2.  **Learning thermostats:** These claim to learn your schedule and preferences. Mine "learned" to crank the AC when I was consistently working from home. Great, until I went on vacation, and it kept cooling an empty house. Or when guests stayed over, and it stubbornly stuck to *my* learned schedule, ignoring their comfort. It had data, but no understanding of an altered routine.
3.  **Sunrise/Sunset triggered blinds:** An automation to open bedroom blinds at sunrise feels luxurious. Until you realize sunrise changes throughout the year, sometimes clashing with a desired lie-in. Or worse, it opens them wide just as you're on a video call, bathing your face in harsh light. The system doesn't know if you're sleeping, working, or just prefer privacy.
4.  **Presence-based door locks:** Lock the door when everyone leaves, unlock when someone returns. Fantastic. Except when your phone dies, or a child forgets their device, or a repair person needs entry when you're just down the street. It only understands "device presence," not "human intent."

The issue isn't the technology's capability; it's the inability to bake in the complex, often subconscious, context that humans use every second.

### The "Too Many Cooks" Problem

When multiple systems or people have control, things get messy. My central hub might want to turn off the living room lights because it's past bedtime, but my voice assistant just heard me say "Turn on all lights" because I dropped something. Conflict. The system doesn't know which command takes precedence based on the immediate situation.

Then there's the partner acceptance factor. "Why did the kitchen light just turn off on me?" "The blinds just closed in the middle of my meeting!" If the automation frustrates others in the household, it's a net negative, no matter how clever you think it is. Common sense dictates a system should make *everyone's* life easier, not just the primary configurator.

### Maintenance Debt

Every smart device is another device that needs power, updates, and occasional troubleshooting. Batteries die without warning. Firmware updates break integrations. Wi-Fi drops, taking half your house offline. Suddenly, what was supposed to save time becomes a new, unpaid technical support role. The mental overhead of maintaining this complex web often outweighs the marginal gains.

## Real-World Tradeoffs

Our experience highlighted some stark realities:

| Aspect         | The Dream (Marketing)           | The Reality (Experience)        |
|----------------|---------------------------------|---------------------------------|
| **Lighting**   | Seamless, adaptive, mood-setting | Randomly turns off, delayed, confusing, causes arguments |
| **Thermostat** | Learns preferences, saves energy | Jumps temps, ignores actual comfort, adds stress when guests visit |
| **Security**   | Proactive, instant alerts        | False alarms, annoying notifications, misses real threats due to complexity |
| **Effort**     | Effortless, saves time           | Constant tweaking, troubleshooting, adds a new mental load |
| **Reliability**| Always works, predictable        | Fragile, dependent on internet, batteries, firmware, sometimes just "stops" |

## What I'd Do Differently

Looking back, here’s how I’d approach automation today, leaning heavily on lessons learned about common sense:

1.  **Prioritize Pain Points, Not Possibilities:** Don't automate just because you *can*. Identify a real, recurring problem that automation can reliably solve.
    *   **Good examples:** Exterior lights on at sunset, a simple motion sensor turning on a utility closet light, door/window sensors for security alerts, scheduled thermostat adjustments (basic, not "learning").
    *   **Bad examples:** Complex multi-room lighting scenes that require precise timing, presence-based routines for critical functions, systems that control comfort based on a "guess."
2.  **Start Small, Iterate, Validate:** Implement one automation, test it rigorously for a week or two. Does it genuinely improve things? Is it robust? Only then consider expanding.
3.  **Manual Override First:** Every single automated function must have an easy, physical, and intuitive manual override. A light switch that always works, a thermostat you can simply dial up or down, blinds you can pull. If the automation fails, or you simply want to do something different, it should be easier to do it manually than to fight the system.
4.  **Embrace Simplicity:** A dedicated smart plug for the Christmas tree lights is brilliant. Trying to link it into a complex holiday "scene" with synchronized music and fireplace effects is probably overkill and a recipe for frustration.
5.  **Local Control Over Cloud Reliance:** Where possible, choose devices and systems that can function locally without constant internet access or cloud services. This dramatically improves reliability and responsiveness.

## Who This Is For / Not For

**This approach to automation is for you if:**

*   You're a tinkerer who genuinely enjoys the process of setting up and refining systems.
*   You have very specific, consistent pain points that automation can reliably address (e.g., mobility challenges, strict schedules).
*   You understand that "smart" doesn't mean "magic," and are prepared for occasional troubleshooting.
*   Your household members are equally invested or are very patient with your experiments.

**This approach is NOT for you if:**

*   You're looking for a "set it and forget it" solution to instantly simplify your life.
*   You get easily frustrated by technology that doesn't work perfectly every time.
*   Your household has dynamic routines, frequent guests, or diverse preferences.
*   You're on a tight budget, as the time and effort investment can quickly outweigh the financial savings.

What I'd recommend instead, for most people, is to focus on robust single-purpose smart devices that solve a clear problem and have strong manual overrides. Think smart plugs for holiday lights, a reliable smart thermostat you can easily adjust from your phone, or a dedicated security camera system. Don't chase the fully integrated, hyper-automated "smart home" dream unless you have a deep interest in the underlying tech itself.

The goal should be convenience, not complexity. Automation, when applied thoughtfully and with a dose of common sense, can genuinely enhance your life. But when you try to automate *everything*, you often just build yourself a digital house of cards, constantly on the verge of collapsing into annoyance. Sometimes, the smartest thing you can do is just flip a switch.

We Automated Everything Except Common Sense

You’re scrolling. You see something. You click. You scroll more. Another notification pops. You switch tabs. Rinse. Repeat. Five minutes later, you’re lost down a rabbit hole, feeling vaguely unsatisfied, and completely unsure how you got there. Sound familiar?

The internet moves at light speed. Your brain? Not so much. This mismatch isn't just an inconvenience; it's a fundamental problem for your focus, your well-being, and your ability to think deeply. It's time to talk about deliberately slowing things down.

### Quick take

*   **The default state of the internet is overwhelming.** It bombards you faster than you can process.
*   **Your brain isn't built for constant, high-speed input.** It needs time to digest.
*   **This leads to shallow attention, decision fatigue, and often, anxiety.** We mistake input for understanding.
*   **The solution isn't necessarily disconnection, but intentional friction.** Make it harder to get distracted.
*   **Tools can help, but mindset is key.** Design your digital environment for focus, not speed.
*   **You reclaim mental space by choosing slowness.** It’s a deliberate act of resistance.

## The Problem: Cognitive Overload, Instant Gratification

We live in a world where speed is synonymous with efficiency. Gigabit internet. Instant search results. Notifications pinging from every app, device, and platform. But this relentless pace, while impressive technologically, often short-circuits our own cognitive processes. We’re drinking from a firehose, then wondering why we’re perpetually thirsty.

### The "Always On" Trap

Think about your typical morning. Before your first coffee, your phone probably offered you a dozen headlines, five work emails, and three social media updates. By 9 AM, you’ve consumed more information than someone a century ago might have in a week. Your brain attempts to keep up, scanning, filtering, reacting. But this constant input stream leaves little room for reflection, synthesis, or genuine insight. We mistake information *access* for information *processing*. The result? A mind that feels busy but rarely feels productive.

### The Cost of Speed

The hidden cost of this warp-speed digital life is profound. I used to find myself opening a browser for one specific task – check a definition, look up an address – and within minutes, be six tabs deep, scrolling through unrelated articles, completely having forgotten my original intention. This isn't just wasted time; it's a constant drain on your mental energy. Each click, each new piece of information, demands a micro-decision. Over a day, these thousands of tiny decisions add up to significant decision fatigue. Our focus becomes fragmented, our attention span shrinks, and the capacity for deep work—the kind that truly moves the needle—evaporates.

## My Setup / Context

To give you some perspective, my work involves a lot of writing, research, and collaborative document editing. I have a fiber internet connection at home (think 500 Mbps download, 200 Mbps upload), so speed is never an issue. My primary devices are a MacBook Pro and an iPhone, both capable of doing essentially anything instantly. I used to operate with every notification on, multiple browser windows open, and the constant urge to "just check" something. My "fast habits" meant I spent more time *managing* information than *using* it. This experience, feeling perpetually behind despite having all the tools, is what pushed me to fundamentally rethink my approach to digital speed.

## Strategies for Deliberate Slowness

This isn't about ditching the internet entirely; it's about reclaiming your brain's pace in a hyper-fast world.

### Building Friction Back In

Sometimes, the best solution is to simply make it harder to fall into the rabbit hole.

1.  **Scheduled "Internet Breaks":** Instead of constant connectivity, block out specific times for "internet work." This includes email, social media, news, and even non-critical research. Outside these windows, the internet is for *output* only (writing, coding, focused work).
2.  **Physical Barriers:** My phone often lives in another room, or at least out of arm's reach while I’m doing focused work on my laptop. Out of sight, out of mind. Even turning it upside down can make a difference.
3.  **App Blockers / Website Filters:** Tools exist that allow you to block distracting websites or apps for set periods. I use one during my writing blocks. It’s not about willpower; it’s about architecting an environment where willpower isn’t constantly tested.
4.  **Analog First:** Before opening a browser for research, I grab a notebook. Outline ideas, jot down questions, map out my thoughts. This pre-computation helps refine what I *actually* need from the internet, making my searches more targeted and less prone to distraction.
5.  **Single-Tasking Rules:** When I'm online for a specific task, only that tab and related documents are open. No side quests. No "just checking Twitter." This takes conscious effort but pays off immensely in focus.

### Choosing Tools Wisely

Not all digital tools are created equal when it comes to fostering focus. Some inherently slow you down (in a good way).

*   **E-readers vs. Tablets:** An e-reader like a Kindle is designed for reading, and little else. A tablet, with its full web browser, app store, and notification capabilities, is a distraction machine masquerading as a productivity tool.
*   **Minimalist Apps:** Seek out apps that do one thing well, without endless features, notifications, or social feeds. Text editors that strip away formatting options, simple note-taking tools, or calendar apps that just show your schedule.
*   **"Dumb" Phones (or Smart Phones Set Dumb):** Many people find relief in using a basic phone for calls and texts, or by stripping their smartphone of all but essential apps, turning off notifications, and using grayscale mode.
*   **Curated Feeds (RSS):** Instead of letting algorithms dictate what you see, use an RSS reader to subscribe only to the blogs and news sources you truly value. You pull information when you want it, rather than it being pushed to you constantly.
*   **Dedicated Devices:** For deep creative work, consider a device specifically for that purpose, ideally with no internet connection at all. An old laptop configured purely for writing, for example.

## Tradeoffs and Who This Is For

Embracing slowness isn't without its challenges.

### The Downside of Disconnecting

*   **Potential for Isolation:** You might miss out on real-time news, social conversations, or urgent updates. There’s a balance to strike between focus and staying informed.
*   **Initial Productivity Hit:** Changing habits is hard. The first few days or weeks of deliberately slowing down can feel frustratingly inefficient as you retrain your brain.
*   **Learning Curve for New Habits:** It takes effort and consistency to establish new routines and resist old temptations. The urge to "just check" is powerful.
*   **Not for Everyone:** Certain roles (e.g., social media managers, emergency responders) require constant, high-speed monitoring. This advice is for those who *can* dictate their digital boundaries.

### Who Benefits Most

This approach is highly beneficial for:

*   **Knowledge Workers & Creatives:** Writers, designers, programmers, researchers – anyone whose job requires deep, sustained concentration.
*   **Students:** To improve learning, retention, and the quality of academic output.
*   **Anyone Feeling Overwhelmed:** If you constantly feel behind, anxious, or like your brain is "full."
*   **Individuals Struggling with Focus:** If you notice your attention span shrinking or find yourself easily distracted from important tasks.

## Comparison: Fast vs. Slow Internet Habits

| Aspect                | Fast Habits (Problem)                                  | Slow Habits (Solution)                                   |
| :-------------------- | :----------------------------------------------------- | :------------------------------------------------------- |
| **Information Consumption** | Endless scrolling, notification-driven                   | Curated feeds, scheduled checks, intentional pull        |
| **Decision Making**   | Impulsive clicks, reactive responses                   | Deliberate choices, reflective thought before action     |
| **Focus**             | Fragmented attention, shallow engagement               | Sustained concentration, deep work blocks                |
| **Tool Use**          | Multi-tasking, all-in-one apps, constant switching     | Single-tasking, specialized tools, dedicated periods     |
| **Mental State**      | Overwhelmed, anxious, perpetually busy                  | Calm, clear, engaged, genuinely productive               |

## What I’d Recommend Instead

Instead of letting the internet pull you along at its frantic pace, push back. Start small. Pick one digital habit you want to slow down this week. Maybe it's checking email only twice a day. Maybe it's leaving your phone outside the bedroom. Instead of letting the algorithm choose your next piece of content, actively seek out what you *intend* to consume. Think of it as a mental diet, where you're mindful of every byte you ingest.

Don't see the internet as a default. See it as a powerful tool to be used with precision and purpose. The goal isn't to be less connected, but to be more intentionally connected, ultimately giving your brain the breathing room it desperately needs to truly thrive.

The Internet Is Faster Than Your Brain (And That’s a Problem)

The internet loves a good trend, and "building in public" is one that’s sticky. Everywhere you look, people are tweeting their daily progress, sharing loom videos of half-baked ideas, and documenting every single decision. It feels like everyone is on stage, shouting about their process.

But here’s the thing: after watching this play out for years, I'm starting to wonder if the show has overshadowed the actual construction. Are we really *building* things, or are we just really good at *talking about building*? Because often, it looks like a lot of performance and very little tangible output.

## Quick take

*   "Building in public" often prioritizes performance over genuine creation.
*   The constant need to share can derail deep work and focus.
*   It creates an illusion of progress without necessarily leading to tangible products.
*   Your "audience" probably cares more about results than daily updates.
*   Authentic transparency is valuable; performative transparency is draining.
*   Sometimes, the best way to build is to simply… build, quietly.

## The Performance Trap

There’s a powerful pull to share every step. It promises community, feedback, and maybe even early customers. But for many, it morphs into something else: a performance. You’re no longer just working; you’re working *for an audience*.

This subtle shift changes everything. You start polishing drafts you’d normally scrap. You explain basic decisions just to fill airtime. The focus moves from "how do I solve this problem?" to "how do I present myself solving this problem?" It's a mental tax on top of your actual work, draining energy better spent elsewhere.

### Why we get sucked in

1.  **Validation:** Instant feedback loops can feel good, like a digital pat on the back.
2.  **Visibility:** Hoping to catch the eye of investors, partners, or future users.
3.  **Accountability (perceived):** Thinking public commitments force you to follow through.
4.  **Community:** The desire to connect with like-minded individuals.

All valid desires, but the "how" matters. If the *how* involves constant, uncritical sharing, the downsides often outweigh the upsides. You spend more time crafting the narrative of your journey than actually taking meaningful steps on that journey. The "building" becomes secondary to the "public."

## What Does "Building" Actually Mean Anymore?

When I hear "build in public," I picture someone literally assembling something piece by piece, inviting people to watch. What I often see is someone talking about *planning* to assemble something, then talking about *finding the pieces*, then talking about *organizing the pieces*, and then… silence, or a pivot to a new "build in public" project.

Real building involves:

*   Deep, uninterrupted focus.
*   Messy, ugly first drafts.
*   Failed experiments nobody ever sees.
*   Long stretches of silent iteration.

These aren't glamorous. They don't make for good social media threads. So what gets shared? The easy stuff. The "I just created a landing page!" or "Look at my new brand colors!" These are components, sure, but not the core *creation*.

## My Setup / Context

I’ve been involved in various "creator economy" adjacent spaces for years, both personally and professionally. I’ve launched tiny projects, worked on bigger initiatives, and watched countless others do the same. I've fallen into the trap myself, believing that consistent public updates would somehow accelerate things.

My experience comes from trying to launch a small software tool, writing a short ebook, and even just trying to learn a new skill like coding. In each case, the urge to "show my work" often coincided with procrastination on the actual work. I’d spend an hour formatting a tweet about my progress instead of spending that hour *making* progress. It was a subtle, insidious form of self-sabotage, masquerading as productivity.

I learned that for me, the crucial stages of deep work and problem-solving required quiet. They required obscurity. When the audience was implied, my brain was split: half on the problem, half on how I'd explain the problem-solving process later. It rarely led to better solutions.

## Who Is This For (and Not For)?

"Building in public" isn't inherently bad. It just has specific use cases where it genuinely shines.

| Good Fit For                               | Less Ideal For                                      |
| :----------------------------------------- | :-------------------------------------------------- |
| Open-source projects (community contribution) | Early-stage product development (rapid iteration)   |
| Learning a *specific* skill (e.g., coding challenge) | Deep creative work (writing a novel, composing music) |
| Transparent company culture (internal processes) | Developing proprietary IP (competitive advantage)    |
| Post-mortem analysis / sharing lessons learned | Initial problem discovery / user research           |

If your core goal is genuinely collaborative, or if the "product" *is* the process (e.g., documenting a complex scientific experiment), then by all means. But for most solopreneurs and small teams trying to bring something new into the world, it's often a distraction.

## What I’d Recommend Instead

Instead of broadcasting every twitch, consider a more strategic, results-oriented approach. Focus on the actual building, then share the *outcomes* and *insights*.

### Build in Silence, Share with Purpose

1.  **Prioritize Deep Work:** Schedule uninterrupted blocks of time where you are simply *creating*. Turn off notifications. Close social media. Don't even *think* about how you'll explain it later. Just do the work.
2.  **Define Milestones:** Instead of daily updates, set clear, internal milestones. A launched feature, a completed chapter, a user-tested prototype. These are actual points of progress.
3.  **Share the "What," Not the "How":** Once you hit a milestone, then you can share. "We launched X!" "Chapter 3 is done!" "Here's what we learned from our first 10 users."
4.  **Offer Post-Mortems, Not Live Streams:** After shipping, reflect. What went well? What went wrong? What would you do differently? *This* kind of sharing is incredibly valuable and honest. It's built on actual experience, not speculation or ongoing performance.
5.  **Curated Transparency:** If you *do* want to build a community, share behind-the-scenes glimpses strategically. A weekly summary, a monthly update, or a specific "lessons learned" thread. Make it additive, not performative.

It’s about understanding the difference between genuine transparency and incessant chatter. One builds trust and provides value; the other often creates noise and slows you down. Your job isn't to entertain with your process; it's to deliver a valuable product or idea. Focus on that, and the rest will follow.

Everyone Is “Building in Public” and Nobody Is Building Anything

https://v.redd.it/hncxtb9o0vmg1/CMAF_1080.mp4

Puppy

Orpheus Descent to Hades by Rostyslav Zagornov

Mia. Done by me with ink and watercolors.

https://v.redd.it/kprbrvhctumg1/CMAF_480.mp4

How many ex NBA players are Jehovah’s Witnesses?

I vacuum sealed my emergency cigarette

https://v.redd.it/80ed1vnx70ng1/CMAF_360.mp4

Award

My parents some months before they married, in 1981.

How Conservatives become Instant Liberals (Don Wright, 2004)

French Renault FT-17 light tank which was captured by the Soviets during the Polish-Bolshevik War in 1920, afterwards donated by the Soviet Union to the Kingdom of Afghanistan – photo shows U.S. soldiers with the tank, c. 2005.

https://www.reddit.com/r/worldnews/comments/1rkmiqs/rworldnews_discussion_thread_us_and_israel_launch/

/r/WorldNews Discussion Thread: US and Israel launch attack on Iran; Iran retaliates (Thread #5)

https://www.reddit.com/r/worldnews/comments/1rklggb/hi_reddit_im_andrew_mills_a_reuters_reporter_on/

Hi Reddit, I’m Andrew Mills, a Reuters reporter on the ground in Qatar covering the Iran war. Ask Me Anything!

White House press secretary Karoline Leavitt on Tuesday denied claims that Secretary of State Marco Rubio said that Israel dragged Trump into war with Iran.

https://foxbaltimore.com/news/nation-world/white-house-denies-rubio-said-that-israel-dragged-trump-into-war-with-iran-karoline-leavitt-middle-east-drones

White House denies Rubio said that Israel dragged Trump into war with Iran

https://www.reddit.com/r/worldnews/comments/1rkbczv/rworldnews_live_thread_russian_invasion_of/

/r/WorldNews Live Thread: Russian Invasion of Ukraine Day 1469, Part 1 (Thread #1616)

https://www.itv.com/news/2026-03-03/united-states-seeking-an-armed-uprising-inside-iran

United States seeking an armed Kurdish uprising inside Iran, with ground operation expected within days

https://www.ynetnews.com/article/1wydcb29l

Tech, News, History, Wallpapers & Anime — NoShitBlog

We Automated Everything Except Common Sense

NEWS >

/r/WorldNews Discussion Thread: US and Israel launch attack on Iran; Iran retaliates (Thread #5)

Hi Reddit, I’m Andrew Mills, a Reuters reporter on the ground in Qatar covering the Iran war. Ask Me Anything!

White House denies Rubio said that Israel dragged Trump into war with Iran

/r/WorldNews Live Thread: Russian Invasion of Ukraine Day 1469, Part 1 (Thread #1616)

United States seeking an armed Kurdish uprising inside Iran, with ground operation expected within days

Trump: Not happy with Spain's position on Iran, we'll cancel all trade ties with it

BLOG >

We Automated Everything Except Common Sense

The Internet Is Faster Than Your Brain (And That’s a Problem)

Everyone Is “Building in Public” and Nobody Is Building Anything

HISTORY >

My parents some months before they married, in 1981.

How Conservatives become Instant Liberals (Don Wright, 2004)

French Renault FT-17 light tank which was captured by the Soviets during the Polish-Bolshevik War in 1920, afterwards donated by the Soviet Union to the Kingdom of Afghanistan – photo shows U.S. soldiers with the tank, c. 2005.

WALLPAPERS >

Neon Moon Over a Silent Shore

West Village warehouse building apartment that opens up to a courtyard garden, Lower Manhattan, New York City

A star’s death - Medusa Nebula

FUNNY >

How many ex NBA players are Jehovah’s Witnesses?

I vacuum sealed my emergency cigarette

Award

ANIME >

Indeed

anime irl

My first edit is probably a year, how did I do?

CREEP >

Puppy

Orpheus Descent to Hades by Rostyslav Zagornov

Mia. Done by me with ink and watercolors.