Earlier quoted context omitted.
Isn't that with all the products? New teams that own the legacy code base, new PMs that need to show they are doing something... That's how all software products rot. It's normal lifecycle of products that we need to accept.
it shouldn't have to be that way
Tables: Tracking work for teams
231–240 of 375 posts
Re: Tables: Tracking work for teams
#232Tangentially related, but google nixed android chrome's "home"/"duet" feature which allowed having the url bar at the bottom of the screen and made navigating on a phone/tablet _much_ easier. I'm somewhat baffled how they can work on a tablet and be so unaware of what a good UI looks like.
Also, like all google's mobile apps, the iOS version is just straight up better: https://apps.apple.com/us/app/google-chrome/id535886823
Looks like there's a new flag chrome://flags#enable-conditional-tabstrip [0]. Here we go again.
Re: Tables: Tracking work for teams
#233Hard technology vs. apps/services?
Re: Tables: Tracking work for teams
#234Earlier quoted context omitted.
As a Googler, I'd just say it's a boring meme that shows little thought and just wastes time actually getting to interesting discussion here. It's almost akin to "first" from the old days of Slashdot or the race to mention generics whenever anything related to Go comes up. Products come and products go, this is not unique to Google. Killed By Google is cited as some sort of proof, but that goes back to _2003_, and do…
Really not helping the condescending Googler stereotype there bud. Or perhaps its OK for you to be this way as a tech "elite" that makes $450k a year.
Not sure where the "elite" or "450k/year" is coming from as well in the parent comment. Perhaps give that comment another chance to see what they are actually saying?
Disc: Googler.
Re: Tables: Tracking work for teams
#235Next time a VC asks you "what are you going to do if Google builds X too?" send them a link to this discussion!
Re: Tables: Tracking work for teams
#236Earlier quoted context omitted.
Are all these comments about the near and inevitable death of your new product at all soul-crushing? I'm a stranger on the internet and even I can feel the burn. Good luck.
As a Googler, I'd just say it's a boring meme that shows little thought and just wastes time actually getting to interesting discussion here. It's almost akin to "first" from the old days of Slashdot or the race to mention generics whenever anything related to Go comes up. Products come and products go, this is not unique to Google. Killed By Google is cited as some sort of proof, but that goes back to _2003_, and do…
Re: Tables: Tracking work for teams
#237Re: Tables: Tracking work for teams
#238Earlier quoted context omitted.
That's going to be the common case; without knowing the end-target application, most data formats we would pick at random are useless to non-programmers. Even JSON is too complex for non-programmers.
Plaintext would not be too complex for non-programmers. Coupled with in-file tokens, it makes for an easy format to export into anything. That's why I am using it as the base format for my forum application. At any time, the entire forum content can be exported into plaintext, which is readable by most users on most platforms (except iOS) And also can be re-imported into just about anything with a quick Perl script.
There's a reason plaintext is rarely used as the preferred method of semantic data exchange. What's our preferred method of representing images with plaintext? Audio files? Rich text, such as Google Docs? Spreadsheets (complete with formulae and attached macros)? Databases that contain bin-blob fields?
> And also can be re-imported into just about anything with a quick Perl script.
In your specific use case, I expect that works well. In the general case, my experience has been that plaintext can be imported into just about anything incorrectly with a quick Perl script. And when the data is MBs / GBs, the odds that such an error goes unnoticed until the data is needed and cannot be reconstituted are high.
Re: Tables: Tracking work for teams
#239Interesting that they would launch this as a totally separate product and not as a part of G Suite. Do you think they want to create some distance between them and the rest of Google because ofd Google's reputation of shutting down products? Or maybe they want to launch a product outside the usual bureaucracy?
"At Area 120, we work on 20% projects 100% of the time." It literally just has no backing by Google's corporate or business goals.
Re: Tables: Tracking work for teams
#240Earlier quoted context omitted.
Are all these comments about the near and inevitable death of your new product at all soul-crushing? I'm a stranger on the internet and even I can feel the burn. Good luck.
As a Googler, I'd just say it's a boring meme that shows little thought and just wastes time actually getting to interesting discussion here. It's almost akin to "first" from the old days of Slashdot or the race to mention generics whenever anything related to Go comes up. Products come and products go, this is not unique to Google. Killed By Google is cited as some sort of proof, but that goes back to _2003_, and do…
It's not a meme. It's a very real problem that prevents people from wanting to invest in Google services. It's a self-fulfilling prophecy too when people don't use these services, then they get shuttered for low usage.
Google has a huge amount of work to do to earn the trust they've burned, and responses like this damage the cause further. You've cemented firmly in my mind that staying the hell away from this and anything Google has to offer is the right choice, as they clearly don't take this problem seriously and won't even acknowledge it.
I really think you should reconsider.