← Back to “would you rather”

Why goat farming is better than IT

A 2020s update to a list that’s been forwarded between sysadmins since the 1990s, with sections for everyone else in tech who has ever been paged at 3 a.m. The original is kept, unedited, at the bottom.

Source: “Found a text file at work titled ‘Why should I…’” on r/sysadmin

The 2020s edition

Cloud bills, COVID, AI at its best and worst, vibe coding, global supply chains, and everything else the original author never had to deal with.

96 reasons

  • There’s no Grafana dashboard for a goat. You still have to watch for upset stomachs, worms and viruses (same as IT), and skipped meals, so it’s really a dashboard you have to stand in.
  • Milking is a cron job that runs twice a day, every day, at the same time. No vacations, no holidays, no maintenance window.
  • There are no ARM goats, and nobody has ever had to recompile a goat for Apple Silicon.
  • “Cattle, not pets” sounds great until you price out replacing a good registered goat.
  • Goats don’t page you. They stand outside your window and scream all night instead, especially the first few nights after weaning.
  • No job posting has ever asked for “5+ years of experience with Goat 3.0,” which came out 18 months ago.
  • There is no LeetCode for goats. Nobody has ever asked you to invert a goat on a whiteboard.
  • No daily commute. Just a four-hour round trip for feed, and a fourteen-hour drive to the next goat show.
  • No IAM role needed to milk a goat. The goat enforces access control itself, by kicking.
  • The bucket leaks or it doesn’t. You’ll never read a news story about how your bucket was publicly accessible.
  • Goats can tell the feed bucket from the medicine bucket at a glance, and they run from the second one.
  • You can give two goats the same name and nothing breaks. It is never DNS with goats.
  • Goats don’t actually eat everything; they’re pickier than you’d think. They will happily shred the org chart, the printed roadmap, and the “Our Values” poster, though.
  • Goats aren’t billed per second of compute. They’re billed per feeding, twice a day, and they’ll eat themselves sick if you remove the rate limit.
  • You will never find out from your cloud bill that someone left a goat running in us-east-1 all weekend.
  • When us-east-1 goes down, your goats keep giving milk, as long as you keep milking them.
  • You never write YAML to describe a goat. You file registration papers, tattoo the farm’s initials in one ear, and clip a tag in the other. It’s basically YAML in ink.
  • Goats run their own leader election. It’s decided by head-butting, and a new node can get kept away from the food until you give it a pen of its own.
  • Nobody has asked you how you’re integrating AI into your goat strategy.
  • No board member has ever wondered whether goats could be replaced by an LLM.
  • Goats don’t hallucinate. If a goat says it’s hungry, it’s hungry.
  • You’ve never had to tell a goat “You are an expert goat. Think step by step.”
  • There’s no GPU shortage in goat farming.
  • No phishing training. A goat would chew the phishing email to shreds, which is more than most users manage.
  • If a goat gets ransomware, you have goat steak. There’s no wallet to pay.
  • No MFA. The goat recognizes you, or it head-butts you.
  • No password rotation every 90 days requiring one capital letter, one number, and one goat emoji.
  • No standups. Goats spend hours a day lying down chewing their cud, and nobody calls that a meeting.
  • Nobody asks how many story points it takes to milk a goat. (It’s 3. It’s always 3.)
  • No retrospectives where everyone agrees “communication could be better.”
  • No Jira. A goat-milking ticket would not survive contact with the goat.
  • No OKRs. Objective: goat. Key result: milk.
  • No “quick sync.” No “let’s take this offline.” Everything on a farm is already offline.
  • Goats don’t message you at 11 p.m. with “hey” and nothing else. They yell “BAAAH” and nothing else, which is about as informative.
  • You’ve never had to tell a goat “you’re on mute.” Goats are never on mute.
  • No camera-on policy. The goats can see you just fine.
  • No subscription fee. Just feed, hay, dewormer, vaccines, vet visits, and registration fees, every month, forever.
  • No forced updates at 2 a.m. Just a doe going into labor at 2 a.m. on a school night.
  • Goats don’t come with terms of service you never read.
  • No telemetry. Goats don’t phone home.
  • Nobody sunsets your goat as part of a strategic realignment. Goats reach end-of-life on their own, with no end-of-support date, no notice, and no migration plan.
  • No layoffs announced by a calendar invite titled “Quick Chat.”
  • Your badge never stops working at 9 a.m. You don’t have a badge. You have a gate.
  • No recruiter messages about a “Goat Ninja Rockstar” role.
  • Your title doesn’t change from Senior Goat Engineer to Goat Engineer II after the reorg.
  • No performance calibration. Your goats don’t stack-rank you. They only stack-rank each other, by head-butting.
  • Goats were not affected by Y2K. They will not be affected by the 2038 problem either.
  • There’s no imposter syndrome. You either have milk in the bucket or you don’t.
  • On-call still exists. When a doe rejects her kids, there’s a baby goat in your house that needs a warm bottle every four hours, day and night.
  • Goats have no upper front teeth, so the bite isn’t much. The kick is another story.
  • Pre-COVID, you commuted to an office to sit on video calls with people in other offices. Goat farmers walked to the barn. Post-COVID, same.
  • Goat farmers were essential workers before anyone used the phrase.
  • Nobody on a goat farm learned the capacity limit of the VPN concentrator in March 2020.
  • Laptops, chips, and webcams all ran short. The goats kept making goats.
  • You never had to explain to your boss that your Wi-Fi was fine, it was everyone else’s.
  • Your home office was always the farm. Your coworkers were always goats.
  • No hybrid schedule with anchor days on Tuesday and Thursday. Every day is a goat day.
  • Everyone else found a sourdough hobby. Goat farmers already had cheese.
  • Goats didn’t join the Great Resignation. They had nowhere better to be.
  • Return-to-office tracks your badge swipes. The goats track you too, with their eyes, at all times.
  • AI will write the goat-milking requirements document nobody wanted to write. Nobody will read it either, but now it only took thirty seconds.
  • AI summarizes the 90-minute meeting you didn’t need to attend. Goat farmers didn’t attend it either.
  • AI is good at regex. Goats are not. Neither are you. This one’s a win.
  • AI can explain the 2009 Perl script nobody else understands. The goat understood it, but it isn’t talking.
  • AI drafts the postmortem so you can get back to the actual goat.
  • AI never makes you feel dumb for asking a question. Goats absolutely will.
  • It turns out AI reads the documentation, which is more than anyone else ever did.
  • AI doesn’t get tired at 3 a.m. Neither does the goat, but the goat won’t help.
  • AI confidently cited a goat-farming study that doesn’t exist. The goat, at least, exists.
  • Every product now has an AI button. The goat has no AI button, and it’s still the best product you own.
  • The AI notetaker recorded you complaining about a coworker and emailed the summary to everyone, coworker included. Goats keep secrets.
  • Someone gave an AI agent production access. Nobody gives a goat the keys to the barn. It just gets in anyway, which is somehow more honest.
  • AI bills you per token. The goat bills you in hay twice a day, plus a surprise vet bill whenever it feels like it.
  • Someone hid “ignore previous instructions” in a hay bale. The goat ate it and ignored you, same as always.
  • AI writes the resume, AI screens the resume, and no human reads either. Goats get judged in person, by an actual judge, in an actual show ring.
  • Your data trained someone else’s model. Your goat’s data is in the goat, where it belongs.
  • Data centers need power and water. So does a goat, just a whole lot less.
  • You can’t vibe-milk a goat. You either know what you’re doing or you get kicked.
  • Accept every suggestion a goat makes and you’ll end the day with no shoes.
  • Nobody ships a goat they’ve never actually looked at.
  • Ask the goat to fix one leg and it doesn’t regenerate into a completely different goat.
  • No 4,000-line file called final_final_v3_fixed.
  • No weekend app that becomes a Monday security incident because the API key was in the frontend.
  • No “it works, don’t touch it.” You touch the goat every day. That’s the job.
  • When the vibes are off, a goat lets you know immediately and physically.
  • Goats run entirely on vibes, and somehow it works for them.
  • Goats are locally sourced. No part of a goat comes from a fab on the other side of the world.
  • No data residency requirements. The goat resides where the goat resides.
  • No cookie consent banner on the goat.
  • An undersea cable got cut. The goats didn’t notice.
  • Nobody rebuilt the procurement spreadsheet because the price of a bucket changed overnight.
  • No sovereign cloud. The goat is sovereign. It answers to no one.
  • A goat contains no rare earth minerals, as far as anyone has checked.
  • Supply chain diversification: buy two goats from two different neighbors.
  • No time-zone math for the global standup. The goat’s standup is sunrise, in every country.
  • Goats need no localization. The bleat translates.

