| Pages: [1] 2 :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Pillowtalk
Republic Military School
Minmatar Republic
0
   |
Posted - 2011.12.21 14:32:00 -
[1] - Quote
I love Eve, I really really do. I just came back to Eve after 3 years, and one thing hasn't changed an ounce. CCP has absolutely no quality control at all.
When I left it was......
"OHHHH new big expansion"
bugs
patch
bugs
patch
bugs
emergency downtime
bugs
patch
emergency reboot
patch
And its still the same.
CCP you really gotta step it up a notch as far as quality control goes. You need to hire an ace who has been doing project management for 15 years or something.
I spent 6 hours last night reinstalling the Eve client because the patch broke my install.
You gotta get this under control or my return is gunna be short.
P.S. I'm really not trying to be negative or denigrate CCP, just calling it how I see it =/ |
Teinyhr
A Club for Reputable Gentlemen
5
|
Posted - 2011.12.21 14:39:00 -
[2] - Quote
*standard comment on how unique PC's are a pain to program for, and that while some part of code might behave okay with a dozen testers, might go completely apeshit when used by thousands of people at the same time* |
indiana bones
Federal Navy Academy
Gallente Federation
20
|
Posted - 2011.12.21 14:44:00 -
[3] - Quote
i can haz..... ur stuffz? |
baltec1
250
|
Posted - 2011.12.21 14:50:00 -
[4] - Quote
Name a MMO that doesnt have bugs in big patches. |
Ammzi
Imperial Guardians
186
|
Posted - 2011.12.21 14:56:00 -
[5] - Quote
baltec1 wrote:Name a MMO that doesnt have bugs in big patches.
Bot nets?
quote CCP Spitfire
"Hello Im Blue,"
|
Thomas Abernathy
Beekeepers Anonymous
19
|
Posted - 2011.12.21 15:57:00 -
[6] - Quote
Have to agree with OP...
Daily patches to patch the patch, and a new set of patch bugs, not to mention half the bugs introduced with Crucible are still there. It's becoming increasing hard to say good things about CCP, when it's the same old problems over and over... 
Losing connection with probes
windows resetting themselves after every bugfix, info on other players not displaying properly, overview not updating.
The list goes on and on...
When you break more things than you fix...there's an issue. 
"Fighting CCD since 2139" |
Borisaurus
Dreddit
Test Alliance Please Ignore
5
|
Posted - 2011.12.21 16:12:00 -
[7] - Quote
I too am outraged at CCP's fervent bug fixing and also feel that certain unavoidable realities of the process are in fact slights against me personally and not consequences of certain changes to the game's code that help me more than inconvenience me.
Canvas Glue - Chrome Extension. |||| Aesthetics and Spacecraft - A sporadically updated gaming blog. |
Lucien Visteen
Imperial Academy
Amarr Empire
57
|
Posted - 2011.12.21 16:33:00 -
[8] - Quote
Pillowtalk wrote:"OHHHH new big expansion"
bugs
patch
bugs
patch
bugs
emergency downtime
bugs
patch
emergency reboot
patch
This is the lifecycle for every mmo out there I believe.
The ships hung in the sky in much the same way that bricks don't. |
Thomas Abernathy
Beekeepers Anonymous
19
|
Posted - 2011.12.21 17:02:00 -
[9] - Quote
Borisaurus wrote:I too am outraged at CCP's fervent bug fixing and also feel that certain unavoidable realities of the process are in fact slights against me personally and not consequences of certain changes to the game's code that help me more than inconvenience me.
Sorry Jr Goon, your opinion is not really relevent. 
Just because you kids got SC's nerfed to allow your rifter blobs to take over 0.0, doesn't mean everything is good with the rest of the game....
"Fighting CCD since 2139" |
Cindy Marco
Sebiestor Tribe
Minmatar Republic
4
|
Posted - 2011.12.21 17:18:00 -
[10] - Quote
Pillowtalk wrote:I love Eve, I really really do. I just came back to Eve after 3 years, and one thing hasn't changed an ounce. CCP has absolutely no quality control at all.
When I left it was......
"OHHHH new big expansion"
bugs
patch
bugs
patch
bugs
emergency downtime
bugs
patch
emergency reboot
patch
And its still the same.
CCP you really gotta step it up a notch as far as quality control goes. You need to hire an ace who has been doing project management for 15 years or something.
I spent 6 hours last night reinstalling the Eve client because the patch broke my install.
You gotta get this under control or my return is gunna be short.
P.S. I'm really not trying to be negative or denigrate CCP, just calling it how I see it =/
You could replace CCP with alot of other names and it would be just as true. Its just the way most MMOs are. |
Jack bubu
GK inc.
Pandemic Legion
112
|
Posted - 2011.12.21 17:21:00 -
[11] - Quote
after 6 years of EVE, the Battlefield series and alot of other games you kind of get used to it and just shrug it off :P |
Hung TuLo
Heavy Asset Relocation Inc
17
|
Posted - 2011.12.21 18:29:00 -
[12] - Quote
I actually am a professional software quality control analyst.
How may of you in this thread can say that, how many of the players can say that. What do you really know about SQC?
It is virtually impossible to catch every single bug that is in a game this size. Its not possible
1. There are so many computer set-ups that need to be considered.
2. Different graphics cards that are used.
3. Networking issues to consider.
4. Different programing modules that need to be worked on on a daily basis.
5. New equipment that needs to be considered in their systems.
6. They release new code every six months that allow you to enjoy this game. We arn't talking 10 lines of code, we are talking 10's of thousands of lines of code that probably need to be modified.
7. Intigration processes.
8. characters that transfer from one server to other servers.
9. Localization issues.
10. patching issues and when it needs to happen.
11 Release issues.
12. Code upgrades.
13. Code migrations.
14. Petition requests and responses.
15. Server Load issues
That is a small list.
So, when you want to ***** and complain about the patches remember this,. There is alot more than what is going on that you can't see. They have a job just like you should have a job. They are doing their job to the best of their ability and are trying to be a professional as possible.
Don't assume they arn't doing their jobs just because something doesn't work.
Their ability isn't the issue, your attitude is.
"In space all warriors are cold warriors" ----á General Chang-á Star Trek VI |
Thomas Abernathy
Beekeepers Anonymous
19
|
Posted - 2011.12.21 18:44:00 -
[13] - Quote
Hung TuLo wrote:I actually am a professional software quality control analyst.
How may of you in this thread can say that, how many of the players can say that. What do you really know about SQC?
It is virtually impossible to catch every single bug that is in a game this size. Its not possible
1. There are so many computer set-ups that need to be considered.
2. Different graphics cards that are used.
3. Networking issues to consider.
4. Different programing modules that need to be worked on on a daily basis.
5. New equipment that needs to be considered in their systems.
6. They release new code every six months that allow you to enjoy this game. We arn't talking 10 lines of code, we are talking 10's of thousands of lines of code that probably need to be modified.
7. Intigration processes.
8. characters that transfer from one server to other servers.
9. Localization issues.
10. patching issues and when it needs to happen.
11 Release issues.
12. Code upgrades.
13. Code migrations.
14. Petition requests and responses.
15. Server Load issues
That is a small list.
So, when you want to ***** and complain about the patches remember this,. There is alot more than what is going on that you can't see. They have a job just like you should have a job. They are doing their job to the best of their ability and are trying to be a professional as possible.
Don't assume they arn't doing their jobs just because something doesn't work.
Their ability isn't the issue, your attitude is.
Did you work for Microsoft by chance?
"Fighting CCD since 2139" |
Hung TuLo
Heavy Asset Relocation Inc
17
|
Posted - 2011.12.21 18:58:00 -
[14] - Quote
HAHAHA,
No I didn't mate but, the work for a SQCA is the same where ever you work. QC on games are different for QC on other companies software. But the USe of control is the same. There are standards that are adhered to. SOmetimes you have to make compromises. Do you stop a major piece of software from being implemented due to a very minor problem? no.
Everything is dependant upon the severity of the problem. Some things go out the door even when there are known issues. That you can't control.
When you are promised something you expect it right? Well when EVE tells you you are getting a release you better get it because 100% of your customers are expecting it. QC can only find so many problems in a timeframe. Even a smaller amount of those items can be fixed at a time. (Time Constriants)
It is easier and better to release something with a small amount of issues than it is to release nothing at all. IF you get a date of release and nothing is release what happenns to the thoughts of the players expecting the release. Opps EVE isn't reliable in their timeframes. That is worse than opps EVE gives us a release ya there are small bugs but we know it will get fixed.
"In space all warriors are cold warriors" ----á General Chang-á Star Trek VI |
War Kitten
Panda McLegion
382
|
Posted - 2011.12.21 20:04:00 -
[15] - Quote
Yeah CCP, test EVERYTHING before release.
There can't be more than what, 10 or 20 features and actions to verify right? Just run through them all real quick after every 1-hour downtime for patching.
This is my signature.-á There are many others like it, but this one is mine. |
Xolve
Intaki Armaments
Important Internet Spaceship League
279
|
Posted - 2011.12.21 20:09:00 -
[16] - Quote
Pillowtalk wrote:CCP you really gotta step it up a notch as far as quality control goes. You need to hire an ace who has been doing project management for 15 years or something.
I spent 6 hours last night reinstalling the Eve client because the patch broke my install.
You gotta get this under control or my return is gunna be short.
I got a better idea, how about we send CCP home for the holidays so they can enjoy whatever it is they do in the Winter in Iceland, and you go to CCP HQ and fix everything yourself. We will all be happy to forum-camp and shitpost it up about what a horrible job you're doing.
Or maybe you could appreciate the fact that they are still actively involved in making their game better and better every year to the best of their abilities while trying to satisfy as much of their playerbase as possible. Stop bitching.
Lady Spank for C&P Moderator.
|
Ai Shun
State War Academy
Caldari State
63
|
Posted - 2011.12.21 20:12:00 -
[17] - Quote
Hung TuLo wrote:I actually am a professional software quality control analyst.
How may of you in this thread can say that, how many of the players can say that. What do you really know about SQC?
It is virtually impossible to catch every single bug that is in a game this size. Its not possible
1. There are so many computer set-ups that need to be considered.
2. Different graphics cards that are used.
3. Networking issues to consider.
4. Different programing modules that need to be worked on on a daily basis.
5. New equipment that needs to be considered in their systems.
6. They release new code every six months that allow you to enjoy this game. We arn't talking 10 lines of code, we are talking 10's of thousands of lines of code that probably need to be modified.
7. Intigration processes.
8. characters that transfer from one server to other servers.
9. Localization issues.
10. patching issues and when it needs to happen.
11 Release issues.
12. Code upgrades.
13. Code migrations.
14. Petition requests and responses.
15. Server Load issues
That is a small list.
I'd recommend reading The Clean Coder by Uncle Bob. It is a good resource for being a true professional covering topics from TDD through to Estimations and Communication. And it is written conversationally, so it is a light, easy read as well.
Hung TuLo wrote:Don't assume they arn't doing their jobs just because something doesn't work.
Their ability isn't the issue, your attitude is.
I agree with you in principle on the core point; it is nigh on impossible to ensure your code will work on every single environment for any given circumstance. A bad memory chip that occasionally flakes out can **** everything up and it won't be your fault. A device driver, written by some company that mass produces cheap NICs can have subtle bug that will affect your software - but because your software is the visible face of their interaction with the PC they blame you.
What can however be done is to try and cover the edge cases. Take the UI reset problem. It has not happened to me yet. I don't know if this is a bug or not; but I have seen it reported quite a few times on the forums. (Marginal in terms of population, I expect) So, how long before it becomes useful to spend a few hours adding the ability to save/load the UI to a local XML file? Or storing the UI settings in a separate location on shutdown and comparing them to those locations on-load. And if they are different, prompt the end-user.
As to the second bit quoted, I agree.
Hung ToLo wrote:Everything is dependant upon the severity of the problem. Some things go out the door even when there are known issues. That you can't control.
That really does not sound very professional. You wittingly ship a defective product when it is within circumstances you can control? I would suggest you get your development team to communicate better with QA, to ensure they have proper unit tests and to make sure that everything passes before they even release it to QA. And you and your development team should be pushing back to management to ensure that expectations are met.
Honestly, I would much rather ship a week late than release a product I know is defective. How could I call myself a professional if I did not? |
Hung TuLo
Heavy Asset Relocation Inc
17
|
Posted - 2011.12.21 20:27:00 -
[18] - Quote
I do understand your point.
Depending on the severity and criticalness of the problem. You don't even thing of placing something into production. And yes you do have those meetings between QA and dev teams.
In the end QA sometimes does not have the "power or control" to sto something from going into production.
It mainly is the 80/20 law or the 90/10 law.
As long as 80% - 90% of the code is working as expected then a push to production is waranted. Once again that depends on the critical nature of the problem. In your example of the UI problem. If the UI was found to be working 95% of the time and the problem was minor. Should the entire push be stopped?
Most of the time. The answer to these things are not your regular QA folks or you dev folks. Its their managers that are answering to the CEO or other bigwigs that will make the ultimate decision. By and large the QA staff is doing their job.
Remember QA just reports the facts. The test the software and report problems, possible causes and possible ramifications.
QA does not cause the coding problems they find them.
Its those in the nosebleed seats that make the decisions.
"In space all warriors are cold warriors" ----á General Chang-á Star Trek VI |
Avid Bumhumper
Imperial Shipment
Amarr Empire
6
|
Posted - 2011.12.21 20:27:00 -
[19] - Quote
Hung TuLo wrote:I actually am a professional software quality control analyst.
How may of you in this thread can say that, how many of the players can say that. What do you really know about SQC?
It is virtually impossible to catch every single bug that is in a game this size. Its not possible
1. There are so many computer set-ups that need to be considered.
2. Different graphics cards that are used.
3. Networking issues to consider.
4. Different programing modules that need to be worked on on a daily basis.
5. New equipment that needs to be considered in their systems.
6. They release new code every six months that allow you to enjoy this game. We arn't talking 10 lines of code, we are talking 10's of thousands of lines of code that probably need to be modified.
7. Intigration processes.
8. characters that transfer from one server to other servers.
9. Localization issues.
10. patching issues and when it needs to happen.
11 Release issues.
12. Code upgrades.
13. Code migrations.
14. Petition requests and responses.
15. Server Load issues
That is a small list.
So, when you want to ***** and complain about the patches remember this,. There is alot more than what is going on that you can't see. They have a job just like you should have a job. They are doing their job to the best of their ability and are trying to be a professional as possible.
Don't assume they arn't doing their jobs just because something doesn't work.
Their ability isn't the issue, your attitude is.
And your response, if you really are what you claim, is predictible.
It may not even be your fault, companies in general have reached the point where it's no longer, how can I improve my customer service/app/whatever.
It's how can I squeeze more out of what I have, and how low are my customers expectations considering what they deal with daily..
If the other guy isn't doing the job either, we have nothing to worry about....
This is the new mindset......less bad == good enough. 
Not saying all companies have adopted this posture, but if you look around, you'll recgonize the attitude.....
|
Arctur Vallfar
Knights Adamant
14
|
Posted - 2011.12.21 20:33:00 -
[20] - Quote
Fixing bugs ain't like dusting crops, boy. |
RubyPorto
Profoundly Disturbed
RED.Legion
180
|
Posted - 2011.12.21 20:46:00 -
[21] - Quote
Avid Bumhumper wrote:And your response, if you really are what you claim, is predictible. It may not even be your fault, companies in general have reached the point where it's no longer, how can I improve my customer service/app/whatever. It's how can I squeeze more out of what I have, and how low are my customers expectations considering what they deal with daily.. If the other guy isn't doing the job either, we have nothing to worry about.... This is the new mindset......less bad == good enough. Not saying all companies have adopted this posture, but if you look around, you'll recgonize the attitude.....
Not quite. The attitude is "Given this fixed set of resources, what's the most important thing I can fix? Done. Given this fixed (now smaller) set of resources, what's the most important thing I can fix? Done." There are some important things to fix that are simply to hard to fix before release (and aren't worth delaying the release thus delaying the improvements the release brings), and some things that aren't that hard but are less important than other things that need fixing and thus don't make it in.
It boils down to an example of a knapsack problem, with unknown (but bounded) weights and unknown (but bounded) values. Try to figure out how much value (bugfixes) you can fit into a knapsack within a certain weight (resources: Clock Time, Dev Time, Testing time, Money, etc.). |
RubyPorto
Profoundly Disturbed
RED.Legion
180
|
Posted - 2011.12.21 20:46:00 -
[22] - Quote
FORUMS R BAD at Foruming, mmmkay? |
Ai Shun
State War Academy
Caldari State
63
|
Posted - 2011.12.21 20:50:00 -
[23] - Quote
Hung TuLo wrote:I do understand your point.
Depending on the severity and criticalness of the problem. You don't even thing of placing something into production. And yes you do have those meetings between QA and dev teams.
In the end QA sometimes does not have the "power or control" to sto something from going into production.
It mainly is the 80/20 law or the 90/10 law.
As long as 80% - 90% of the code is working as expected then a push to production is waranted. Once again that depends on the critical nature of the problem. In your example of the UI problem. If the UI was found to be working 95% of the time and the problem was minor. Should the entire push be stopped?
Most of the time. The answer to these things are not your regular QA folks or you dev folks. Its their managers that are answering to the CEO or other bigwigs that will make the ultimate decision. By and large the QA staff is doing their job.
Remember QA just reports the facts. The test the software and report problems, possible causes and possible ramifications.
QA does not cause the coding problems they find them.
Its those in the nosebleed seats that make the decisions.
If you can, read that book. It is mainly for developers, but it changed my mind about how the process should work. I know we can't always deal with ideal scenarios, but a lot of the up-front should come from development; not QA.
Seriously. I strongly recommend that book. |
Atlas Oracle
Colossus Enterprises
3
|
Posted - 2011.12.21 21:00:00 -
[24] - Quote
Hung TuLo wrote:I actually am a professional software quality control analyst.
<...>
Their ability isn't the issue, your attitude is.
you're a pathetic oxygen thief
|
Sycho Pathic
Republic Military School
Minmatar Republic
8
|
Posted - 2011.12.21 21:58:00 -
[25] - Quote
Anything more complicated than a bubble-sort follows that pattern.
Frankly, I'm rather impressed with how well CCP manages EVE.
|
Corina Jarr
Spazzoid Enterprises
Purpose Built
107
|
Posted - 2011.12.21 22:24:00 -
[26] - Quote
I wonder how many of the people who complain about the patching actually submit complete bug reports.
That is, highly detailed down, including system information, what you did to get the bug, how often it occurs, and your EVE settings.
Including troubleshooting attempts can help too (and the results of said attempts). |
Ranger 1
Ranger Corp
572
|
Posted - 2011.12.21 22:30:00 -
[27] - Quote
Ai Shun wrote:Hung TuLo wrote:I do understand your point.
Depending on the severity and criticalness of the problem. You don't even thing of placing something into production. And yes you do have those meetings between QA and dev teams.
In the end QA sometimes does not have the "power or control" to sto something from going into production.
It mainly is the 80/20 law or the 90/10 law.
As long as 80% - 90% of the code is working as expected then a push to production is waranted. Once again that depends on the critical nature of the problem. In your example of the UI problem. If the UI was found to be working 95% of the time and the problem was minor. Should the entire push be stopped?
Most of the time. The answer to these things are not your regular QA folks or you dev folks. Its their managers that are answering to the CEO or other bigwigs that will make the ultimate decision. By and large the QA staff is doing their job.
Remember QA just reports the facts. The test the software and report problems, possible causes and possible ramifications.
QA does not cause the coding problems they find them.
Its those in the nosebleed seats that make the decisions. If you can, read that book. It is mainly for developers, but it changed my mind about how the process should work. I know we can't always deal with ideal scenarios, but a lot of the up-front should come from development; not QA. Seriously. I strongly recommend that book.
I think what it basically boils down to is that if a release was held up until ALL bugs (regardless of severity) were squshed, it would never be released... especially when discussing software as unique and intricate as EVE is.
Much of the code in EVE is very unique... completely uncharted ground even for companies that have tried for years to come up with something similar, and failed.
Given the persistent nature of the environment and the countless variations of end user interactions with the software, plus the fact that (although they have made strides in this direction) there really is no effective way to stress test their code under normal use conditions prior to release, you end up with a lot of patches after the fact. It is a reality of the situation, not a failure in processes.
You can have most other types of software completely isolated on test platforms (word processors, music players, cooking programs, most other multi player games, what have you), fully test all possible uses with the maximum number of simultaneous users possible, and still have a good chance of missing something.
You can't do that with EVE.
Many of the things that make EVE unique and special to us have this inevitable downside. I think they've done a pretty fair job of minimizing that downside and implementing needed bug fixes in a timely manner.
Perfect code is a worthy goal, just (in this case) not a very realistic expectation.
Revenge should not stop at the ship!
It's not so much a mission statement,-áit's more like a family motto. |
RubyPorto
Profoundly Disturbed
RED.Legion
181
|
Posted - 2011.12.21 22:33:00 -
[28] - Quote
Corina Jarr wrote:I wonder how many of the people who complain about the patching actually submit complete bug reports.
That is, highly detailed down, including system information, what you did to get the bug, how often it occurs, and your EVE settings.
Including troubleshooting attempts can help too (and the results of said attempts).
Probably very few, though (and this is coming from a Mac user)
CCP doesn't exactly make the process easy (at least for the Mac)
One way of thinking is that users should not be required to help fix software that they're paying for (I don't agree with this point)
[*] Neither of the 2 main bugs affecting the Mac client produce crashlogs without special logging set up (and one doesn't produce anything even then) |
Liam Mirren
38
|
Posted - 2011.12.21 22:43:00 -
[29] - Quote
Hung TuLo wrote:I actually am a professional software quality control analyst.
How may of you in this thread can say that, how many of the players can say that. What do you really know about SQC?
It is virtually impossible to catch every single bug that is in a game this size. Its not possible
1. There are so many computer set-ups that need to be considered.
2. Different graphics cards that are used.
3. Networking issues to consider.
4. Different programing modules that need to be worked on on a daily basis.
5. New equipment that needs to be considered in their systems.
6. They release new code every six months that allow you to enjoy this game. We arn't talking 10 lines of code, we are talking 10's of thousands of lines of code that probably need to be modified.
7. Intigration processes.
8. characters that transfer from one server to other servers.
9. Localization issues.
10. patching issues and when it needs to happen.
11 Release issues.
12. Code upgrades.
13. Code migrations.
14. Petition requests and responses.
15. Server Load issues
That is a small list.
So, when you want to ***** and complain about the patches remember this,. There is alot more than what is going on that you can't see. They have a job just like you should have a job. They are doing their job to the best of their ability and are trying to be a professional as possible.
Don't assume they arn't doing their jobs just because something doesn't work.
Their ability isn't the issue, your attitude is.
Your reaction makes sense from a personal/DEV point of view, you can't (and shouldn't) blame specific DEVs or coders for issues. But you SHOULD blame the software company as a whole (management) for creating a situation where churning out less than desirable content/expansions/patches is inevitable or, worse, expected practise.
If it's worth doing, it's worth doing right. |
Ai Shun
State War Academy
Caldari State
64
|
Posted - 2011.12.21 22:51:00 -
[30] - Quote
Ranger 1 wrote:Perfect code is a worthy goal, just (in this case) not a very realistic expectation.
Most of my C / C++ development experience comes from an ICS solution and IDS solution. (About 7 years, roughly from 2001 to 2008) Prior to that it was medical information systems and some R&D type work. So yeah, I've worked in environments where there were complex customer environments and I know our QA team bent over backwards to try and replicate the problems encountered by, for example, a chap out in the Outback with a sattelite setup that wanted to share his connection with his household while his main system was running Windows ME ...
You can imagine ...
But, I've changed my perspective after reading that book. While I can acknowledge that perfection is impossible; there are several mechanisms that developers can employ to not only reduce the risk but also to ensure that if the inevitable happens the system is capable of dealing with it. Yes, it is complicated. Yes, it is difficult.
But software developers, just like any other professional be that a doctor or a lawyer or whatever, has to have the same professionalism. What happens if a doctor comes back after a week and says: "Hey, you know. I ****** up a bit. I was meant to remove your appendix, but I took your nutsac instead. My bad. It was a bug. Let me patch that for you ..."
Everything nowadays runs off software. We trust software with almost every aspect of our lives. And getting that level of perfection is ... well. It should be a goal. Complexity should not be used as an excuse.
That said, software development is still a relatively new discipline. We're inventing better methodologies, structures and designs every day. EVE is going on 7 or 8 years old now in terms of release, the code base must be even older! And while I suspect the code base has been refactored in that timeframe, I suspect there is still a lot of "old" knowledge and structure in there. I'm willing to cut them a lot of slack in terms of bugs because I have not encountered ONE yet in my interaction with EVE Online.
I still think though that developers (generally) should be the ones that takes responsibility for writing their code using pair programming, test driven development, solid unit testing and so forth to take professional accountability for what they do. To ensure that what goes to QA is ******* bullet proof. And if QA can poke a hole in it, a developer should be mortified.
Read the book if you're in a development environment. It shouldn't take you more than an evening to work through and it's a good methodology / philosophy piece. I'm taking bits of it and pushing my teams here to start working more that way. It makes our clients a lot happier
|
| |
|
| Pages: [1] 2 :: one page |
| First page | Previous page | Next page | Last page |