Everyone who has and ever will buy Minecraft will almost definitely spend most of their time in single player. Only some people play multiplayer, and he's pandering to the minority. Doing something like fixing leave despawn would help *EVERYONE* instead of just the minority that plays SMP. Notch has his priorities messed up >.>
Wrong.
Everyone who starts Minecraft will spend all there time in Single player.
Then they branch of about 50/50 to either or.
Before this update there were a lot of sour kids in the SMP discussion thread.
Now that it's out it seems all the single player kids are sour.
It's really kind of sad.
New? That's not new. Not new at all. Lonsdaleite has been known of since the late 60s. It's also hard to claim it's the "hardest substance on Earth" since it does not in fact occur naturally on the Earth. It's brought here due to meteorite impacts. You can find it, but it is exceedingly rare, and won't appear in any quantities which would allow it to be used for anything significant.
One big flat map.
The World generates randomly around you as you find it.
(You'll notice when you load a world it has a file size next to it, the more you explore, the higher this number will become.)
To Stuck:
1. Actually, it has everything to do with the method he's creating with. In waterfall you would make a feature. Test the feature. Polish the feature. Cry when the feature didn't make the final cut. In agile, he's making it. Looking to see it WORKS. Then putting it onto the live server so people can find bugs/ provide feedback.
2. No, in depth testing takes a long time, if you want to actually find anything. Fixing a bug can take as little as 5 minutes depending. Obviously, sometimes it's not quite that simple, but in the long run, it saves time.
3. Agile. He Releases an update weekly. He's doing that. (which is pretty amazing, i might add)
4.And your making yourself look like an ignorant jackass. I wonder which is worse?
In a way you're right, but i still don't agree with how hes using sprint anyway, he's not exactly even on a set timetable yet, he delayed a release just because he forgot his key to release the update, give me a break. If he wants to properly utilize it he should set a start and end date and if the end data arrives you make sure everything compiles and runs and then throw it out, if it doesn't you cut what isn't finished and make it run.
I'm sure he 'basically' tests it, but in recent updates its become sorta clear that alot of bugs are getting called out that he never even realizes even though they're a pretty basic part of gameplay, game crashes, things not breaking and such. Realistically he should take atleast 30 minutes to run around and test things a bit before he sends an update out, make sure nothing major and quick to pinpoint is broken, it takes more effort to report it from a third person and then fix it and slate it for the next release then it does to fix it when its broken in most cases, or diagnose it as a big problem that has to be disabled(he did that with the leaves, and it makes sense, just not always.)
I'm sure hes working on it, I'm not saying he's intentionally screwing releases up, i think he just needs better methods to handle releases and planning, his blog posts definitely sound like hes getting overwhelmed at having to be.. more organized now(he should have been organized by himself.)
Honestly, I think it'll get more "streamlined" and organized soon.
We have to keep in mind, right now, he probably doesn't want to update at all.
He's moving into an office, hiring workers, and everything is pretty hectic.
The reason he's doing it is becuase on top of all that, he wants to be able to keep us happy and update it.
Once everyones in that office. and actually doing agile. Everything will come out harder, better, faster, stronger.
(right now the only agile part of it really is the releases and costumer collab.)
A HUGE part of agile is the communication, and really, until he gets his other programmers and animators and etc. etc. in that room with him to bounce things back and forth, it's going to be hectic.
...
We. Are. Testing. It.
Implementation is when he puts it live.
And like I said in a previous post:
The chances of he himself finding that SOMETIMES leaves make infinite loops that corrupt data? Slim.
The leaves are a one and one case example, the point was about the apparent inability to test product thoroughly enough before releasing a test version. Notch put the update up earlier and anyone that downloaded it, had their game crash, it flat out did not run on ANYONE'S computer. Ontop of that most of the features that are 'bugged or broken' in SMP right now, aren't just a 'this person in this case' thing, they're pretty obvious, like mobs flat out not showing up if your difficulty is set to peaceful even though they're actually there.
As for implementation, read my comment about the car, you don't send a program out for testing that flat out does not run, it'd be better to put up with whiners and take another week fixing it then to just throw out a bugged version(he had to scramble to fix it and make a second release, which I'm glad he did in a pretty timely fashion).
But that's the thing.
You can't "wait another week" with agile sprints.
It destroys the methodology and brings it to waterfall.
And as for the implementation of the not working game:
Blizzard does that pretty much every patch, and they're a fortune 500 company with hundreds of workers.
It's pretty common.
He does test his product before sending it. He's not dumb enough not to.
But it's not the long, intricate testing that finds the bugs that people notice.
It's quick "Does this do what I wanted to?" "Sweet, moving on"
Kind of testing.
Then he gives it to us and we do the in depth part of it.
-You're wrong.
-It's a -payed- Alpha, its the same as getting an invitation to a CLOSED alpha, in that your invitation costs dollars.
-Testers don't fix blatantly obvious bugs, they provide a test platform to find harder to find bugs, ones that aren't seen at all by the coder running the compiled program, they are a result of all the changes working together to create unintended behavior.
-It's implemented poorly and that's why it breaks, i understand -why- Notch disabled the leaf thing, but really there's no real excuse for releasing an update that flat out corrupts -everyone's files- as happened before, either that was a server goof or he flat out never even ran the game after he compiled it. You don't build a new car and push it onto a truck and say, take it to the test facility, you make sure it starts first.
-Tested by whom? I still don't even get what that sentence implies, its obviously NOT tested if you're sticking up for the fact that -we- are supposed to test it. Can you please make up your mind before writing a two word sentence? Your apparent lack of knowledge is just appalling.
...
We. Are. Testing. It.
Implementation is when he puts it live.
And like I said in a previous post:
The chances of he himself finding that SOMETIMES leaves make infinite loops that corrupt data? Slim.
About that last part:
The difference here and from the 45K failed mmos is most of the MMOs arent playable when they have the hype.
It's just everyone thinking its going to be awesome.
And then finding out "oh, this is just another lolgrind with one extra feature."
And..
Minecraft IS awesome.
Alpha and Beta stages only differ in the fact that during Alpha your actively introducing new features. Adding new features is known to generally add bugs at the same time. It doesn't mean that the developer can't do any form of testing before releasing it to the public. Developers should be doing the same amount of in house testing during both stages. Its just that your more likely to spot bugs during Alpha as theoretically there should be more present during the Alpha stage.
Btw when posting please use sentences(Ones larger than 2-3 words each).
Wrong.
In WATERFALL thats how it works.
This is agile and scrum.
And I believe FDD?
And who says he doesn't test?
Of course he's not going to do an extensive 5 hour test. Thats what were here for.
He goes in. Makes sure it does what it was coded to do.
Leaves and moves to the next feature.
Rinse Repeat.
Do you know why he removed leaves?
Because SOMETIMES. For SOME people it caused fatal crashes.
The chances of him getting that to work in his bit of testing by himself? Slim.
The more time he spends testing, the less time he spends making features.
You are far more likely in a normal setup to have people to test the game during the Beta stage rather than the Alpha stage, so in a normal Development Cycle you have to rely more on in house testing during the Alpha stage.
Btw when posting please use sentences(Ones larger than 2-3 words each).
/facepalm.
OPEN. ALPHA.
And I'll make my sentences.
As.
Long.
As.
I.
Please.
Things don't get tested before you put them out. BECAUSE WE ARE THE TESTERS.
You do realise that people making games normally test stuff before they send there game to testers? Due to the fact that if they didn't it would take them far longer to find and fix all the bugs.
Testers are meant to be the Last line of defence. They are not meant to be the first. The first line of defence is meant to be the team programming the game.
Your wrong.
It's Open Alpha.
You write it.
It's implemented.
It's tested.
0
But the main problem they'd run into in bringing it to platform specific OS is time allocation to each OS.
You'd have to make this work in Windows.
Then go back and do it for Mac.
And that would, in turn double the time taken to create updates and such. And more than likely complicate it.
I think Notch mainly uses Java because he understands it very well, also. : /
0
Wrong.
Everyone who starts Minecraft will spend all there time in Single player.
Then they branch of about 50/50 to either or.
Before this update there were a lot of sour kids in the SMP discussion thread.
Now that it's out it seems all the single player kids are sour.
It's really kind of sad.
0
Christmas Update:
METOERS B CRASHING INTO UR MAP.
...
That would be intense.
And awesome.
0
The World generates randomly around you as you find it.
(You'll notice when you load a world it has a file size next to it, the more you explore, the higher this number will become.)
0
1. Actually, it has everything to do with the method he's creating with. In waterfall you would make a feature. Test the feature. Polish the feature. Cry when the feature didn't make the final cut. In agile, he's making it. Looking to see it WORKS. Then putting it onto the live server so people can find bugs/ provide feedback.
2. No, in depth testing takes a long time, if you want to actually find anything. Fixing a bug can take as little as 5 minutes depending. Obviously, sometimes it's not quite that simple, but in the long run, it saves time.
3. Agile. He Releases an update weekly. He's doing that. (which is pretty amazing, i might add)
4.And your making yourself look like an ignorant jackass. I wonder which is worse?
0
Honestly, I think it'll get more "streamlined" and organized soon.
We have to keep in mind, right now, he probably doesn't want to update at all.
He's moving into an office, hiring workers, and everything is pretty hectic.
The reason he's doing it is becuase on top of all that, he wants to be able to keep us happy and update it.
Once everyones in that office. and actually doing agile. Everything will come out harder, better, faster, stronger.
(right now the only agile part of it really is the releases and costumer collab.)
A HUGE part of agile is the communication, and really, until he gets his other programmers and animators and etc. etc. in that room with him to bounce things back and forth, it's going to be hectic.
0
But that's the thing.
You can't "wait another week" with agile sprints.
It destroys the methodology and brings it to waterfall.
And as for the implementation of the not working game:
Blizzard does that pretty much every patch, and they're a fortune 500 company with hundreds of workers.
It's pretty common.
He does test his product before sending it. He's not dumb enough not to.
But it's not the long, intricate testing that finds the bugs that people notice.
It's quick "Does this do what I wanted to?" "Sweet, moving on"
Kind of testing.
Then he gives it to us and we do the in depth part of it.
0
...
We. Are. Testing. It.
Implementation is when he puts it live.
And like I said in a previous post:
The chances of he himself finding that SOMETIMES leaves make infinite loops that corrupt data? Slim.
0
The difference here and from the 45K failed mmos is most of the MMOs arent playable when they have the hype.
It's just everyone thinking its going to be awesome.
And then finding out "oh, this is just another lolgrind with one extra feature."
And..
Minecraft IS awesome.
0
Doom.
Wolfenstien. <3
0
Wrong.
In WATERFALL thats how it works.
This is agile and scrum.
And I believe FDD?
And who says he doesn't test?
Of course he's not going to do an extensive 5 hour test. Thats what were here for.
He goes in. Makes sure it does what it was coded to do.
Leaves and moves to the next feature.
Rinse Repeat.
Do you know why he removed leaves?
Because SOMETIMES. For SOME people it caused fatal crashes.
The chances of him getting that to work in his bit of testing by himself? Slim.
The more time he spends testing, the less time he spends making features.
/facepalm.
OPEN. ALPHA.
And I'll make my sentences.
As.
Long.
As.
I.
Please.
0
Your wrong.
It's Open Alpha.
You write it.
It's implemented.
It's tested.
0
Open Alpha.
What does this mean?
Things get put out on the due date. DONE OR NOT.
Things don't get tested before you put them out. BECAUSE WE ARE THE TESTERS.
You guys complain WAAAAY to much over the cost of 2 packs of cigarettes.
0
Creepers Behind You!
0
If that becomes a shirt, I'm getting it.