Nagi takes a seat

Anime_Irl

Horny Jail

You know the drill. "Just ship it." The mantra echoes in stand-ups, in Slack, in your own head. It feels good, right? Fast, agile, getting things done.

But sometimes, "just shipping it" isn't brave. It's reckless. It’s a shortcut that piles up debt, burns out teams, and ultimately, hurts the very product you’re trying to build. We need to talk about the dark side.

## Quick Take

*   "Just ship it" often means "ship it broken, fix it later."
*   This culture prioritizes speed over sustainability, short-term over long-term.
*   It creates immense technical debt that cripples future development.
*   Team morale and quality plummet, leading to burnout and churn.
*   Users notice. Trust erodes, leading to negative reviews and churn.
*   The initial "win" of speed is quickly overshadowed by ongoing maintenance pain.
*   It's not about *never* moving fast, but *when* and *how* you choose to.

## The Siren Song of Speed

There's a reason "just ship it" gained traction. In a world demanding constant innovation and rapid iteration, the idea of quickly pushing features to users for feedback holds undeniable appeal. It promises market validation, agile pivots, and a competitive edge. And for truly nascent MVPs, or pure experiments with no long-term commitment, it can absolutely be the right move. Get it out, learn, move on.

But this philosophy, when applied universally, starts to rot from the inside. The lines between a "rough MVP" and "critical production system" blur. The temporary workaround becomes the permanent solution. The quick fix becomes the foundation for the next quick fix.

## The Hidden Costs of Constant Rushing

When "just ship it" becomes the default, not the exception, the product and the people building it pay a hefty price.

### Mounting Technical Debt

This is the most obvious, yet most frequently ignored, consequence. Every skipped test, every hacked-together integration, every piece of uncommented spaghetti code is a debt accrued. And like financial debt, it compounds.

Symptoms of unmanaged technical debt:

1.  **Slower Development Cycles:** What used to take a day now takes a week because you’re constantly navigating a minefield of fragile code.
2.  **Increased Bug Count:** New features break old ones. Patches introduce new vulnerabilities. QA becomes a nightmare.
3.  **Developer Frustration:** Engineers spend more time firefighting and less time innovating. Morale plummets.
4.  **On-Call Burden:** The product is constantly breaking, leading to frequent late-night alerts and exhausted teams.
5.  **Resistance to Change:** Major refactors become impossible, making it harder to adopt new technologies or pivot.
6.  **Knowledge Silos:** No one truly understands how critical parts of the system work because they were rushed and undocumented.

### Eroding Quality and User Trust

Users aren't stupid. They notice when your app is buggy, slow, or inconsistent. "Just shipping it" often means features are half-baked, performance isn't optimized, and the user experience is an afterthought. This isn't just annoying; it erodes trust.

You might get a quick bump from a new feature announcement, but if that feature crashes regularly or has critical flaws, the goodwill is gone. Users churn. Word-of-mouth turns negative. Your reputation takes a hit that's far harder to recover from than the initial time saved.

### Burnout and Morale Collapse

Teams under constant pressure to "just ship it" are always in crisis mode. There's no time for thoughtful design, proper testing, or even a good night's sleep. Developers feel like code monkeys, not craftsmen. Product managers are always chasing the next deliverable, never truly polishing the current one.

This relentless pace leads to:

*   **High Turnover:** Good engineers, designers, and PMs leave for environments where they can do quality work.
*   **Apathy:** People stop caring about the quality of their output because they know it'll be rushed out anyway.
*   **Poor Innovation:** Without space to think, learn, and experiment, true innovation stagnates.

## My Setup / Context

I’ve seen this play out in various roles – from a mid-size SaaS company scaling rapidly, to a series of product-focused startups. In one instance, a company I worked for was obsessed with weekly feature releases. Every Monday, something new had to go out. The initial excitement quickly turned into dread. We were constantly patching, hotfixing, and apologizing to users. The "next big thing" was always built on the shakiest foundation, leading to a perpetual state of emergency. My role was primarily in engineering management, so I was constantly balancing the demands from product/sales with the realistic capabilities and stress levels of my team. We shipped a *lot* of features, but the underlying system became a complex, fragile mess that eventually required a full re-architecture – costing far more time and money than if we'd built it right the first time.

