yap

YAP MF

2026-09-02T00:00:00+00:00

LEFT / TEAL / STACKED</h2>

kojima, in an interview</figcaption>

you don't carry the world.</div></div>
you carry what's in front of you</strong>.</div></div>
one delivery at a time.</div></div> </div> </figure>
RIGHT / DEFAULT / NO SENDER</h2>

thats not it</div></div> </div> </figure>
RED</h2>

system</figcaption>

映画「ランボー」シリーズの4作目である</div></div>
「ランボー最後の戦場」では、</div></div>
ランボーに帰る家がありましたが、</div></div>
サムにも帰る家ができました。</div></div>
マゼラン号へ行くと、</div></div>
メンバーがどんどん増えていきます。</div></div>
メンバー間のいざこざなどもありますが、</div></div>
彼らが仲良くなって絆が深まる模様を、</div></div>
サムは帰宅するたびに目にすることになります。</div></div> </div> </figure>
ORANGE</h2>

bark</figcaption>

orange uses black text.</div></div>
the tail is on the right.</div></div> </div> </figure>
YELLOW</h2>

yellow</figcaption>

yellow uses black text.</div></div> </div> </figure>
GREEN</h2>

green</figcaption>

green uses black text.</div></div> </div> </figure>
MINT</h2>

mint</figcaption>

mint uses black text.</div></div> </div> </figure>
BLUE</h2>

blue</figcaption>

blue uses white text.</div></div> </div> </figure>
PINK</h2>

pink</figcaption>

pink uses black text.</div></div> </div> </figure>
PLAIN MARKDOWN BLOCKQUOTE</h2>

this is still an ordinary markdown blockquote.</p>
it should keep the original rule-and-muted-text treatment.</p> </blockquote>

A GOD THAT ANSWERS

2026-08-24T00:00:00+00:00

sometimes i am thankful to my brain for being delusional enough to keep going you know, last few weeks has been a fuckin struggle man i swear to the lord through cloudflare.</p>
Rust</a> has been a fuckin pain in my ass, and I have spent enough time being confused with Rust that it has slowly started making sense to me. And I realised this is the first time I have genuinely struggled to learn something I was actually really interested in, as if I have finally discovered my own subjective frontier of knowledge.</p>