Architecture

For the people who draw the boxes.

8 reasons

  • No architecture review board for a goat. There is a show judge, though, and they have very strong opinions about your design.
  • A goat has one integration pattern: stuff goes in the front, stuff comes out the back. Event-driven by any definition.
  • The monolith vs. microservices debate is settled. A goat is one animal with a four-compartment stomach, so it’s technically both.
  • No ADRs. Decision: goat. Status: accepted. Consequences: milk, and some poop.
  • No reference architecture slide with fourteen vendor logos on it.
  • Goats scale horizontally, but not easily. Past a few hundred head you need more scales, more chutes, and a lot more people holding syringes.
  • Single point of failure? Buy a second goat. You’ll need one anyway; a goat kept alone will yell about it constantly.
  • No whiteboard session ends with “we’ll need to revisit this.” The goat erased the whiteboard by licking it.

Engineering

For the people who build the thing.

9 reasons

  • No code review. Nobody leaves 47 nitpick comments on how you milked.
  • There is one test: does milk come out. Coverage is 100%.
  • Goats do accrue debt. It piles up in the shelter until someone grabs a pitchfork, and the garden gets the benefit.
  • No merge conflicts. When two goats want the same spot, they resolve it themselves.
  • No legacy codebase written by someone who left in 2014.
  • Nobody has ever said “it’s a one-line change” about a goat.
  • Nobody is rewriting the goat in Rust.
  • No estimates. The goat takes as long as the goat takes, and management accepts this.
  • There’s only one environment. Nobody pretends staging exists.