## Who This Is For (and Not For)

It's crucial to understand that "just ship it" isn't inherently evil, but its application needs careful thought.

**This advice is for:**

*   Teams working on established products where stability, performance, and user trust are paramount.
*   Projects requiring high reliability, such as financial tools, healthcare apps, or critical infrastructure.
*   Companies that understand the long-term value of a maintainable codebase and a sustainable team culture.
*   Anyone struggling with high bug counts, developer burnout, or constant hotfixes.

**This advice might *not* be for:**

*   Early-stage startups building a genuine Minimum Viable Product (MVP) to test a core hypothesis, where the goal is to validate *if* anyone cares, not to build a robust system.
*   Pure R&D projects or internal experiments where the output is expected to be disposable.
*   Situations where the cost of delay *truly* outweighs the cost of quality, and a rapid, temporary solution is genuinely necessary (e.g., a critical security patch with an immediate threat).

## What I'd Recommend Instead

Moving beyond "just ship it" doesn't mean moving slow. It means moving with *intent*.

### Deliberate Delivery

Instead of mindless rushing, adopt a philosophy of deliberate delivery. This means:

*   **Defining "Done":** What truly constitutes a shippable feature? Does it include tests? Documentation? Performance checks? User acceptance? Make this explicit and non-negotiable.
*   **Strategic Pauses:** Build in time for critical maintenance. This isn't wasted time; it's an investment.
    *   Dedicated "fix-it" sprints or days.
    *   Time for thoughtful code reviews and pairing.
    *   Regular refactoring sessions.
    *   Time for proper exploratory testing beyond basic unit tests.
*   **Automated Quality Gates:** Use CI/CD pipelines to enforce code quality, test coverage, and deployment readiness *before* anything hits production.
*   **Empowerment:** Trust your engineers to say "this isn't ready." They are the experts on the technical health of the product. Give them the autonomy and support to build things properly.
*   **Trade-off Transparency:** When speed is truly critical, make the *cost* of that speed explicit. Document the technical debt being taken on, and create a plan for paying it back. Don't just ignore it.

Here’s a simplified comparison:

| Feature           | "Just Ship It" Culture                  | Deliberate Delivery Culture             |
| :---------------- | :-------------------------------------- | :-------------------------------------- |
| **Primary Goal**  | Speed of release                        | Sustainable value delivery              |
| **Focus**         | New features, visible output            | Quality, maintainability, user experience |
| **Team Morale**   | High stress, burnout, high turnover     | Engaged, ownership, lower burnout       |
| **Product Health**| Fragile, bug-ridden, high tech debt     | Robust, stable, evolving cleanly        |
| **User Impact**   | Initial excitement, quick frustration   | Consistent satisfaction, lasting trust  |
| **"Done" Means**  | Code pushed to main                     | Tested, reviewed, documented, stable    |

Choosing deliberate delivery isn't about becoming slow. It's about choosing to build a robust, sustainable product that teams love working on and users love using, for years to come. It’s an investment in your future, not a race to the bottom.

## Ship Smart, Not Just Fast

The urge to "just ship it" is powerful, especially when you're under pressure. But true agility isn't about cutting corners; it's about making smart, sustainable choices. Don't let short-term gains sabotage your long-term success. Build with intent, respect your team, and your users will thank you for it.

The Dark Side of Just Ship It Culture

We all crave the open road, the blank canvas, the power to do whatever we want, whenever we want. That’s freedom, right? The dream. But then the alarm goes off, the bills land, and suddenly, the "freedom" we imagine comes with a hidden price tag: responsibility. And that’s where most of us hit the brakes.