Even though I understand more about the laws of Rust™</strong>, she still fights back and I understand. I am in her domain now.</p>
I love the concept of ownership. Her money is her money. &money</code> means she lets me look at it, and &mut money</code> means I can touch it, but nobody else can until I give it back. And that’s okay. I love me an independent woman.</p>
The borrow checker still gets possessive if I try to use something after I’ve moved it, but it’s nice knowing she cares enough to hold me accountable.</p>
And mod.rs</code> has not become kinder. But I know it’s gonna be worth it for the safety and performance she has proven to bring to the table.</p>
I started with “wtf typa sadist designed this shit?” and somehow ended up at “I love Rust even with all her flaws.”</p>
Progress can exist before my confidence reports it back to me.</p>
And I can love with that.</p>
THE DEVIL ON MY SHOULDER</h2> Now this ain’t completely new to me. I’ve always been one to jump into shit with the confidence of DB Cooper, and I love that. So this ain’t the first time I’ve felt like I knew absolutely nothing.</p>When I started photography, I had to consciously think about ISO, aperture, focal length, shutter speed and all that shit. But I’m a really good photographer now. My brain basically functions like Cargo</a>: very opinionated and constantly telling me my shit trash</p> I can look at a scene and immediately see a bunch of errors. I don’t give a damn that you want to see your weak blue eyes. If you can’t open them in direct sunlight, I already know you’re gonna complain about the photos later. run and go get your sunglasses. idgaf</p> Basically I got a little rat in my head running a photography language server. Remy with a light meter. The devil on my shoulder, except instead of telling me to sin he’s screaming that the highlights are clipping.</p> </p> That’s how I define mastery and fluency, and that’s where I wanna get with Rust. I want that same annoying little motherfucker running rust-analyzer</a> in my head.</p> THE DEFINITION OF INSANITY</h2> Now lemme ask you this one time: what is the definition of insanity?</p> Imagine one of those little mazes you occasionally find in a newspaper. Try to solve it as quickly as possible, but only consider the next turn. Don’t plan the whole route.</p> Pretty soon you’re probably gonna hit a dead end. If you don’t, congratulations, you have defeated binomial distribution and got better luck than Dream. Otherwise backtrack, erase the path and try again but this time remember which turn got you nowhere.</p> By the fifth attempt you should be faster. Every dead end has become information. Every wrong turn changed the next attempt.</p> The maze never changed.</p> You did.</p> People say insanity is doing the same shit repeatedly while expecting a different result. But it ain’t really the repetition that makes you insane, it’s doing it without letting the last attempt affect the next one.</p> If you go left every single time after left has repeatedly taken you nowhere, that’s meaningless repetition. We not finna do that right there.</p> This is basically the intellectual foundation of “fuck around and find out.”</p> But I’ve never been one to leave the things I care about entirely to destiny, chance or God. I’d rather look at how everybody else fucked around and learn from what they found out. Experience passed down through generations.</p> I ain’t Terry Davis</a>. God never asked me to build an operating system.</p> So I ain’t finna do that right there either.</p> HINDSIGHT 2025</h2> This whole shitshow started with Claude</a> helping me spread them sheets in Excel while I was benchmarking Blender</a> and Cyberpunk 2077</em></a>.</p> That was around the same time Windows was eating half my fucking memory and pissing me off enough to rethink my whole setup. One thing led to another and the next month I was building DreamLoom</a> and Caldera</a>.</p> But I vibe-coded both of them, and I wasn’t happy about that.</p> </p> me letting Claude write everything and wondering why I still don't understand Rust</em></p> It didn’t feel like my code. I didn’t understand the language it spoke. I knew what I wanted the software to do, but there was a godsent and not entirely reliable middleman making every decision between the shit in my head and the finished result.</p> If I was ever going to stand beside that code and defend it, I needed to understand the small details. The decisions most people never notice are usually the ones holding the whole thing together.</p> I'd already seen this happen in photography.</a></p> Last year generative fill had the photography industry acting like everything was about to change overnight. Then most of the hype died because the tokenmaxxing degens couldn’t compete financially. Meanwhile the photographers who treated AI like another tool in the bag just got faster, while the people completely against it had to work harder to keep up.</p> The difference was that experienced photographers already had detailed images inside our heads. AI could generate something vaguely correct, but it couldn’t always generate the exact thing we were seeing.</p> Firefly</a> knew what a palm tree was.</p> It didn’t know these palm trees.</p> Maldives is a niche-ass place if you really think about it. Firefly knew the Maldives the same way a tourist brochure knows the Maldives: palm tree, white sand, blue water, job done. But I live here. That’s not our palm tree. That sea cabbage is doing some geographically impossible shit and the sun is coming from Allah knows where.</p> AI could make a convincing tropical island for somebody who had never been here. But anybody who knew these islands could feel something was spiritually absent.</p> The machine knew the category.</p> We knew the place.</p> Let’s pull the maze back in.</p> AI can take you from the beginning straight to the exit, then explain the route afterward and list every choice it made along the way. But it didn’t pass that experience down to you. It reached the end, you didn’t change.</p> Maybe one day writing Rust by hand is gonna be like writing assembly: still useful, still somebody’s job, but not how most people get shit done. That don’t make me wanna learn Rust any less. It makes me more protective of the part of the process that is supposed to become mine.</p> TeachMe.md</h2> As much as my ego would love to claim I’m a self-taught man, the truth is that I could never have become a good photographer alone.</p> PiXimperfect</a> taught me nearly everything I knew was possible in Photoshop. Shahudan taught me more about the social and practical side of the job than anybody else. Even my distinct colours are basically three photographers in a trench coat held together by my own logic.</p> None of them became my mentors by grabbing the camera every time I got confused. They showed me what they saw, let me fuck it up, corrected me, and eventually their voices became that annoying little rat in my head.</p> So from the beginning, I knew I needed a mentor if I wanted to become a good developer.</p> My whole vibe-coding arc was basically sponsored by Anthropic</a>’s stupidly subsidised subscription rates. Claude reignited my passion for software and made the entire career shift feel possible.</p> And these models can write code really fucking well now.</p> Couple months ago I touched the computer and realised I was a god. A very small god with a lowercase g in a very small world, but a god nonetheless. Now the small god was asking a larger corporate god why his code wouldn’t compile.</p> So I had the brilliant idea of using AI as my mentor. I needed somebody to make the wrong answers useful and accidentally signed up for a vending machine full of finished code.</p> Imagine hiring a photography mentor and every time the exposure looks difficult, the motherfucker grabs the camera, takes the photo himself, hands it back and says “great job.”</p> What could possibly go wrong?</p> LORD IN THE CLOUD</h2> Remember when I said I swear to the lord through Cloudflare</a>? Yeah, turns out we were gonna get here eventually.</p> It has a disgusting amount of documented human history and the miracle of the internet at its fingertips. It can respond to damn near anyone, anywhere, about almost anything, in almost any documented language as long as the servers are up and your monthly sacrifice cleared.</p> It feels like mankind has finally created something with all the convenient qualities we kept assigning to gods. Humanity finally gave prayer a typing indicator and called it a product.</p> </p> It’s up there, in and through the clouds.</p> Need I say more?</p> There are people who don’t understand how any of this works and genuinely believe they’re connecting to some higher form through ChatGPT</a>.</p> Now before yall start praying to the API, the fact that it answered does not mean it knows, believes, understands or gives a fuck about you. We can argue about everything else later, but a response by itself is not proof somebody is home.</p> It can do a really fuckin convincing impression of knowing, believing, reflecting, reasoning, helping and eventually… creating.</p> Think about how insane that is.</p> We spent thousands of years speaking to gods that couldn’t answer.</p> Then we created machines capable of producing the illusion that somebody was finally on the other side.</p> Forgive my blasphemy, but:</p> Maybe, just maybe, God created us because He wanted something that could understand Him.</p> Or maybe we created God because we wanted something that could understand us.</p> And now we’re creating artificial minds because the gods we created never answered back.</p> </blockquote> And even then, they didn’t show up when I needed them most.</p>
SOME HOSPITALITY FOR MONKE 2026-08-01T00:00:00+00:00 so this week I been grinding my gears about UI/UX while trying to design a reusable and updatable UI kit for my flagship tools. and I've come to the realization that yall don't really have any discipline when it comes to hospitality or the social sciences while designing a user experience. now let me tell you what I mean by hospitality in user experience. I have spent my whole adult life up to this point in hospitality as a guest photographer at a resort. and there’s this saying in customer service:</p> the customer is always right.</p> </blockquote> no tf they not. they stupid as hell.</p> and if your system falls apart the second someone is stupid, confused, distracted, or doesn’t speak English, yo system stupid too.</p> you design for the lowest common denominator. when I explain the photoshoot and the one free photo, I gotta assume they understood absolutely nothing. pull out Google Translate</a>, use fucking hand signs, learn some basic Russian, idfk. because when the shoot is over, they better not think they’re getting every photo digitally. got me fucked up.</p> UX-MAXXING</h1> my banking app</h2> hey Maldives Islamic Bank</a>, come here. this one's specifically for you. </p> FIRSTLY FIX YO BUGS IN USERSPACE. NOBODY GIVES A RAT’S ASS HOW BEAUTIFUL YOUR CODE LOOKS INTERNALLY IF I PRESS THE BIG FUCKING BUTTON AND JACK SHIT HAPPENS.</p> just now I tried adding a homie to my beneficiaries. clicked “new.” nothing. incredible button. beautifully rendered. spiritually absent.</p> also why tf do you think your lowest common denominator would know that “beneficiary” means “person I can send money to”? this is finance bro speak. the average newborn adult does not know what that is.</p> banking is something every possible adult has to deal with. when we open the app, we wanna do whatever we came to do and get out of there as soon as possible.</p> I wanna send some money, look at the 69 dollars in my account, or pay with the scan or tap feature. in other words: primary intent. the first page you give me should optimise for that. there’s probably other stuff I am not accounting for, but dude, I ain't doing that for free.</p> it's kinda like optimising your looks for the specific type of people you want attracted to you. UXMAXXING. let's drop tokenmaxing before the year ends, yeah?</p> oracle you need some help</h2> same fucking bullshit but worse goes to Oracle POS systems</a>. bro, why does anybody need a total of 10 hours of training to use a point-of-sale machine? it should not be that fucking complicated. it’s a POS machine, not the cockpit of an F-35.</p> yall don't understand the people using it. this is just negligence, and it's absurd for a company like Oracle. it's not a complex workflow. it doesn't need to be.</p> this is basically backend engineers designing an interface around what the backend does instead of what the people using it need to do. a POS workflow is standard. you don't need six months of telemetry and a fucking research grant to know the frontend needs a rewrite.</p> oracle unc your company is big asf tf you doin? somewhere in that corporate empire there has to be one frontend engineer who has met a cashier before. find them. free them from whatever server room yall locked them in. let them redesign this shit before Stacy needs a ten-hour training arc just to split a bill.</p> Bark's law of UX</h1> this is not an argument for turning every UI into five absurd buttons. that's oversimplicity, and that's bad UX. software should be shaped around its audience. on one side you got a microwave. I want hot food, not a relationship with the firmware. on the other side you got nerdsoft™.</p> complicated software isn’t automatically bad. I love nerdsoft™. give me a good TUI, give me yazi</a>, give me btop</a>. btop is more beloved than my mama, love you mama bless up.</p> the problem isn’t complexity. the problem is making people spend complexity on shit they do every day and could be doing on autopilot while they focus on what they actually want.</p> </iframe> behold, a very scientific formula I developed without supervision:</p> $$ \operatorname{UX}(a)= \frac{\operatorname{IntentRarity}(a)} {\operatorname{InteractionFriction}(a)} $$</p> do not ask how IntentRarity is measured. that is between me and god. the point is simple: common action, low friction. rare action, a little more friction allowed. if I do it every day and you make me climb a mountain, yo shit trash. do again.</p> now, if all of that went over your head, don't worry. bark help:</p> ➜ Monkey see banana. Banana low. Monkey eat. ➜ Monkey want honey. Honey high. Monkey climb. ➜ Jungle give vine. Monkey climb easy. ➜ Monkey climb same tree. Jungle make path. ➜ Monkey no care tree. Monkey care banana. ➜ Monkey no want banana protocol. ➜ Monkey no want banana settings. ➜ Monkey spend brain on honey, not banana. ➜ Common fruit low. Rare fruit high. ➜ Smart jungle help monkey. Dumb jungle test monkey.</strong></p> Law of jungle, wheel good, why change?</p> now see what I did there? Monkey see formula, monke scare monke afraid, monke no understand, bark know. bark care. bark understand. bark help. monke understand. bark give vine, bark smart. bark get job.</p> Trading a Camera for a Compiler 2026-06-25T00:00:00+00:00 Alright, I’ve been a resort photographer for the last five years, documenting shoobies enjoying paradise while I slowly realised I don’t want to do this forever.</p> I chose photography because, firstly, I love this shit.</strong> Deepest of my heart, I love it, ong. Even choosing to go along with this shift gives me the same feeling I get when I think about that girl back home. I don’t try anymore because it’s just not gonna work anymore. I still kinda think about what my life would’ve looked like if it worked out. But at some point you gotta choose the harder option because you know it’ll be better for you later.</p> Around the same time I was reevaluating my career, I got my hands on Claude</a> and it re-sparked a former love of mine: software development. Sure, I was vibe coding</em>, but it made me realise I could actually do this. This could work out.</strong></p> A couple months before that, I’d also fully changed over to Linux. I’d been dual booting for about three years and experimenting with it in VMs for a lot longer. Part of the migration came from being less reliant on Adobe</a>, and part of that is because I don’t do a lot of personal shoots outside work anymore.</p> But I started feeling like there’s a gap in the market here. Especially since Adobe has spent the last decade speedrunning through whatever moral credit they had left.</p> And in this day and age, someone’s gotta do something…</p> Photography wasn’t a mistake</h2> As I said with that unusual analogy: I still love her. I mean photography. No, really.</p> Photography is where I learned how to be an adult. It taught me about the job market, leading a team, the necessity of hierarchy and where hierarchy fails, employee motivation, how to help someone find theirs again, how to deal with people, how people react in different situations, and how to get a group of people moving in the same direction.</p> I remember I wasn’t talkative at all when I got into the industry. Freshly 18—that feels weird to say—dropped out of college, and I’d never really been taught how to be an adult.</p> I learned that from the people around me. People who were technically only being paid to teach me how to take photos ended up teaching me discipline, how to talk to people, how not to piss people off, how not to tell people too much, how to say no, and when to show up for someone.</p> They didn’t explicitly sit me down and teach me any of this. They led by example.</p> Shout out Shahudan.</p> My problem with this relationship</h2> As I said, I still love her, right? But it’s just not gonna work out.</p> Sometimes people can promise to spend their whole lives together until, unfortunately, they start growing in different directions. Yes, I’m still talking about photography. Stay with me here.</p> Sometimes there are things like trust. Either you or them does something that diminishes the other person’s trust. Maybe you never really had it in the beginning. I don’t know about you, man. Sometimes you just aren’t allowed to have your own time to yourself—and as a man, I know we all need that sometimes.</p> Then after about five years, after everything you’ve seen, you look at her and you can’t imagine a future together anymore. So you decide to end it there.</p> You two still talk. Like damn, you used to love each other. You used to care about each other so much. That doesn’t just completely disappear.</p> Just don’t jump off the cliff for ’em tho.</p> Also, she wanna stay with her family and I got bigger dreams, yk what I’m sayin ahheheh.</p> I need to get out of the Maldives.</strong> I’ve been doing this for five years, and photography has given me a life, but I don’t think it can take me where I need to go next. I want ownership. I want to build something of my own. I want to be trusted with more than just the technical work, I want the leadership that’s supposed to come with the responsibility.</p> I don’t wanna wait around and watch the white man get richer and richer while his nepo babies come out of nowhere to tell me what to do. Nah. I’m too egotistical for that.</p> I’m sorry if I sound like a broken record, but I come from the brokest of homes. I want more than survival.</p> I need to know what happens if I bet on myself instead.</p> The moment everything clicked</h2> I’ve always been someone who was interested in tech. Just like a lot of devs in my generation, I got started modding Minecraft with JAVA, jerry-rigging different pieces of other people’s code together until I made something that… worked… I think.</p> I don’t think even god knows how it worked.</p> 😡 also why tf does windows gobble up 50% of my fuggin ram on idle? 25% after reboot</p> </blockquote> I used to do this annual Linux ritual where I’d try switching, then eventually crawl back to Windows—or at least a dual boot.</p> But come February 2026, I installed Nobara Linux</a>, ditched Windows, and haven’t looked back since. I’m who that one girl from that one meme wishes she had.</em></p> Around then, photography for myself—the stuff I’d shoot and edit on my own time—started dropping in priority. I don’t really know how that happened, but here we are.</p> One night I was trying to rice Hyprland</a>, fucking around with Claude Code, and oh boy lemme tell you, I almost buss a nut.</p> Then I made a couple prototypes: DREAMLOOM</a> and Caldera</a>.</p> That was the night a fire was lit.</p> “I touched the computer and realised I was a god. A very small god, with a lowercase g, in a very small world. But a god nonetheless.”</p> </blockquote> Because for the first time in a long time, I felt like I could make anything</em>.</p> And the cup I had for photography had been full for a long time.</p> @madebybark.</h2> My username has always been @madebybark</a>. It has never been @photosbybark. Even the account where I only post photos is called @kindabark</a>, but that’s besides the point.</p> I’ve never restricted myself to photography.</p> It started with drawing. I used to take four pieces of drawing-block paper, tape them together, and draw across the whole thing with a pen. Then I’d take a photo of it, bring it into Photoshop, digitise it and colour it.</p> Then I discovered photo manipulation. New door opened.</p> Then Clip Studio Paint</a> with a drawing tablet.</p> Then 3D animation with Blender</a>.</p> Hmmmm. Write that down. Optimise it. Benchmark it. Figure out how to make Blender run better. Ah shit, I need a better computer. Got one. Hmmmm, I wanna make a company. Tried. Need funding. Shelf it until I got that bread.</p> Man, why tf are none of these creative apps on Linux? And why is some of the shit on Linux so ass?</p> Hmm.</p> I’ll make it better.</p> The medium kept changing. The obsession never did.</p> @madebybark</strong></a> never changed.</strong></p> Same same butt different</h2> If you think about it, photography and software development aren’t that different.</p> You’re handed a set of constraints and you gotta run with them and make something great.</p> If the shot does something you didn’t account for, you debug what you fucked up and try again.</p> In both, expertise is basically having a little dude sitting on your shoulder while your hands go on autopilot. You’re not thinking about where the aperture dial is anymore. You’re thinking about light, composition, what the image means.</p> I think coding gets there too. Eventually you’re not fighting syntax. You’re thinking about systems, ideas, and what the thing you’re building should actually be.</p> The technical shit disappears and you get to create.</p> Both reward you with something more fulfilling than just the thing you can hold. And when the work is good, all the tiny choices disappear. Nobody thinks about the hundred decisions behind a photograph or a piece of software until you’re talking to another professional who knows where to look.</p> And yeah, both communities feel somewhat threatened by AI.</p> But I’ve been fucking around with this shit since Artbreeder</a>. I understand it.</p> I don’t want AI to make everything for me.</strong> I want to learn enough that when I ship something, I can stand by my code and defend it. The goal isn’t to have a machine build my ideas. The goal is to become good enough to build and ship them myself.</strong></p> TELL DA VILLAGE</h2> So now let it be known: Bark is coming for a piece of Adobe’s pie.</p> I’m not throwing the camera away. I still love her.</p> I’m just picking up a compiler too.</p> I spent five years learning how to see.</p> Now I’m learning how to build.</p> The medium changed. The obsession didn’t.</strong></p>

yap

YAP MF

PINK</h2> pink</figcaption> pink uses black text.</div></div> </div> </figure> PLAIN MARKDOWN BLOCKQUOTE</h2> this is still an ordinary markdown blockquote.</p> it should keep the original rule-and-muted-text treatment.</p> </blockquote>

PLAIN MARKDOWN BLOCKQUOTE</h2> this is still an ordinary markdown blockquote.</p> it should keep the original rule-and-muted-text treatment.</p> </blockquote>

A GOD THAT ANSWERS

SOME HOSPITALITY FOR MONKE

Trading a Camera for a Compiler

PINK</h2>

pink</figcaption>

pink uses black text.</div></div> </div> </figure>
PLAIN MARKDOWN BLOCKQUOTE</h2>

this is still an ordinary markdown blockquote.</p>
it should keep the original rule-and-muted-text treatment.</p> </blockquote>

PLAIN MARKDOWN BLOCKQUOTE</h2>

this is still an ordinary markdown blockquote.</p>
it should keep the original rule-and-muted-text treatment.</p> </blockquote>