I started a company that was asked to write a proposal to make what became the app that failed last night. I declined because it was outside of our core skillset. You can read my prior comments or look at my profile to validate this. If you want my perspective as someone who started a Democratic software company, you should keep reading.<p>This app emerged from a mandate to make the caucus more accessible and transparent. It was well-intentioned but underfunded and lacked comprehensive organizational buy-in. Introducing tech can help but you have to spend tons of money to make it reliable and usable, then you have to spend more to train everyone in using it. This is a problem organizations of all sizes and shapes face when making massive IT changes.<p>Shadow is a firm that makes custom software for Democrats and progressives. It has an unnecessarily sinister name. There are not a lot of companies that make software for Democrats because it’s an awful job. You make very little money. Everyone hates you when things go wrong, which they will, because the product testing cycle and margins are nonexistent. Then everyone will assume things went wrong because you are some combination– you choose– of secretly evil, secretly working for Bernie, secretly working for The Establishment/Hillary (per someone's unpersuasive Imgur post below), or secretly working for Buttigieg.<p>Others have noted that Shadow also made software for the Buttigieg campaign. If you take my claims above as true, this should be unsurprising to you: a hard market where everyone hates you and no one has money to pay you is not attractive to enterprising software engineers, so there are few firms available to choose.
Checked their LinkedIn and the employees who work there. The founder is non-technical and there are two developers: one who is a "back-end intern" and the other is a front-end developer (both are fresh from bootcamps).<p>...Yikes.
I'm picturing the Dos Equis meme saying "I don't always test, but when I do, I test in production. Stay on call, my friends."<p>At least now I don't feel bad about when I test in production. (just kidding, I didn't feel bad before).
What did this app do exactly? It was just a reporting app, I'm assuming that the source data collected, albeit perhaps in different formats, lived somewhere else and that there wasn't a lot of data or a lot of variations. From my understanding it seems there was an Auth0 redirect issue, but why wasn't this just a night of taking the source data and doing scripting then shipping out the reports via a secure DropBox type service? We've all be there where an ETL job fails, since it isn't critical (e.g., financial transaction), it wasn't tested every which way and we just had to some scripting.<p>Even if it is, say, 500TB of data, in 300 different formats usually those formats aren't drastically "different." Maybe I'm not understanding what the application was supposed to do to not understand why this wasn't solved every quickly. Or maybe given the timeline it was solved quickly once the right people got involved and figured out what needed to be done.
I'm all about Hanlon's razor but naming the ticking time-bomb of a voting software startup "Shadow Inc." seems a bit too on the nose to be pure stupidity.<p>Everything about this reeks of a publicity stunt to "ruin" electronic voting in the public eye.
More info:<p><a href="https://thegrayzone.com/2020/02/04/pro-israel-buttigieg-seth-klarman-iowas-voting-app/" rel="nofollow">https://thegrayzone.com/2020/02/04/pro-israel-buttigieg-seth...</a>
How long will it take our society to realize that democracy is threatened when machines are involved in voting or vote counting?<p>Going back to voting exclusively by ink on paper and hand counting is imperative.
This app failed because no one did enough testing and enough training. What I saw was a relatively simple app to input some data. The problem seems to have been that they never tested it at scale and they assumed that all the users would be able to download it and use it.<p>My experience is that customers hate to pay for testing once they see the product running. They assume that it's done. I had a customer tell me that if I did the programming right it should always work and testing should be minimal. I had to explain to him that that's not the case with software and testing is one of the most important parts of the software development cycle. He felt it was a waste and that I was looking to add extra costs for no reason.<p>I bet there was not enough money. People seem to feel that a few grand will cover the costs. They figure 10k is an outrageous amount. What they don't seem to understand is that it will barely cover the costs of planning the app.<p>Both the developers and the people that approved the app for use need to take responsibility. Too bad since it could have saved a lot of money and time in the long run.<p>BTW, this could have been a Google Form with a spreadsheet as a back end. But user training would have still been an issue. You can't get around that.
This should really be getting more attention, here is an alternative breakdown: <a href="https://imgur.com/gallery/ycOC0HX" rel="nofollow">https://imgur.com/gallery/ycOC0HX</a>.
The jest of it is one of the most important institutions in the United States (the Democratic National Committee) uses a highly nepotistic and incompetent system for managing IT which leads to colossal failures in marketing, canvassing, and security. Not to mention massive PII violations as millions of emails, phone numbers and SSNs, are passed around in plain-text via CSV files.<p>The reason this happens is because hundreds of millions of dollars are lit on fire during election season and all the sharks, including former Google employees, come out to swim. Even well intentioned projects get slammed by the crunch of the election season (seriously try shipping a well scaled app in < 2 months with terrible product direction) and ultimately fail - failing the needs of the entire citizenship of the country.<p>After the success of Obama's 2008 and 2012 campaigns even more money was funneled into IT as a sort of perceived silver bullet. But in 2016 it wasn't, and yet no analysis was done to correct the problems for the 2020 cycle - because the decision makers (all these "CTOs") are clueless fucks who are just there for the money and could care less about the integrity of our democratic system.<p>- in 2016 I worked for one of the companies in this niche and saw the bidding/sales/engineering processes first hand. FWIW I am a life long democratic voter and this makes me sick to my stomach.
I don’t agree with the use of an app here for many reasons. That said, such an app would basically need secure authentication and a form to upload some pre-templated numbers.<p>It seems pretty hard to screw that up so badly but clearly it’s quite easy to make a complete dumpster fire from those requirements.
A small drop in the sea of technical problems: did anyone design the app to work for ages 20-90? People well in their 80's work caucuses.<p>Ok, did anyone actually <i>design</i> the app?
According to multiple reports, the vote counts entered into app and sent were not what was received by HQ. How do we know that the company wasn't paid to change the numbers on the backend? How would the numbers change by themselves? I'll be called a tinfoil-hatter for assuming malice.
This is why we need to start using Byzantine Fault Tolerant distributed systems to vote via our mobile phones. No need for a voting holiday or standing in line. Bigger turnout, too. If it's secure enough for banking apps, why not for opt-in voting via app.<p>Maybe it's too hard to move to electronic voting nationwide. But every organization has governance and could use an electronic voting system based on BFT consensus of mutually distrusting parties. Vote using an app, it gets stored "on-chain", then you can check it on another app.
This Motherboard article has more details on the app including screenshots <a href="https://www.vice.com/en_ca/article/y3m33x/heres-the-shadow-inc-app-that-failed-in-iowa-last-night" rel="nofollow">https://www.vice.com/en_ca/article/y3m33x/heres-the-shadow-i...</a><p>My favorite screenshot is the last one, it looks like a generic mobile Firefox error for a misspecified URL.
This should really be getting more attention, here is an alternative breakdown: <a href="https://imgur.com/gallery/ycOC0HX" rel="nofollow">https://imgur.com/gallery/ycOC0HX</a>.<p>The jest of it is one of the most important institutions in the United States (the Democratic National Committee) uses a highly nepotistic and incompetent system for managing IT which leads to colossal failures in marketing, canvassing, and security. Not to mention massive PII violates as millions of emails, phone numbers and SSNs, are passed around in plain-text via CSV files.<p>The reason this happens is because hundreds of millions of dollars are lit on fire during election season and all the sharks, including former Google employees, come out to swim. Even well intentioned projects get slammed by the crunch of the election season (seriously trying shipping a well scaled app in < 2 months with terrible product direction) and ultimately fail - failing the needs of the entire citizenship of the country.<p>After the success of Obama's 2008 and 2012 campaigns even more money was funneled into IT as a sort of perceived silver bullet. But in 2016 it wasn't, and yet no analysis was done to correct the problems for the 2020 cycle - because the decision makers (all these "CTOs") are clueless fucks who are just there for the money and could care less about the integrity of our democratic system.<p>- in 2016 I worked for one of the companies in this niche and saw the bidding/sales/engineering processes first hand. FWIW I am a life long democratic voter and this makes me sick to my stomach.
The owners and staffers at Shadow INC have a severe conflict of interest. The company is loaded with former Clinton staffers and the CEO sent a tweet in support of Buttigeig, who recently paid tens of thousands to the company.<p>Other suspicious dealings are a premature victory announcement by Buttigeig's campaign and a leak of a picture of paper tallies which included a PIN allegedly used to login to the tally app. Looking for the tweet now...<p>><a href="https://townhall.com/tipsheet/leahbarkoukis/2020/02/04/shadow-hillary-staffers-n2560675" rel="nofollow">https://townhall.com/tipsheet/leahbarkoukis/2020/02/04/shado...</a><p>Edit: I'm not necessarily trying to suggest anything, but I'd like to point out that this post went from +10 to +2 in a matter of minutes.
Is it just me, or is the money just draining away from the economy right now? It's like we were all splashing around in the ocean and suddenly everyone is noticing that their toes are touching the bottom, and there's a few people standing on the steps, floaties on, looking around at us in horror.
Let me get this straight. A company deeply embedded in the Democratic establishment (0) that has worked directly with Buttigieg — the candidate with close ties to Facebook aka the company undermining democracy since 2016 — managed to totally screw up, potentially undermining the campaign of Sanders, the anti-establishment candidate.<p>Yeah, democracy is fucked.<p>0. <a href="https://theintercept.com/2020/02/04/iowa-caucus-app-shadow-acronym/" rel="nofollow">https://theintercept.com/2020/02/04/iowa-caucus-app-shadow-a...</a>
This is ridiculous. Paper. Use a Paper as the true vote. Cross check after that.
I have read so many comments on here up-selling the ability of technology but no one in this thread has the answer. It's apparent.<p>Do the paper vote - as it was always done. Let our technology analyze it afterwords. Why are we all trying to put our technology in front of this simple device. of paper.<p>You all know this rule = "make a single application do one thing well."<p>Again, this is ridiculous from a Credibility sense. Paper + networks, Paper + mobile, forget the paper, Mobile only, Mobile + scale. Where are we at? No where and much less. Just take a paper vote and tally it. Is that so hard?
I think the author's take on this is a bit heavy with hyperbole, but there's no doubt Iowa was a mess last night.<p>My son was there working as volunteer, and so was his ex-girlfriend, who's still a close family friend. I was chatting with them both throughout the evening and into the wee hours this morning.<p>They worked different locations in the Des Moines metro area and the results they reported to me were pretty close to the same in both.<p>I'll say this about it, it's hard to imagine that less than 4500 calls to a server over the course of an hour or two would "crash" it, or even ten times that number. And that I think an SQL db is a poor choice for an app like that.<p>CouchDB, or most any open source "nosql" db, would've been a better choice and, really, so would a dead simple flat file db to store the data for each precinct in and those are both very easy to build for something as simple as this.<p>And they didn't even need an "app" per se. All they needed was a password protected web page with a dead simple form.<p>What happened makes it a bit difficult to avoid pondering if the delays weren't deliberate. Whatever the case may be, the DNC is who ended up taking it on the chin.
My coworker has an alternate theory that frankly makes a lot more sense than “the app broke.”<p>The Iowa caucus is not a paper ballot. People stand in groups in a large multipurpose room and raise their hands for who they vote for. Depending on the viability threshold, people move to new groups and are recounted.<p>The exact rules are complicated and the process is run by unpaid humans. Moreover, in 2020 everyone has smartphones to post embarrassing mistakes on social media. And this year is a very crowded primary for the democrats, raising the chance for error.<p>Under this theory, the app is a convenient scapegoat to hide the fact that the process is inaccurate and bad. For politicians this seems pretty convenient. Who would you rather blame, and decades old tradition or an app contractor?