It’s easy to wish for a life without limits. It's harder to build it. Because real freedom isn’t found by escaping commitments, but by choosing which commitments you’re willing to own completely.

---

## Quick Take

*   **Freedom isn't free.** It demands active ownership.
*   **Responsibility is the cost of real autonomy.** You pay in effort, decisions, and consequences.
*   **We chase options, avoid consequences.** This leads to perpetual readiness, never starting.
*   **True freedom involves choosing your burdens.** It's about selective constraints, not zero constraints.
*   **Without ownership, you're always a passenger.** Someone else is steering your life.
*   **This isn't about giving up dreams.** It's about owning the messy, hard path to achieve them.
*   **Stop waiting for permission.** Start taking responsibility for your decisions and their outcomes.

---

## The Illusion of 'Free' Freedom

The internet feeds us a steady diet of "digital nomad" dreams and "passive income" fantasies. Images of laptops on beaches, mornings spent hiking, afternoons earning. It looks like freedom without effort. It feels achievable, just… out of reach.

But what happens when you peel back the layers? The digital nomad hustled for years to build their portable business. The passive income stream required intense, active work upfront. The freedom wasn't given; it was *earned* through a mountain of unsexy, consistent responsibility.

### The Endless Option Paralysis

We get stuck wanting to keep all our options open. We research endlessly, plan meticulously, but never commit. Why? Because commitment closes doors. It means choosing one path and letting go of others. And that means taking responsibility for the path you choose, including its potential failures.

*   Want to start a business? You want the flexible hours, but not the 14-hour days or financial insecurity.
*   Want to move to a new city? You want the fresh start, but not the hassle of finding a new community or the fear of loneliness.
*   Want to change careers? You want the exciting new field, but not the temporary pay cut or the learning curve.

The desire for ultimate freedom, unbound by any specific choice, ironically leads to inaction. You become paralyzed by the sheer volume of "what if" scenarios, never actually *doing* anything.

---

## The Weight of Real Autonomy

True autonomy isn't about a lack of rules; it's about making your own rules and holding yourself accountable to them. It's heavy. It’s scary. And it’s the only way to build a life that’s truly your own.

### What Responsibility Really Means

It's not just paying your bills on time or remembering to buy milk. Responsibility, in the context of freedom, means:

*   **Owning your decisions, good and bad.** No blaming external factors when things go sideways.
*   **Following through on commitments, even when motivation wanes.** Especially then.
*   **Anticipating consequences and planning for them.** The proactive, not reactive, approach.
*   **Being the source of solutions, not just problems.** Identifying challenges and then finding a way forward.

Imagine being the captain of a ship. You have the freedom to chart your own course. But you’re also responsible for the crew, the cargo, the weather, and the destination. You don't get to blame the ocean if you run aground. That's real autonomy. It's immense power, coupled with immense accountability.

---

## The Trade-Offs You're Not Seeing

We often frame freedom as the opposite of being tied down. But what if it's about choosing *which* ropes you want to tie yourself with, and for what purpose?

| Freedom Without Responsibility         | Freedom *With* Responsibility                                 |
| :------------------------------------- | :------------------------------------------------------------ |
| **Feeling:** Untethered, uncommitted   | **Feeling:** Focused, purposeful                              |
| **Focus:** Keeping options open        | **Focus:** Committing to chosen paths                         |
| **Outcome:** Inaction, constant seeking | **Outcome:** Progress, specific results                       |
| **Energy:** Dispersed, reactive        | **Energy:** Directed, proactive                               |
| **Risk:** Regret of missed opportunities | **Risk:** Failure on a chosen path (with learned lessons) |
| **Who's in control?** Circumstance    | **Who's in control?** You (within chosen limits)             |

This table isn't about saying one is inherently "better" for everyone. It's about understanding the actual results of each approach. If you want specific outcomes, you need to lean into the right column.

---

## Choosing Your Chains (and Loving Them)

