Enjoy the benefits of a premium membership!
Upgrade Account
-
TalkBass has been independent since 1998. Add your voice.
Create a free account to reply to discussions, view embedded media, and browse with fewer display ads.
Join free Log in
Want zero display ads or expanded classifieds tools? Compare plans.
Why? I don't get it.
- Thread starter BassyBill
- Start date
Gaolee
Official leathers tester and crash dummy
Because they can. It's a computer thing as far as I can tell. I'm not a computer guy, so the endless "upgrades" with their inevitable screw-ups are just an irritant as far as I'm concerned.
I wish I had a dollar for everything that was marketed as "New and improved" that turned out to be a turkey. Give me old and time tested any day of the week.
I wonder how much money would be saved by companies if they would just thoroughly test their new products and get them right the first time rather than to have to spend the extra bucks on recalls and replacements.
I also wonder how much all those recalls have cost us as consumers. Darn bean counters.
I wonder how much money would be saved by companies if they would just thoroughly test their new products and get them right the first time rather than to have to spend the extra bucks on recalls and replacements.
I also wonder how much all those recalls have cost us as consumers. Darn bean counters.
The simplest backup plan is to revert everything back the way it was.
Outside of that, sounds like they didn't test out the new changes in a test environment. Or there was a detail that they didn't implement in the production environment that they did in the test environment. I understand that some upgrades are necessary as software companies stop support of old versions, forcing companies to upgrade to supported versions.
Old news my friend. The TB update was way more than two weeks ago. 
-Mike
-Mike
Ha ha! I must admit, it took me quite a while to get used to the new TalkBass when it was launched. Now I've sort of settled in, I think it's way better to use (and also much more stable from a tech point of view - the XenForo software has been a major improvement).Old news my friend. The TB update was way more than two weeks ago.
-Mike
Because it's common to market something as "new" and "cutting edge"...and then have the buyer spend the next 5 years downloading bug-fixes, corrections, patches and up-dates.
At the end of that 5 years, the "new' and "cutting edge" product is released......and the cycle starts all over again.
At the end of that 5 years, the "new' and "cutting edge" product is released......and the cycle starts all over again.
Web people...
I am a computer guy... With more than a little gray hair... it's unseasoned tech people that unleash the stupidity from what I can tell.
Amen... I'm all over new functionality. It is part of the tech existence. New or die... Problem is that web dev project management and QA seems to be sorely lacking...
Usually, the most likely scenario is that someone higher up rushed the project (and most likely added new feature requests to the originally agreed upon specs) while the developers demanded more time, yet the developers/testers get all the blame, even from the people who rushed the project.
Yep, that can happen too. A strong PM is going to present that scenario back to management and point out the capacity issues. This is one reason Agile is a must in some organizations.
Gaolee
Official leathers tester and crash dummy
When a techie offers to show you some "cool stuff," run screaming the other way. Every time I went over how I use Excel with a Microsoft representative, and that happened fairly regularly about ten years ago, they would be amazed that I could "create information." Well, duh! That's what you do when you do an estimate. Those guys always thought I would be interested in all kinds of gee-gaws and gimcracks that they wanted to put into the program. I told them repeatedly that it would just be bloatware and slow things down. Not to mention be utterly useless to people like me who actually use Excel. History shows you how much they listened to the users they interviewed.
As far as I can tell, the computer program developers go off on their own little tangents that they like and completely forget that there are people who use the programs they write for very practical purposes. When it doesn't work any more and when the upgrade means your old estimate is now unusable, it's a tax on my time, imposed by an idiot. Yes, program developers are idiots who don't suffer the consequences of their cockamamie and poorly executed gimmicks.
Yes, I have an attitude problem when it comes to IT. They have earned my bad attitude. Automobile makers have their issues, but if they screwed things up as regularly and as thoroughly as computer people, we would all be dead.
As far as I can tell, the computer program developers go off on their own little tangents that they like and completely forget that there are people who use the programs they write for very practical purposes. When it doesn't work any more and when the upgrade means your old estimate is now unusable, it's a tax on my time, imposed by an idiot. Yes, program developers are idiots who don't suffer the consequences of their cockamamie and poorly executed gimmicks.
Yes, I have an attitude problem when it comes to IT. They have earned my bad attitude. Automobile makers have their issues, but if they screwed things up as regularly and as thoroughly as computer people, we would all be dead.
Last edited:
Patently false; the developers want to avoid all useless crap because they actually have to build that stuff! If we're developing a commissioned project that we have no real interest in, we will do what the specs and the project manager tells us. You have to understand that the people who order a new product are the ones that should know what they want, and should be able to write that down in a way an outsider can understand (though a good sales team + PM should be able to help with getting the information), and the developers can only know what reads in the specifications. Also, graphical/UI designers are rarely software engineers, so if they mess something up and the client approves their messed up crap, it further garbles things later on. Even if the specs are clear, they are usually missing important tidbits that the customer didn't remember or think of writing down; adding these later on will delay the project, as some things that seem like minor changes may require major rewrites in the software. If it's an in-house project and the developers know how the product should really work, they can usually spot missing things much more reliably, but that won't help with deadlines if the feature requests come from a client that for one reason or another has control of the deadline regardless of the late-coming additions (currently battling a situation like this
). When deadlines are hitting hard, testing time will also be severely limited.Welcome to dev-hell! I can promise you that most of us would rather make the minimum viable product to save time, since time is a luxury we're rarely given.
Sure, there are crappy developers too, but in a well-established software company, the cause for most problems is rarely the devs. The classic rule of garbage in, garbage out works here too. In the time I've been working as a software engineer / project manager, I've only been in a single project that had near-impeccable specs from the client and went almost exactly as originally planned. But as I said before, no matter what causes the delays or problems, ignorant people will always blame the devs since they're obviously the only guys that contribute to making the software! 
We go off on tangents when we are interested in what we do, and the stuff we're paid for rarely fits that bill.
Last edited:
Gaolee
Official leathers tester and crash dummy
I was using the term generically for the entire process and organization that screws things up. Yep, I'm basically an ignorant person when it comes to how that mess gets made, but it is still a frustrating mess to have to deal with.
in the world of computers it seems to be "if it aint broke, fix it til it is"
Bob Lee (QSC)
In case you missed it, I work for QSC Audio!
- Jul 3, 2001
- 12,668
- 2,036
- 67
- Disclosures
- Former Technical Communications Developer, QSC Audio
It's probably not limited to Company A, but also Companies B through Z.
...and the real problem is that the "requirements" make no sense whatsoever.Usually, the most likely scenario is that someone higher up rushed the project (and most likely added new feature requests to the originally agreed upon specs) while the developers demanded more time, yet the developers/testers get all the blame, even from the people who rushed the project.
Many times there is a functionality issue behind the scenes. The company will upgrade, in order to handle the specific issue, but the upgrade will have decreased functionality in an area they had not thought of. Or, there will be bugs in the new design. In some cases, this gets fixed. In other cases, not so much.
Bob Lee (QSC)
In case you missed it, I work for QSC Audio!
- Jul 3, 2001
- 12,668
- 2,036
- 67
- Disclosures
- Former Technical Communications Developer, QSC Audio
