I'll try not and take it personally.

You know the reason for this punchline is because hardware isn't a recurring cost and developers are.  The sad part is that in an actual case like this, management decides it's best to hire contractors for the construction of the product.  But for support, they'll drop it back onto permanent employees who haven't touched the code.

Bit of a downer there.  So let's talk about something fun.  I got a chance to play around with NancyFX yesterday.  They call themselves the custodians of the super-duper-happy path.  It is amazingly fun.  In just a few minutes, I'd Nugeted NancyFx from VS2010, started an empty web project, dumped a C# module into my project (almost anywhere works), inherited from NancyModule, and then dumped code like this into it...

Get["/greet/{name}"] = x => {
      return string.Concat("Hello ", x.name);
};

Except for being a bit of an idiot and calling my first project "Nancy" (don't do that), I had half a dozen REST endpoints running just that fast.  I'm going to teach it to my nine-year old who's been asking about how to do a bit of coding in C# (we've played around with jQuery already.  Kids seem naturally inclined toward understanding selectors in my opinion).

Title: I'll try not and take it personally.
Snarky: There's money on the project for hardware, but not for developers.

I'll never understand fiscal year end logic.

I never received such a threat in my days on large company projects, but I am no stranger to the perverse year end logic that often meant trying to spend large sums of money as quickly as possible.  

I guess like work, money will get spent to meet it's allotted budget, or something like that.

Title: I'll never understand fiscal year end logic
Snarky: I'll put it this way.  If you don't spend the money before Friday, there won't be enough to keep you on Monday.

Also, 2 + 2 != 4