Bill Bitner

These tweets are my own.

[Bill Bitner @BitnerBill]

@leroysflowers I am getting a lot of spam email from florist shops using an email that I only used once for you. Stop giving out email addresses or worse selling them. Thanks.

[Bill Bitner @BitnerBill]

@steak_umm The Eagles have live eagles at home games.

[Bill Bitner @BitnerBill]

Rule 12 Customers forgive mistakes, not excuses.
https://t.co/JaiW519eyO

[Bill Bitner @BitnerBill]

The recap on 8 days without social media. https://t.co/VD9fQ5c6fm

[Bill Bitner @BitnerBill]

Starting my annual break from social media a few days early. See you on the 12th.

[Bill Bitner @BitnerBill]

https://t.co/hqM8NoKUNh

[Bill Bitner @BitnerBill]

@thecryptolauren Maybe "Fiat" or "Minima"?

[Bill Bitner @BitnerBill]

Friday Fun - Have a great weekend everyone!

[Bill Bitner @BitnerBill]

Congrats to the #zVM Team on reaching General Availability of z/VM 7.4

https://t.co/Mkv8XLy8R2

[Kaleb @PrimeERod]

idk how I didn’t notice this but bro look at the ref running 4.2 40 speed 😭😭😭

[Bill Bitner @BitnerBill]

Fun Friday - when I first saw this, I thought it was spray insulation. Have a good day everyone and a great weekend!

[Bill Bitner @BitnerBill]

https://t.co/OCCgvHZ3v2

[Bill Bitner @BitnerBill]

https://t.co/hXgkLhOELl

[Bill Bitner @BitnerBill]

@ich408i Was great to see some people from Vertali at the VM Workshop earlier this month. Hope all is well!

[Bill Bitner @BitnerBill]

@cooksd @ZacEfron I watched it the other weekend, and really enjoyed it.

[Bill Bitner @BitnerBill]

@samknutson What a great shot!

[Bill Bitner @BitnerBill]

@martinpacker I don't get it.

[Bill Bitner @BitnerBill]

@HaloedPayload Or another case, where we started looking at other machines to see who had or didn't have the problem to help establish what was different, what changed.

[Bill Bitner @BitnerBill]

@HaloedPayload Something that came to mind was working on a network performance problem. We had set traces but they weren't triggered. Decided to ask for a network diagram (should have earlier). When we got that, it was obvious there were multiple TCP/IP stacks and we had traced the wrong one.