Btw, you have to understand I built educational online marketing training platforms from scratch working with developers about 20 years ago for a few years. Spent countless sleepless nights working with developer teams and individuals in India, Pakistan, eastern Europe, the US while living in the US. I instructed them what I wanted built then, I'd test it, I'd find bugs report to get fixed, ask for adjustments and changes. Many of it was marketing funnels with email opt ins, and multiple buy buttons and intricate marketing messaging requiring specific formating (before the drag and drop and build your own was a thing (I was actually in charge with onboarding a team to create probably even the first such specific for marketing funnels (like clickfunnels, like kartra) system 16 years ago now). If anything wasn't functioning that could mean hundreds of thousands or millions of sales gone awry on launch day.
There have been some wonderful devs that have been a joy to work with and some others it has almost felt like a battle, like a ego thing. Like, some almost feel baffled and super resistant to accepting there are any errors and wanting to fix their code?
I mean that even happened as recent as last year. I was working at this fellowship and it was totally not my role but I couldn't help me to turn my strategy, marketing, funnel and launch hat on and super overgive until i finally had to say enough is enough. But they literally we're getting ready to launch their funnel. And I nicely asked if anyone more than the dev guy has gone through the user experience and tested everything front.
This created well unfortunately months long delays in them launching and needing to revamp their whole approach probably more than once because once a few team members started testing it became apparent that there's little that's functioning as it should. Or maybe I should say a lot of things were broken, behaving mysteriously and didn't seem to wanna be fixed until even a whole new platform was being considered to transition over. It wasn't just the dev, it was the Lead who clearly had no idea how to properly help navigate the challenge. It was clear to me the dev was incompetent. So eventually after weeks of witnessing them having no logical strategic approach and playing mental gymnastics around taking totally illogical paths, I'd suggested they bring in an expert in this particular system to have him consult with or just take him off the project. I so happened to be in a group related this system and took me two minutes to connect with the forefront expert builder on it.
Eventually I left this team because they took every single strategy advice I gave to help remedy their incompetence (stepping outside of the role I had come in with, on so many levels overgiving) but failed to reciprocate creating an equitable relational field.
Anyhow. Got swooped into a bit of a rant on that last one... But...
Like Why is that? Why are some devs like not acknowledging or just blaming something else but their own code for why something is not working... It's not my fault it's not working on three different devices and there are inconsistencies. It's not me. You built it. I am helping you fix it by pointing it out. Don't gaslight me. Also, you can maybe code and build but I strategize and relate to the user experience. Don't underestaminate me.
And grow a fucking pair.