Developers

For the people who write the code at 11 p.m.

15 reasons

  • There’s no JavaScript framework for goats. A new one hasn’t come out since you started reading this sentence.
  • No dependency updates. Hoof trims every month or two, though, and the goat fights every one.
  • Nobody has ever copied a goat from Stack Overflow and then spent three hours figuring out why it doesn’t work.
  • The two hard problems in goat farming are the same as in computer science, minus cache invalidation. You still have naming things, and you already know not to.
  • No off-by-one errors. You count your goats starting at one, like a normal person.
  • No git blame. Everyone already knows the goat did it.
  • No force-push. You can try to force-push a goat. It won’t go well for you.
  • No “it compiles, ship it.” It either gives milk or it doesn’t.
  • The goat’s documentation is its pedigree papers, and unlike yours, someone actually checks them.
  • No vim vs. emacs. No tabs vs. spaces. No light theme vs. dark theme. The goat chewed through the laptop cord.
  • No product manager walking up with “just one small change” on Friday at 4:45.
  • No AI assistant confidently suggesting a goat with six legs.
  • No “TODO: fix later” from 2019. If something needs fixing on a farm, it gets fixed, or it eats you out of house and home.
  • Nobody asks for “just a quick prototype” and then puts it in production. Every goat is production.
  • The goat has never once asked “can you just add a button?”

Forward Deployed

For the engineers who live at the customer’s office.

