This has frustrated me for so long, and what turned me off of AWS for so long, even though I still had to dive in at some point.
Even today I was looking at Tapad, and it took me 3-4 page clicks to figure it out, looking at their solutions and reverse engineering their copy written jargon.
Some sites I swear I'll browse every page and still not understand what they do...
I can understand the approach to appeal to, let's say, sales or non-tech oriented people using THEIR jargon, so it's not tech industry specific but probably annoying and pedantic for everyone..
Software dev at Netflix | DC techie | Conference speaker | egghead Instructor | TC39 Educators Committee | Girls Who Code Facilitator | Board game geek | @laurieontech on twitter
This has frustrated me for so long, and what turned me off of AWS for so long, even though I still had to dive in at some point.
Even today I was looking at Tapad, and it took me 3-4 page clicks to figure it out, looking at their solutions and reverse engineering their copy written jargon.
Some sites I swear I'll browse every page and still not understand what they do...
I can understand the approach to appeal to, let's say, sales or non-tech oriented people using THEIR jargon, so it's not tech industry specific but probably annoying and pedantic for everyone..
Amazon are crap in naming their stuff.
I just learned (well, about a month ago) the reason some services are AWS xyz and some are Amazon xyz.
If it's used internally by Amazon and started there: it's Amazon xyz.
If it was developed as a service first: AWS xyz.
Never knew that. Interesting.
We are partnered with AWS for the last few years. Even our GM didn't know this. 😂🤣