214 karma · joined February 6, 2019
You're not alone. It's a big reason why time based releases are popular. It's why eXtreme Programming (XP) became a thing.
Given enough time, every engineer would ship the most exquisite solution; problem is, their competitor shipped something good enough long ago OR that exquisite solution isn't what the customer wanted.
Release early, release often.
It's more likely a management problem, with managers who've fallen into the Peter Drucker "Activity Trap".
A basic understanding of how we're influenced. Books that come to mind are:Influence: The Psychology of Persuasion, Thinking Fast and Thinking Slow, and The Design of Everyday Things.
After accepting we can be influenced, then we need to understand real world examples of nefarious influence through social media and adtech. The Senate Intelligence Committee report on the 2016 election comes to mind.
So if we can be influenced, and if there's evidence our elections have been influenced; then we need to question if China is a threat, through Tik Tok.
https://cheatsheetseries.owasp.org/cheatsheets/Password_Stor...
Some companies will have the luxury to avoid a race to the bottom, driven by the addiction to quarterly profits. The rest will get to read about their luxuries, will they endure a sisyphean existence.
Likely has more to do with the looming "debt spiral", and not productivity.
https://news.bloomberglaw.com/bankruptcy-law/global-real-est...
I've learned, yes, you can save money - but only if you're good at forecasting workload and operational costs out 5 years.
I suspect most rushing into the move have inaccurate mental models around true costs related to things like a 24/7/365 NOC and rolling their own IAM to solve SOC2 requirements.
Then there's the recruiting problem. Many engineers want to stay sharp on the latest and greatest in the cloud. Few will want to work on your klunky MVP built in house.
https://www.toyota-industries.com/company/history/toyoda_sak...
https://cloud.google.com/architecture/devops/devops-culture-...
Change management becomes the bottleneck when organizations exceed Dunbar's Number, and a "reverse Conway maneuver" is needed to counter excessive cost of coordination.
https://cloud.google.com/architecture/devops/devops-tech-arc...
Why not require registration and in turn authentication? Easier to rate limit with authentication.
It's also unclear what outcome the business is looking for. If I had to guess, a big contract requires "security" and management wants to check that box the cheapest way possible.
If it's about first steps to improving security posture, and assuming you have a SAAS offering - then the first thing I'd do is start a bug bounty with hackerone or bugcrowd. It's the quickest way to both establish a feedback loop on security state, while also introducing a forcing function to prioritize fixing defects.