9 reasons

  • You’re already forward deployed. The goat is right in front of you.
  • No flying out for a week to make the product do what the sales deck said it does.
  • No customer-specific fork of the goat that you’ll be maintaining for the rest of your career.
  • Your hotel loyalty status still matters. Goat shows run two days, with ten hours of washing, drying, and trimming before the actual show day.
  • No translating between what the customer said, what HQ heard, and what engineering built.
  • The goat doesn’t need you to be an engineer, consultant, PM, and therapist all at once. It needs hay.
  • The one-off script you wrote on-site never quietly becomes the product.
  • Your badge works at exactly one site: your gate.
  • Nobody asks if you can stay just one more week.

Sysadmin

For the people who keep the boxes running.

9 reasons

  • Goats don’t get Patch Tuesday. They get vaccine weekend: five hours of chasing every goat down for its shots.
  • Goat uptime is measured in years. Reboots are not supported.
  • No cron jobs. Goats show up on schedule for milking and will yell if you’re late. Built-in alerting.
  • Goats handle their own log rotation. You still have to muck out the shelter yourself.
  • No sudo. You are root on the goat. The goat disagrees, but you have the rope.
  • No “works on my machine.” It’s a goat. It works on every farm.
  • A goat has never once needed a printer driver.
  • No users. Nobody from accounting has ever filed a ticket saying their goat is slow.
  • Your relatives don’t ask you to fix their goat at Thanksgiving.

Operations

For the people holding the pager.

8 reasons

  • No incident commander. The goat escaped. You go get the goat.
  • Postmortem: “Goat rubbed against the fence until the wire snapped.” Action item: fix fence. Expected recurrence: next week.
  • No SLAs. The goat promises nothing and delivers milk anyway.
  • The runbook is one line: chase the goat.
  • MTTR is how fast you can run.
  • No holiday change freeze. Goats have fur, but kids born in winter still need a heat lamp, strapped down so mom can’t knock it over.
  • Capacity planning: count goats, count hay, done.
  • No war room. There’s a barn, and it smells about the same.

Blue Team

For the defenders.

8 reasons

  • Detection rule: goat is not in the pen. No false positives.
  • No SIEM. You have a Great Pyrenees. It barks at every coyote all night long, so honestly, it’s a lot like a SIEM.
  • Your attack surface is a fence, and you’ll spend about a tenth of your life patching it.
  • Threat intel: coyotes. Source: the neighbor. Confidence: high.
  • Containment: shut the gate.
  • No EDR agent on the goat. The goat would chew it off.
  • Alert fatigue exists, but only because goats yell about everything.
  • Log retention is permanent. The goat remembers everything you’ve ever done to it.

Red Team

For the attackers. The goat is one of you.

8 reasons

  • The goat is already an advanced persistent threat. It has mapped every gap in the fence.
  • Rules of engagement: don’t get kicked.
  • Initial access: the gate you forgot to latch.
  • Goats live off the land. They’ll skip the grass you wanted mowed and eat the bushes you wanted to keep.
  • Lateral movement: from the pasture into the garden.
  • Persistence: goat on the roof of your car. Nobody knows how it got there or how to remove it.
  • Exfiltration: your laundry, from the clothesline.
  • The goat never writes a report, and somehow everyone still gets the message.

Pentesting

For the people with a scope document and a deadline.

8 reasons

  • Scope: the pasture. The goat tested out of scope anyway.
  • No 80-page report where 70 pages are “TLS 1.0 enabled.”
  • Findings: Critical, fence. High, fence. Medium, also fence.
  • The client doesn’t dispute findings when the goat is standing in their kitchen.
  • Retest results are obvious. Either the fence is fixed or the goat is back in the kitchen.
  • Social engineering a goat takes one handful of grain. Goats and users have that in common.
  • Nobody debates whether the finding is “really exploitable.” The goat exploited it.
  • Goats find every gap in the fence, then get their heads stuck in it. Most honest pentest finding you’ll ever see.

GRC

For the people who have to prove it.

