I've tried to keep my mouth shut and give WDFW the benefit of the doubt throughout this process. With that said, I've been directly involved with two major software/payment processing conversions and three major software/processing companies in the past 4 years (an overall franchise containing millions of individual accounts). A few takeaways...
- We had implemented far more stringent (Anti-Hack) measures long before the breeches many of you experienced with regional fish and wildlife departments took place. Curious who was held accountable...anywhere?
- Any website/payment/application/individual data discrepancies or lags are a direct result of poor management, accountability, or vendor selection. There are extremely under-funded wildlife agencies within the U.S. which would, in my opinion, help justify the types of rollout issues we've experienced (not breeches). Based on my observations, WA shouldn't be one of them (but could be experiencing serious castration by Olympia... I don't know).
- We're all too accustomed to bureaucratic, lazy, "job justification" type agencies who ultimately, we employ. My data was stolen from the VA along with millions of others and I received a blanket apology and free credit monitoring service. Ohhh thanks.
When I moved here, I had horrible experiences just trying to get my hunter's ed certificate "validated" by WA. The people whom I spoke with probably never picked up a rifle in their life. Yet, that's ok. What's not ok, is that my certification date is listed as the date my instructor was certified by my former state. Any half-wit would look at this and question how anyone could be certified at age 6? Of course, any system with logical constraints would have an algorithm built in to flag this.