The key to unlocking more freedom isn't to shed all responsibility, but to actively choose which responsibilities serve your highest goals. These aren't chains; they're the very scaffolding of your desired life.

Here's how to embrace responsibility for more freedom:

1.  **Identify what freedom *actually* means to you.** Get specific. Is it working from anywhere? Having financial independence? Running your own schedule? Don't just say "freedom." Say "freedom to travel for 3 months a year."
2.  **List the responsibilities directly tied to that freedom.** If you want to travel for 3 months, you need financial savings, a remote-friendly job, or a business that runs without you. You need to handle logistics, potential visa issues, unforeseen expenses. What are the gritty details?
3.  **Pick ONE responsibility to actively take on this week/month.** Don't try to solve everything at once. If you need financial savings, maybe this week's responsibility is setting up an automatic transfer to a savings account, or tracking every expense.
4.  **Track the discomfort and the small wins.** Acknowledge when it feels hard. Note when you push through. Celebrate the tiny progress. That positive reinforcement is crucial.
5.  **Adjust and repeat.** This isn't a one-and-done deal. Life changes. Your goals might shift. Continually assess your responsibilities and realign them with your evolving vision of freedom.

### Common Excuses for Avoiding Responsibility (and why they’re BS)

These are stories we tell ourselves to stay comfortable in inaction.

*   **"I don't have enough time."** This almost always means "it's not a high enough priority right now." We make time for what truly matters. Re-evaluate your priorities, then create time.
*   **"I'm not ready/experienced enough."** The mythical "ready" state doesn't exist. You get ready by doing. Every expert started as a beginner who took responsibility for learning and trying.
*   **"Someone else should do it/It's not my job."** This externalizes your agency. If you want the outcome, you might have to take the lead, even if it "should" be someone else's responsibility. Sometimes, leading means doing.
*   **"What if I fail?"** Failure is inevitable. It’s not a final judgment; it’s feedback. The responsibility isn't to *never* fail, but to learn from it and adjust.

---

## My Setup / Context

I used to chase the idea of "passive income" hard. I imagined waking up, checking my bank account, and seeing money just *there*. No work, just freedom. So I tried various schemes: dropshipping, affiliate marketing, even a failed app idea. Each time, I'd get excited about the *idea* of the income, but dread the actual work: writing product descriptions, handling customer service, debugging code, consistent content creation.

I wanted the freedom of the outcome without the responsibility of the process. I was stuck in a cycle of starting, getting overwhelmed, then quitting, feeling like a failure.

What shifted for me was realizing that the people achieving that "passive" income were *deeply* responsible for building the foundation. They put in thousands of hours upfront. They didn't avoid the grind; they embraced it.

My turnaround came when I stopped chasing "no work" and started chasing "meaningful work." I decided to take full responsibility for my creative output. I committed to a consistent writing schedule for my blog, even when views were low. I took ownership of every word, every promotion, every interaction.

*   **Consistency is the ultimate responsibility.** Showing up, day after day, even when it's hard.
*   **Decision fatigue is real, so pre-commit.** Decide upfront what you'll do, then just execute.
*   **Failure is a data point, not a personal attack.** My blog posts sometimes flop. I learn, adjust, and write the next one.

---

## What I’d Recommend Instead

If you feel stuck, wanting more freedom but struggling to find it, try this:

*   **Don't chase "freedom *from*." Chase "freedom *to*."** Instead of "freedom from my boss," think "freedom to set my own schedule." This subtle shift changes your focus from escaping to creating.
*   **Start small.** Identify just one area where you feel constrained. Then, pinpoint the single biggest responsibility you're avoiding that, if tackled, would loosen that constraint. Commit to that one thing.
*   **Find an accountability partner.** Not someone who just cheers you on, but someone who will honestly ask, "Did you do what you said you would?" and help you troubleshoot when you didn't. This external pressure can be a great motivator when internal motivation wanes.
*   **Read broadly about ownership and agency.** Explore Stoic philosophy, or books on habit formation and decision-making. These aren't about specific tactics but about fundamental mindsets that help you embrace your power and your role in your own life.