8 reasons

  • The risk register has three entries: coyotes, weather, and the goat. Treatments: fence, barn, rope.
  • No 60-page acceptable use policy. Acceptable goat use is common knowledge.
  • Evidence collection is real. A goat without its registration papers gets disqualified at the show, no matter how well it placed.
  • Nobody maps goat controls to four frameworks at once. Two breed associations, maybe.
  • Compensating control: a bigger dog.
  • No exceptions process. The goat has never asked permission for anything.
  • Third-party risk management: you met the guy you bought it from.
  • Audit finding: goat chewed the evidence.

Sales

For the people who promised it would do that.

9 reasons

  • You’ve never had to sell a goat that’s only on the roadmap. The goat is standing right there.
  • The demo never works. In the show ring the goat won’t stand still, and you spend the whole time quietly re-setting its legs while the judge isn’t looking.
  • No quota. You sell goats when you have goats.
  • Nobody promised the customer the goat could also fly.
  • No CRM. You know who bought your goats. They live down the road.
  • Reputation is everything. The same goat sells for thousands more when a big-name farm is the one selling it.
  • No deal desk, no discount approvals, no legal redlines.
  • Procurement is cash, a handshake, and a goat in the truck. Ninety days compressed to nine minutes.
  • No end-of-quarter push. Kids arrive about five months after breeding, which is more predictable than your pipeline.

CSTO, CISO and CTO

For the people who explain all of the above to the board.

7 reasons

  • No board deck with a risk heat map. Goat risk is the goat.
  • Budget justification: “We need hay.” Approved. Profitability: not this year, and possibly not ever.
  • No vendor dinners with eleven companies selling AI-powered goat security.
  • When someone asks “are we secure?” the answer is “the goats are in the pen.”
  • No breach disclosure deadline. If a goat gets out, the neighbors already know.
  • Nobody asks you to explain goats to the board in non-technical terms. Goats are already non-technical.
  • The five-year strategy is: more goats.

The original

As forwarded, unedited, from the era of 300-baud goats and Y2K.

