No more stars!
#21
A second update followed if you also noticed.
Now, the Posts and Likes are just numbers, not the entire text sentence. Presumably this saves a little space. They could also have just combined the 2 icons into one to save space. We all know it's S2KI...
Plain white with years (and do the calculation correctly, instead of the 5 year model) for normal members.
Gold with years for premium.
Perhaps a 3rd or 4th color for admins and moderators.
Point being, engineers don't do user experience well, so the changed the little stars to 1 logo, and changed the wording to another.
Engifineer- The SaaS model absolutely does this, however, sometimes, they are forced to changed by the hosting (Iaas/Cloud) providers as well. Services, versions, etc... are all modified/changed/deprecated on them so they have to move forward. The more you write custom code on top of SaaS solutions the worse it gets. If you stay bear bones, you're usually pretty safe. I haven't read it, but a friend posted a NY Times article on SaaS recently. My service at my past work I fought against SaaS because the applications on my platform were very OS dependent. If AWS/MS-Azure etc... decided the OS was done, there was no alternative. Instead of going SaaS/Cloud, we kept it in house for the control and not breaking applications. It's a vicious cycle.
Now, the Posts and Likes are just numbers, not the entire text sentence. Presumably this saves a little space. They could also have just combined the 2 icons into one to save space. We all know it's S2KI...
Plain white with years (and do the calculation correctly, instead of the 5 year model) for normal members.
Gold with years for premium.
Perhaps a 3rd or 4th color for admins and moderators.
Point being, engineers don't do user experience well, so the changed the little stars to 1 logo, and changed the wording to another.
Engifineer- The SaaS model absolutely does this, however, sometimes, they are forced to changed by the hosting (Iaas/Cloud) providers as well. Services, versions, etc... are all modified/changed/deprecated on them so they have to move forward. The more you write custom code on top of SaaS solutions the worse it gets. If you stay bear bones, you're usually pretty safe. I haven't read it, but a friend posted a NY Times article on SaaS recently. My service at my past work I fought against SaaS because the applications on my platform were very OS dependent. If AWS/MS-Azure etc... decided the OS was done, there was no alternative. Instead of going SaaS/Cloud, we kept it in house for the control and not breaking applications. It's a vicious cycle.
The following 2 users liked this post by Heyitsgary:
engifineer (Yesterday),
jukngene (Yesterday)
#22
Intuit caused us a ton of pain. Made changes unannounced that actually broke our invoicing and cost us a ton of work to fix all the issues. Made a change that literally set all of our hours to not billable and thus we had to go in and modify all the records to fix it, having to write a script to make it faster. Their response is basically like the SCCA .. "Thank you for your feedback" lol
#23
Sorry to hear. You'd think they'd be testing their work. That's an issue. My point is that sometimes they're forced to make changes that seem unnecessary to us, but are necessary to them for some reason we don't see.
The following users liked this post:
SheDrivesIt (Yesterday)
The following users liked this post:
Kyras (Yesterday)