This path isn't for everyone. If you truly thrive in a highly structured environment where big-picture responsibilities are owned by others, and you prefer to execute defined tasks, that's perfectly valid. There's no shame in knowing your preferences. But if you genuinely yearn for more autonomy, if you feel a restless desire to steer your own ship, then it’s time to pick up the rudder and embrace the beautiful, difficult weight of responsibility.

---

Real freedom isn't given; it's forged. It's the conscious act of choosing your constraints, owning your decisions, and showing up for the messy, unglamorous work required. It's heavy, yes, but it’s a weight you get to choose. And in that choice, there is profound liberation. Start small, pick one thing, and own it completely. You might just find the freedom you've been chasing.

Everyone Wants Freedom, Nobody Wants Responsibility

Most founders don't fail. They just stop. One day, the energy isn't there, the money's tight, the vision's blurry. Instead of a dramatic collapse, there's a slow fade, an unannounced retreat from the arena.

This isn't a post about shaming anyone. It's about honesty. Because when we call every stopped venture a "failure," we miss the real, more common story: the quiet quit. And understanding that distinction changes everything about how you approach your own path.

## Quick Take

*   "Failure" is often a misnomer; "quitting" is a choice, often silent.
*   Founders frequently exhaust their internal resources (belief, energy, patience) before external ones (money).
*   The fear of "failing" can paradoxically lead to quitting sooner rather than adapting.
*   Redefine success on your own terms, not external VC-driven narratives.
*   Burnout is a primary driver for stepping away, not always a flawed business model.
*   Building in public can offer accountability and support, making quiet exits harder.
*   It's okay to quit *strategically*, but not to fade out from lack of clarity.
*   Your psychological toolkit is as vital as your business plan.

## The Myth of the Grand Failure

We love the narrative of the glorious failure. The bold entrepreneur who crashed and burned, learned hard lessons, and rose like a phoenix. It makes for great keynotes. It romanticizes risk. But it's rarely how it goes down for the majority.

For most, it's not a dramatic implosion. It's a creeping doubt, a dwindling bank account (personal, not just business), and a gradual erosion of belief. The product might be decent, the market might exist, but the founder's tank hits empty. They just... stop showing up. The emails get slower, the updates cease, the website quietly goes offline. No press release, no big lessons shared. Just silence.

This isn't to say businesses don't genuinely fail due to market conditions, poor product-market fit, or competition. They do. But the founder's decision to stop often precedes the true "failure" of the business concept itself. The business might have been salvageable, pivotable, or just in need of more time than the founder was willing or able to give.

## The Quiet Quit: Why It Happens

Why do founders make this silent exit? It’s a mix of factors, usually snowballing until the momentum is completely lost.

*   **Emotional Exhaustion:** Entrepreneurship is a marathon of emotional highs and crushing lows. Constant problem-solving, rejection, and uncertainty drain even the most resilient.
*   **Loss of Belief:** Over time, if traction is slow or non-existent, the conviction that drove the initial effort can evaporate. The "why" gets lost in the daily grind.
*   **Financial Strain (Personal):** Most bootstrapped founders are subsidizing their business with their personal savings, time, and opportunity cost. When this becomes unsustainable, the personal cost outweighs the potential reward.
*   **Isolation:** The founder journey can be incredibly lonely. Lacking a peer group or mentor to share the burden makes it easy to internalize struggles and feel alone in wanting to quit.
*   **Lack of Clear Metrics/Wins:** Without clear milestones or even small victories, it's hard to maintain motivation. If every day feels like pushing a boulder uphill without moving, eventually you stop pushing.
*   **Sunk Cost Fallacy:** Sometimes, founders quit because they've invested so much time and money that the thought of continuing down a failing path becomes too painful to contemplate. It's a desperate escape from perceived waste.

