Google has started automatically blocking emails sent by bulk senders who don’t meet stricter spam thresholds and authenticate their messages as required by new guidelines to strengthen defenses against spam and phishing attacks.
As announced in October, the company now requires those who want to dispatch over 5,000 messages daily to Gmail accounts to set up SPF/DKIM and DMARC email authentication for their domains.
I mean, you’re scapegoating developers right now. Developers don’t determine priorities. That’s a product/business direction problem.
Also, UX doesn’t get to say what is hard to do or not (that’s the job of a developer, you really don’t have any way of knowing without familiarity with the implementation details), so that’s certainly at least part of your problem right there.
Bullshit and it’s right there in your comment: devs are not the only ones capable of assessing difficulty. The entire team should be doing that COLLABORATIVELY well before any dev touches a keyboard. Code isn’t some arcane black magic and we’ve all built products before, heard these excuses before… so stop saying “that’s not your job, that’s not my job”. Not a good look.
Suddenly declaring something is too hard and ignoring specs during the build phase is not a part of any dev’s fucking job, though you’d be surprised by the way they act.
Which is encapsulated perfectly in your comment. You mention that it’s someone else’s job to handle business direction problems while ignoring the how that problem is actually the dev not doing their job to begin with. The product meets its goals by showing three points of data, but a dev said fuck it and only showed one. That’s not a business issue, it’s a “I don’t want it” issue. Just like in your comment, any issues with “business direction” did not exist until you cited it to cover up for not doing the work that was already planned.
It’s not scapegoating to point out actual behavior. Behavior I’ve seen for 15 years and behavior you reinforced with your comment. It’s insulting to hear someone act like I can’t possibly understand something being hard. So apparently they don’t need to collaborate and can just make decisions in a vacuum.
It’s especially maddening to hear this after I’ve spent the past year working directly with the CEO and CPO on a new product, led focus groups, spoken with 100’s users on the issue, designed prototyped and validated with additional testing… the board is happy, the c-suite is happy, the users like it, we’re all set except some jackass developer thinks since they know C# everyone else can’t possibly understand how hard things are.