People in computer programming don't deal with EST/EDT at all. I do everything in UTC intentionally to avoid DST issues, that's how I messed up here. Most seemed to get it, as the countdown clocks and UTC conversions I saw initially were accurate.
As a person in computer programming, I'll tell you that since I have had to deal with it, you're wrong on your absolute claim that I (and no other programmers) have had to deal with EDT/EST.
I have had to communicate with customers across the country letting them know precisely when to schedule resources, and such accuracy is pretty important. I had this EXACT issue with a Fortune 500 company within the past year, and have the emails to prove it. And yes, it's confusing to some people.
If you interface with humans, and have to do any scheduling, especially around the spring or fall time change, it's critical.
If you write a web interface that accepts the time, and have to convert it to UTC to put it into your database, you better know the difference between Standard Time and Daylight Saving Time.
But hey, I don't have a stake in this game.
I'm just stating the facts as an observer.
It's your game. You can treat your potential investors any way you want.