## My Setup / Context

I've been immersed in the startup and small business world for over a decade, mostly on the fringes, sometimes in the thick of it. My own path has included launching a few small-scale projects – think niche e-commerce, content sites, and a micro-SaaS experiment – all bootstrapped, all with minimal teams (often just me). I've advised friends on their ventures, observed countless others from idea to launch to stagnation, and spent years consuming every bit of insight from founders who openly share their journey. I haven't built a billion-dollar company, but I’ve seen the patterns of exhaustion, the silent retreats, and the moments when belief truly dies, up close and personal. My insights come from the trenches of small bets and the observation deck of the wider startup ecosystem, not from a venture-backed ivory tower.

## Redefining "Success" Before You Start

This is crucial. If your definition of success is a multi-million dollar exit or venture capital funding, and you're building a niche content site, you're setting yourself up for a quiet quit.

Before you even launch, define what winning looks like for *you*.

*   Is it covering your living expenses?
*   Is it creating a tool that helps 100 people?
*   Is it learning a new skill set?
*   Is it generating enough passive income for a side hobby?

If your business isn't meeting those personal goals, then re-evaluate, pivot, or *strategically* quit. Don't just fade away because you're chasing someone else's definition of "success."

## What I’d Recommend Instead: Proactive Prevention

If I were to start a new venture today, knowing what I know, I'd implement these strategies to prevent the quiet quit:

1.  **Build a Financial Runway, Personally:** Before day one, have at least 6-12 months of personal living expenses saved. This isn't business capital; it's freedom to think clearly without starvation breathing down your neck.
2.  **Validate, Validate, Validate:** Don't build in a vacuum. Talk to potential customers daily. Sell before you build. Get pre-orders. Real market feedback isn't nice-to-have; it's life support.
3.  **Find Your Tribe (Early):** Actively seek out other founders, mentors, or even just a supportive mastermind group. Sharing frustrations and getting outside perspectives is invaluable. Don't be a lone wolf.
4.  **Define Small, Achievable Milestones:** Break down your grand vision into weekly or monthly wins. Celebrate them. Build momentum. It could be 10 user sign-ups, 5 content pieces published, or getting *one* piece of positive feedback.
5.  **Prioritize Your Mental & Physical Health:** This sounds cliché, but it's foundational. Schedule downtime, exercise, good sleep. Burnout isn't a badge of honor; it's a productivity killer and a quit-inducer.
6.  **Develop a "Review and Pivot" Cadence:** Schedule regular, honest reviews of your progress, metrics, and emotional state. Is this still working? Are we still passionate? What needs to change? Don't wait until you're already gone.

## Quitting vs. Strategic Exit / Pivot

There’s a world of difference between giving up in silence and making a calculated decision to change course.

| Aspect            | Quitting Quietly                               | Strategic Exit / Pivot                                  |
| :---------------- | :--------------------------------------------- | :------------------------------------------------------ |
| **Motivation**    | Exhaustion, lost belief, no clear path forward | Re-evaluation, new market opportunity, resource shift   |
| **Outcome**       | Project ceases, potential regret, lost lessons | New direction, valuable lessons, potential new venture  |
| **Mindset**       | Defeat, giving up, shame                       | Adaptability, learning, forward-thinking, proactive     |
| **Action**        | Stop work, fade away, ghost contacts           | Communicate, analyze, plan next steps, reallocate       |
| **Learning**      | Minimal, often unarticulated                   | Documented, shared, applied to future ventures          |

A strategic exit means you’ve analyzed the situation, understood why it's not working *for you*, and made a conscious decision about your next steps. You might sell assets, open-source code, or even gracefully shut down but extract all the lessons learned.

## Who This Is For / Not For

**This advice is for:**
*   Bootstrapped founders.
*   Solopreneurs or small teams.
*   Anyone feeling the grind and questioning their purpose.
*   Those about to embark on their first venture.
*   Founders who value sustainability and personal well-being over hyper-growth at all costs.

