steinarmspreeb18_ESO wrote: »I was just wondering since there is a lot of debate about what is getting fixed and community is complaining that they need to wait for weeks until their skills behave like they should or broken quests and latency issues etc etc
How about publishing your active development backlog along with enhancements and allow the community to vote on your prioritization ? After all they are the real business owner since you are out of business if they give up.
Simply, all active accounts can vote each month or what ever makes the most sense, and have a visibility on their status open/in progress/in test/etc...
I think you will earn some respect by working closer with the community
What do you think?
In theory this sounds good (as in, it's a nice idea to think you'd have some control over stuff), but in practice I'd never ever want it.
I would wager a very, very small percentage of players have any programming, or project management experience. They may know what they'd prefer fixed first, but they don't have any idea how long it will take to get said thing fixed, how many people at the office are capable of working on said thing (are familiar with that specific bit of code), or how the systems work together on the back end of things. Maybe people really want thing A fixed.. but thing A depends upon thing B, which players don't really care about, or we don't hear about because it's not directly shown to players.
Basically, gamers just don't know enough about the actual business to be able to make an educated decision about what should be fixed first given all available factors.
ers101284b14_ESO wrote: »In theory this sounds good (as in, it's a nice idea to think you'd have some control over stuff), but in practice I'd never ever want it.
I would wager a very, very small percentage of players have any programming, or project management experience. They may know what they'd prefer fixed first, but they don't have any idea how long it will take to get said thing fixed, how many people at the office are capable of working on said thing (are familiar with that specific bit of code), or how the systems work together on the back end of things. Maybe people really want thing A fixed.. but thing A depends upon thing B, which players don't really care about, or we don't hear about because it's not directly shown to players.
Basically, gamers just don't know enough about the actual business to be able to make an educated decision about what should be fixed first given all available factors.
Really? Cause according to the people on Facebook and the forums it's super simple and would only take 10 minutes to fix. They would know since their GEDs are the pride of their trailer park.
ers101284b14_ESO wrote: »In theory this sounds good (as in, it's a nice idea to think you'd have some control over stuff), but in practice I'd never ever want it.
I would wager a very, very small percentage of players have any programming, or project management experience. They may know what they'd prefer fixed first, but they don't have any idea how long it will take to get said thing fixed, how many people at the office are capable of working on said thing (are familiar with that specific bit of code), or how the systems work together on the back end of things. Maybe people really want thing A fixed.. but thing A depends upon thing B, which players don't really care about, or we don't hear about because it's not directly shown to players.
Basically, gamers just don't know enough about the actual business to be able to make an educated decision about what should be fixed first given all available factors.
Really? Cause according to the people on Facebook and the forums it's super simple and would only take 10 minutes to fix. They would know since their GEDs are the pride of their trailer park.
Haha. I have to admit.. I use to kinda be one of those "well gee, how long could that actually take.. it's a simple change!" types.. and then I started dating a programmer. It is simply amazing how much work goes into things; how even in the same programming language, two different people coding one thing can do it completely different ways... to the extent that only the original coder only really knows what's going on. Yeah, there are some basic guidelines to follow with any big project.. but a lot of time if the original coder leaves, whoever replaces them has to spend a good deal of time just looking at how the first guy did it to even get a handle on how to begin to fix it. Much respect for developers in general now... which has earned me the title of "fanboy" on many a forum.
steinarmspreeb18_ESO wrote: »I was just wondering since there is a lot of debate about what is getting fixed and community is complaining that they need to wait for weeks until their skills behave like they should or broken quests and latency issues etc etc
How about publishing your active development backlog along with enhancements and allow the community to vote on your prioritization ? After all they are the real business owner since you are out of business if they give up.
Simply, all active accounts can vote each month or what ever makes the most sense, and have a visibility on their status open/in progress/in test/etc...
I think you will earn some respect by working closer with the community
What do you think?
It's a good idea in theory but..let's say they vote to fix "Class Balance". Many don't realise you can't fix such a thing in a day or a week...
People don't have a clue how to fix it, what to change etc. It's like this with many things in programming development. It's much harder than all the players realise, they don't appreciate anything at all.
ers101284b14_ESO wrote: »ers101284b14_ESO wrote: »In theory this sounds good (as in, it's a nice idea to think you'd have some control over stuff), but in practice I'd never ever want it.
I would wager a very, very small percentage of players have any programming, or project management experience. They may know what they'd prefer fixed first, but they don't have any idea how long it will take to get said thing fixed, how many people at the office are capable of working on said thing (are familiar with that specific bit of code), or how the systems work together on the back end of things. Maybe people really want thing A fixed.. but thing A depends upon thing B, which players don't really care about, or we don't hear about because it's not directly shown to players.
Basically, gamers just don't know enough about the actual business to be able to make an educated decision about what should be fixed first given all available factors.
Really? Cause according to the people on Facebook and the forums it's super simple and would only take 10 minutes to fix. They would know since their GEDs are the pride of their trailer park.
Haha. I have to admit.. I use to kinda be one of those "well gee, how long could that actually take.. it's a simple change!" types.. and then I started dating a programmer. It is simply amazing how much work goes into things; how even in the same programming language, two different people coding one thing can do it completely different ways... to the extent that only the original coder only really knows what's going on. Yeah, there are some basic guidelines to follow with any big project.. but a lot of time if the original coder leaves, whoever replaces them has to spend a good deal of time just looking at how the first guy did it to even get a handle on how to begin to fix it. Much respect for developers in general now... which has earned me the title of "fanboy" on many a forum.
Oh I know. I did some basic programming for college and man I still don't get it. And seriously to code this game would probably be around 10,000 single spaced pages of a book. And something on line 68985547 could be screwing up something on line 367. Not to mention you put a wrong , somewhere and everything goes to hell. Good luck finding the missing ,
Most of the problems with this game have nothing to do with code. You can't debug bad design.ers101284b14_ESO wrote: »ers101284b14_ESO wrote: »In theory this sounds good (as in, it's a nice idea to think you'd have some control over stuff), but in practice I'd never ever want it.
I would wager a very, very small percentage of players have any programming, or project management experience. They may know what they'd prefer fixed first, but they don't have any idea how long it will take to get said thing fixed, how many people at the office are capable of working on said thing (are familiar with that specific bit of code), or how the systems work together on the back end of things. Maybe people really want thing A fixed.. but thing A depends upon thing B, which players don't really care about, or we don't hear about because it's not directly shown to players.
Basically, gamers just don't know enough about the actual business to be able to make an educated decision about what should be fixed first given all available factors.
Really? Cause according to the people on Facebook and the forums it's super simple and would only take 10 minutes to fix. They would know since their GEDs are the pride of their trailer park.
Haha. I have to admit.. I use to kinda be one of those "well gee, how long could that actually take.. it's a simple change!" types.. and then I started dating a programmer. It is simply amazing how much work goes into things; how even in the same programming language, two different people coding one thing can do it completely different ways... to the extent that only the original coder only really knows what's going on. Yeah, there are some basic guidelines to follow with any big project.. but a lot of time if the original coder leaves, whoever replaces them has to spend a good deal of time just looking at how the first guy did it to even get a handle on how to begin to fix it. Much respect for developers in general now... which has earned me the title of "fanboy" on many a forum.
Oh I know. I did some basic programming for college and man I still don't get it. And seriously to code this game would probably be around 10,000 single spaced pages of a book. And something on line 68985547 could be screwing up something on line 367. Not to mention you put a wrong , somewhere and everything goes to hell. Good luck finding the missing ,
steinarmspreeb18_ESO wrote: »ers101284b14_ESO wrote: »ers101284b14_ESO wrote: »In theory this sounds good (as in, it's a nice idea to think you'd have some control over stuff), but in practice I'd never ever want it.
I would wager a very, very small percentage of players have any programming, or project management experience. They may know what they'd prefer fixed first, but they don't have any idea how long it will take to get said thing fixed, how many people at the office are capable of working on said thing (are familiar with that specific bit of code), or how the systems work together on the back end of things. Maybe people really want thing A fixed.. but thing A depends upon thing B, which players don't really care about, or we don't hear about because it's not directly shown to players.
Basically, gamers just don't know enough about the actual business to be able to make an educated decision about what should be fixed first given all available factors.
Really? Cause according to the people on Facebook and the forums it's super simple and would only take 10 minutes to fix. They would know since their GEDs are the pride of their trailer park.
Haha. I have to admit.. I use to kinda be one of those "well gee, how long could that actually take.. it's a simple change!" types.. and then I started dating a programmer. It is simply amazing how much work goes into things; how even in the same programming language, two different people coding one thing can do it completely different ways... to the extent that only the original coder only really knows what's going on. Yeah, there are some basic guidelines to follow with any big project.. but a lot of time if the original coder leaves, whoever replaces them has to spend a good deal of time just looking at how the first guy did it to even get a handle on how to begin to fix it. Much respect for developers in general now... which has earned me the title of "fanboy" on many a forum.
Oh I know. I did some basic programming for college and man I still don't get it. And seriously to code this game would probably be around 10,000 single spaced pages of a book. And something on line 68985547 could be screwing up something on line 367. Not to mention you put a wrong , somewhere and everything goes to hell. Good luck finding the missing ,
I'm pretty sure they have developers with more training than your basic programming course .. or I at least hope so
In theory this sounds good (as in, it's a nice idea to think you'd have some control over stuff), but in practice I'd never ever want it.
I would wager a very, very small percentage of players have any programming, or project management experience. They may know what they'd prefer fixed first, but they don't have any idea how long it will take to get said thing fixed, how many people at the office are capable of working on said thing (are familiar with that specific bit of code), or how the systems work together on the back end of things. Maybe people really want thing A fixed.. but thing A depends upon thing B, which players don't really care about, or we don't hear about because it's not directly shown to players.
Basically, gamers just don't know enough about the actual business to be able to make an educated decision about what should be fixed first given all available factors.
ers101284b14_ESO wrote: »ers101284b14_ESO wrote: »In theory this sounds good (as in, it's a nice idea to think you'd have some control over stuff), but in practice I'd never ever want it.
I would wager a very, very small percentage of players have any programming, or project management experience. They may know what they'd prefer fixed first, but they don't have any idea how long it will take to get said thing fixed, how many people at the office are capable of working on said thing (are familiar with that specific bit of code), or how the systems work together on the back end of things. Maybe people really want thing A fixed.. but thing A depends upon thing B, which players don't really care about, or we don't hear about because it's not directly shown to players.
Basically, gamers just don't know enough about the actual business to be able to make an educated decision about what should be fixed first given all available factors.
Really? Cause according to the people on Facebook and the forums it's super simple and would only take 10 minutes to fix. They would know since their GEDs are the pride of their trailer park.
Haha. I have to admit.. I use to kinda be one of those "well gee, how long could that actually take.. it's a simple change!" types.. and then I started dating a programmer. It is simply amazing how much work goes into things; how even in the same programming language, two different people coding one thing can do it completely different ways... to the extent that only the original coder only really knows what's going on. Yeah, there are some basic guidelines to follow with any big project.. but a lot of time if the original coder leaves, whoever replaces them has to spend a good deal of time just looking at how the first guy did it to even get a handle on how to begin to fix it. Much respect for developers in general now... which has earned me the title of "fanboy" on many a forum.
Oh I know. I did some basic programming for college and man I still don't get it. And seriously to code this game would probably be around 10,000 single spaced pages of a book. And something on line 68985547 could be screwing up something on line 367. Not to mention you put a wrong , somewhere and everything goes to hell. Good luck finding the missing ,
ers101284b14_ESO wrote: »steinarmspreeb18_ESO wrote: »ers101284b14_ESO wrote: »ers101284b14_ESO wrote: »In theory this sounds good (as in, it's a nice idea to think you'd have some control over stuff), but in practice I'd never ever want it.
I would wager a very, very small percentage of players have any programming, or project management experience. They may know what they'd prefer fixed first, but they don't have any idea how long it will take to get said thing fixed, how many people at the office are capable of working on said thing (are familiar with that specific bit of code), or how the systems work together on the back end of things. Maybe people really want thing A fixed.. but thing A depends upon thing B, which players don't really care about, or we don't hear about because it's not directly shown to players.
Basically, gamers just don't know enough about the actual business to be able to make an educated decision about what should be fixed first given all available factors.
Really? Cause according to the people on Facebook and the forums it's super simple and would only take 10 minutes to fix. They would know since their GEDs are the pride of their trailer park.
Haha. I have to admit.. I use to kinda be one of those "well gee, how long could that actually take.. it's a simple change!" types.. and then I started dating a programmer. It is simply amazing how much work goes into things; how even in the same programming language, two different people coding one thing can do it completely different ways... to the extent that only the original coder only really knows what's going on. Yeah, there are some basic guidelines to follow with any big project.. but a lot of time if the original coder leaves, whoever replaces them has to spend a good deal of time just looking at how the first guy did it to even get a handle on how to begin to fix it. Much respect for developers in general now... which has earned me the title of "fanboy" on many a forum.
Oh I know. I did some basic programming for college and man I still don't get it. And seriously to code this game would probably be around 10,000 single spaced pages of a book. And something on line 68985547 could be screwing up something on line 367. Not to mention you put a wrong , somewhere and everything goes to hell. Good luck finding the missing ,
I'm pretty sure they have developers with more training than your basic programming course .. or I at least hope so
I hope so too. But the fact is there are still so many lines of code and the people coding it are still human. Humans make mistakes.
Lets put it this way, this is Vanilla WoW's programming without any expansions or anything. Imagine having to search through all that to find what is messing with what. Any line can interact and screw up any other line.
http://www.amazon.com/World-Warcraft-Programming-Reference-Creating/dp/0470229810
steinarmspreeb18_ESO wrote: »In theory this sounds good (as in, it's a nice idea to think you'd have some control over stuff), but in practice I'd never ever want it.
I would wager a very, very small percentage of players have any programming, or project management experience. They may know what they'd prefer fixed first, but they don't have any idea how long it will take to get said thing fixed, how many people at the office are capable of working on said thing (are familiar with that specific bit of code), or how the systems work together on the back end of things. Maybe people really want thing A fixed.. but thing A depends upon thing B, which players don't really care about, or we don't hear about because it's not directly shown to players.
Basically, gamers just don't know enough about the actual business to be able to make an educated decision about what should be fixed first given all available factors.
So your saying that all players need to have programming or project management experience to be able to understand the implications of voting on an issue ?
That's just nonsense.
There are many ways to implement this, they could start by having a single development group assigned to the "Community backlog" ..
steinarmspreeb18_ESO wrote: »In theory this sounds good (as in, it's a nice idea to think you'd have some control over stuff), but in practice I'd never ever want it.
I would wager a very, very small percentage of players have any programming, or project management experience. They may know what they'd prefer fixed first, but they don't have any idea how long it will take to get said thing fixed, how many people at the office are capable of working on said thing (are familiar with that specific bit of code), or how the systems work together on the back end of things. Maybe people really want thing A fixed.. but thing A depends upon thing B, which players don't really care about, or we don't hear about because it's not directly shown to players.
Basically, gamers just don't know enough about the actual business to be able to make an educated decision about what should be fixed first given all available factors.
So your saying that all players need to have programming or project management experience to be able to understand the implications of voting on an issue ?
That's just nonsense.
There are many ways to implement this, they could start by having a single development group assigned to the "Community backlog" ..
dennis.schmelzleb16_ESO wrote: »They can just reveal something like their weekly scrum meeting.
What they have done.
What problems did they encounter.
What are they going to do next (if finished with their sprint backlog.
Then people can vote on the next backlog.
No timeframe votes, just what should be done next.