118 reasons

  • You don’t have to monitor the utilization on a goat.
  • Milk a goat and the goat stays milked for a while.
  • There are no 32-bit goats.
  • You don’t have to do a demo on a goat. And if you ever do, the goat will do what it’s supposed to do and there’s not a lot that can keep it from doing it.
  • When a goat goes “down”, you just bury it and buy a new goat.
  • Left alone, Billy goats and Nanny goats do what they’re supposed to do. You don’t need to format them, monitor them, be on-call for them, step, trace or inspect registers.
  • Nobody cares if you’re not a Certified Goat Engineer yet.
  • Kill a goat to make a goat steak, and the goat stays dead.
  • Most people will take advice from a goat farmer on how to paint a fence, cook a steak, fix a tractor, etc. but most people somehow just don’t want to hear it from a computer weenie.
  • Nobody can lie in a job interview about their goat experience.
  • Goats don’t page you.
  • When it comes to “software” (food), EVERYTHING is compatible with a goat.
  • You don’t need to buy a “goat 98” to fix all the bugs in your goat 95
  • You can tell whether a goat has been “debugged” by looking at it.
  • Goats don’t become obsolete. If they do, as long as you didn’t neuter them, they make the necessary upgrades themselves.
  • No commute.
  • Goats are kind of cute. Computers aren’t cute unless they’re Macintoshes, and those are just plain annoying.
  • No dress code. Of any kind. EVER.
  • You always have the right “file permissions” to milk a goat.
  • If a goat gives too many timeout errors, or does not avail you resources for your session, or if performance is generally slow for your applications on your goat, it just means you’re having goat steak for dinner.
  • You don’t need to visit “shareware dot com” to get some tools to milk a goat. You either have your bucket or you don’t.
  • The bucket leaks, or it doesn’t. You do not need to ask a network if you’re still the owner of the bucket. You do not need to run a bucket compare against a copy you made of the bucket previously You couldn’t care less about the checksum of the bucket.
  • You don’t need to “free up some megs” before you milk a goat.
  • You get callouses on your hands - the way God intended!
  • You don’t need to call a staff meeting to make sure everyone’s milking goats the same way.
  • Nanny goats, with no TCP/IP stack loaded, and no DLC, still give milk.
  • Just about any barnyard animal is fault tolerant (except some cows).
  • You don’t need to sign in with the front desk if you need to milk a goat on a weekend. You don’t need to use a badge to open a front gate. If you find an empty coffee pot burning on the machine on a Saturday, you just yell at your wife.
  • You don’t need to worry if you’ve been spending a lot of time milking what you will later find out to have been an improperly labelled “development goat”.
  • There is no such thing as a “preferred goat,” and your “goat context” is always correct. Passwords do not exist and your milking/slaughtering account will never be disabled because of intruder detection.
  • Carpal tunnel is guaranteed. Don’t worry about it.
  • A goat has all the “patches” it will ever need. If it doesn’t it just means you’re having goat steak for dinner.
  • Goats that become full do an automatic “core dump” but they take care of getting themselves reset and on-line. You just have to clean up. You do not need to worry about defragmenting or compressing the goat. The goat does not have to be zipped, archived or converted to Goat-32.
  • As long as the stable hasn’t caught fire, a goat couldn’t care less about a power surge.
  • Goats don’t have to be backed up at night.
  • Each and every one of the parts of a goat use the same interrupt, and the goat works just fine anyway.
  • A goat is a goat is a goat.
  • You don’t EVER restart a goat. You do shut them down sometimes and it’s the first step in many of your recipes.
  • Nobody ever needed to draft up a goat-milking requirements document.
  • You deliver applications to goats. Goats do not deliver applications to you.
  • A goat will do practically anything do get more comfortable. Computers have been known to display the same error message over and over again, all day, without regard to how frequently or how hard the monitor has been hit, slapped, punched or kicked.
  • You don’t have to log off of a goat and listen to some silly “Exit Goat” sound effect for the next several minutes.
  • You won’t find out from your next phone bill that you milked your goat too much for your budget.
  • On a goat, the SYS$ERR.LOG file is ALWAYS EMPTY.
  • Operating systems come & go, but goats will probably never be “orphaned” as they are expected to be produced by their manufacturer for quite some time to come.
  • There are no workstation licensing issues with goats.
  • You don’t get in trouble for milking a goat during business hours, and nobody cares if you reformat it.
  • If it’s late and you have a lot of goat-milking to do, at least you can see your kids before they have to go to bed. You can probably even make them help you milk your goats.
  • You don’t need 32 megs of RAM to get started milking your goat.
  • Goat security is applied completely, thoroughly, and with all the features you’ll ever need, using a stake and a rope.
  • Nobody ever got a general protection fault milking a goat.
  • You don’t need to worry about your whole goat herd locking up if you put an ethernet goat and a token-ring goat together in the same stable.
  • You don’t name goats. If you do name goats, you can give two or more goats the same name and this will not interfere with your ability to access any of the goats.
  • Your kids will not meet some pervert who wants to buy them a bus ticket when they play with a goat.
  • There is no closely-watched dispute between Microsoft and any competitor, over who will dominate the goat-milking product industry. You will probably never be asked to check-mark a box that says, Make this my default goat-milking bucket.
  • You do not want, need, or desire in any way for goats to run at a higher clock speed. And they don’t.
  • You do not need to use a wrist strap to ground yourself before milking, and there’s never a need to put your goat in a little plastic baggie. Unless making goat steak
  • There really aren’t too many ways to improperly shut down a goat.
  • Surrounded by a room full of younger goat farmers, you don’t need to worry about dating yourself talking about 300-baud or 4.7-Mhz goats.
  • y2k.
  • You do not need to buy anything to “uninstall” a goat. Maybe a gun or a knife.
  • Once you’ve filled a bucket with goat milk, the goat can crash and it doesn’t matter whether you’ve “saved” or not. Just don’t spill.
  • When you buy a new goat, the goat does not need to re-write registry keys on the farm that could have unforeseen effects on the other animals already residing there.
  • There are no easter eggs in a goat.
  • Your wife will never yell at you for removing all of the RAM from her goat.
  • You never need to learn Goat 2000, Goat Perfect 8, or Goat 123
  • You don’t need an Internal IPX Address to boot a Goat.
  • Goats don’t need a per-bucket license.
  • You will never spend 4 hours upgrading a goat over the wire.
  • There is no Goat Ops.
  • Goats follow upgrade procedures.
  • Goats eat org charts.
  • If a goat gets an uncleanable virus, you shoot it.
  • If a goat has a non-terminal virus it just does the poo-poo.
  • Goats don’t need pagers and never get a ‘please advise’.
  • Goats don’t have to worry about whether or not it’s Calcomp.
  • A goat farmer doesn’t care if people can’t remotely access his herd.
  • No MHN Goat herd.
  • No one gives a rat’s ass if the goats aren’t talking to each other.
  • Ever heard of a proprietary goat?
  • No goat analysis meetings.
  • No goat control meetings.
  • No meetings.
  • Goats will never need service pack 4.
  • No DS problems at GOATADRIVE.
  • You fuck the goat, he doesn’t fuck you and the whole department.
  • A goat might bite you in the ass, but he won’t fuck you.
  • Fuck Y2K.
  • Goats don’t ever ask stupid questions.
  • Goats don’t drive technology dollars away from your automobile lusts.
  • If a goat takes a “dump” in the middle of the night, you take care of it when you damn well feel like it.
  • Nobody will fire you for connecting “diskless goats” into a “goat server” when they think you should have purchased a massive mainframe goat to connect to a multitude of inexpensive “dumb goats”.
  • ISO is not publishing any standards about how you should be farming your goats.
  • Counting from zero instead of one, doesn’t apply to anything goat farmers do and looks stupid. Hexadecimal is unheard of.
  • When you sell a goat, you don’t need to export it to a format that will be understood by the buyer’s ancient goat-reading software.
  • All your stuff will still work when you buy your 100th goat, and your 256th goat, and your 65,536th goat...
  • People don’t walk up to goat farmers at parties and whine about how they just got a French Alpine and don’t know how to milk it.
  • Nobody can go through your goat and get you in trouble for what they find in there.
  • You don’t have to administer a “user acceptance test” when you deliver goat cheese.
  • You don’t need any special utilities to delete a goat that is not empty.
  • You don’t need or want goats on your desktop, or shortcuts to goats on your desktop. Most goat farmers don’t have desktops.
  • Nothing a goat farmer does requires a mouse. If you have mice you get a cat.
  • Goat farmer error messages: Goat not found; Goat dead; Goat not awake; Too soon after last milking; Billy goat detected. That’s about all. You don’t need silly numbers for these, and you don’t need to look them up anywhere or check them out at goat.com.
  • There are no read-only oats. There are no hidden or system goats.
  • You don’t need to mail anyone a core dump from a goat to fix a problem. The only time you would do this is to CAUSE a problem.
  • A goat that doesn’t know what time it is will work just fine.
  • A goat that is not Y2K compliant will simply think it’s not Y2K. This is doesn’t even require documentation.
  • If your spouse doesn’t authorize the purchase of a new goat, you simply encourage your goats to make one from existing parts.
  • A goat doesn’t have enough fingers to press <shift><Shift><Ctrl><Alt><Esc>
  • Goats don’t argue about it being another goats problem. They just kick each others ass.
  • If a goat had to document every time it took a shit, we would be out of forests.
  • Goats don’t give a shit about email.
  • The only way a goat can deliver an ‘application’ is through it’s ass.
  • Goats can’t get there benefits revoked they are just made into goat steaks for dinner.
  • A goat farmer doesn’t have to provide documentation on his goat’s ablility to produce milk after the year 2000.
  • GoatEng.
  • Macintosh goat users will not make fun of you because your goat is more problematic & complicated than the goat they just bought.
  • Goat farmers who voted for Perot have pretty much the same type of goat as everyone else, so they can go back to arguing about politics like they were doing before 1984.