**This advice is likely not for:**
*   Founders with extensive VC funding and large teams (their challenges, while related, have different systemic drivers and safety nets).
*   People solely motivated by external validation or a rapid, high-stakes exit.

The honest truth is, most people don't "fail" their way to entrepreneurial success. They persist, they pivot, they learn, they adapt. Or they just… stop. Be intentional about your journey, and if you choose to stop, do it with purpose, not silence. You owe yourself, and your future ventures, that much.

Most Founders Don’t Fail — They Quit Quietly

Planet Eater by me

Léon Spilliaert - Faun by Moonlight (1910)

"Blackcleave Cliffs" - MtG land art by Dave Kendall

https://v.redd.it/e6bmm6g5ureh1/CMAF_360.mp4

Pheww... That was close! Glad they Ducked...

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

Fantastic ad for heels

https://v.redd.it/60t5xmjhkoeh1/CMAF_720.mp4

The Human Centipede 3 - Final Sequence (2015)

Joe Pesci on a date with Naomi Campbell in 1998.

Steve Ballmer giving a presentation at Microsoft’s 25th anniversary, September 5th 2000

The Failanx. The Economist, COVID, July 24th, 2021.

The US vice president says he thinks some Israeli politicians are trying to detail efforts to end the conflict. 

https://www.bbc.com/news/articles/c1m107yj327o

JD Vance accuses Israel of 'manipulating' US public opinion to prolong Iran war

https://www.reuters.com/legal/litigation/marco-rubio-tells-diplomats-play-down-talk-american-tech-kill-switch-2026-07-22/

Marco Rubio tells diplomats to play down talk of American tech 'kill switch'

TOKYO -- Ruling and opposition party members have taken issue with a post by Japanese Prime Minister Sanae Takaichi about her handling of a heavy work

https://mainichi.jp/english/articles/20260722/p2a/00m/0na/005000c

Japan PM Takaichi's '0-3 hours sleep' post draws criticism across party lines

https://www.middleeasteye.net/news/us-greenlights-saudi-nuclear-enrichment-without-safeguards-report

US greenlights Saudi nuclear enrichment without safeguards: Report

https://www.bbc.co.uk/news/articles/cyvl35z3917o

Zelensky sacks top army commander after days of protests

https://www.cbc.ca/news/politics/council-of-the-federation-meeting-prince-edward-island-9.7270861

Tech, News, History, Wallpapers & Anime — NoShitBlog

The Dark Side of Just Ship It Culture

NEWS >

JD Vance accuses Israel of 'manipulating' US public opinion to prolong Iran war

Marco Rubio tells diplomats to play down talk of American tech 'kill switch'

Japan PM Takaichi's '0-3 hours sleep' post draws criticism across party lines

US greenlights Saudi nuclear enrichment without safeguards: Report

Zelensky sacks top army commander after days of protests

Ford says Canada could 'dismantle the U.S. if we wanted to' as premiers gather in P.E.I.

BLOG >

The Dark Side of Just Ship It Culture

Everyone Wants Freedom, Nobody Wants Responsibility

Most Founders Don’t Fail — They Quit Quietly

HISTORY >

Joe Pesci on a date with Naomi Campbell in 1998.

Steve Ballmer giving a presentation at Microsoft’s 25th anniversary, September 5th 2000

The Failanx. The Economist, COVID, July 24th, 2021.

WALLPAPERS >

Stunning sunset at Mount Adams, Washington

Australian Bush, Art By Me

Miles Johnston - Countercurrent (2021)

FUNNY >

Pheww... That was close! Glad they Ducked...

Fantastic ad for heels

The Human Centipede 3 - Final Sequence (2015)

ANIME >

Nagi takes a seat

Anime_Irl

Horny Jail

CREEP >

Planet Eater by me

Léon Spilliaert - Faun by Moonlight (1910)

"Blackcleave Cliffs" - MtG land art by Dave Kendall