Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Are you the same person who writes those spam messages all over devrant? Your writing style is very similar.
I'm thinking Google actually makes mistakes when they integrate projects to the big name ones. It feels like they're adding bloat just to make bean counters happy. It's better to kill something outright than to forcefully integrate it somewhere where it doesn't make sense. Sometimes they make good choices, though, like integrating Word Lens to Google Translate.
It must feel great to be a dev who has worked on multiple projects at Google, all of which have since been cancelled.
Creating a stripped down version of a product is a big red flag to me (e.g. "easy/light mode").
It means the main product is too complicated; it handles too many things. Instead, shift the focus back to the core of the product by removing features.
In the our day-to-day it is completely normal to stumble upon things that used to work but now have been changed: they have been deprecated.
Deprecating and removing features should be added to any product iteration. Thus being "normal" and a common occurrence in any changelog; just like features and bug fixes.
This gives non-tech product owners "permission" to remove bloat. Devs stop whining about "the big rewrite". And end-users don't suddenly have to learn yet another tool with "basic" features missing.
I think the best example is google (https://killedbygoogle.com/) and the worst is the amazon shopping website (what a mess!).
random