On February 11 2020 02:27 Mohdoo wrote: Happy's streak was bound to end at some point and of course it would be an orc. Happy probably just rolled his eyes after losing. It is impossible to appreciably improve when you win every single game.
On the other hand, Happy's dominance has been amazing for the Euro scene. Hawk, Cash and Foggy have all been appreciably improving in the past 3 months and it has clearly had a lot to do with Happy. Having this unbeatable, mighty opponent you run into in every tournament makes you either adapt or be irrelevant. All 3 of them have had some juicy fucking series vs Happy that always seem to go Happy's way. But they've been getting close. Losing 2-3 is not the same as losing 3-0. They are getting there. I'd love to see Cash, Hawk and Foggy all in the next WGL.
As for Reforged graphics: Still complete ass. Many fights I simply can't track to nearly the detail I used to. Part of it is that me coming from years of competitive play, there is a lot I am paying attention to. Sure, I get the general impression of who is winning a fight, but that is not nearly the whole story. There is so much nuance that I am used to focusing on and appreciating. I can't do that anymore on B2W's stream. It is significantly less stimulating because I am absorbing so much less information. I just don't see what I used to see.
Same here man, same here..
I already know i will never "get used to" these new graphics.. They're just simply so off-putting to me.. I can't really enjoy watching the games anymore even if the commentary is good quality..
Damnit.
B2W is so good I still enjoy the casts, but something has been lost here. The thing is, it looks like Blizzard is actively trying to fix it. They just had to release it early. It will probably be totally fine in a year. Until then, I see no reason to stop using Netease.
I can't.. the new graphics are just way too distracting to me..
also - NetEase on 1.32 aka "Reforged" version now as well..
The amount of stuff they have fixed and the various improvements here and there just shows how completely careless they have been with the release. They should have delayed it by 1 or 2 weeks to fix major bugs and it would not have been such a disaster. What a waste…
I think they are just bandaiding now and not really looking for the deeper issues. They worked on this so long, I don't think 1-2 weeks would have made a difference TBH
Or maybe it would. I guess since the shitstorm has the size of a fullfledged hurricane they added some guys to the team from other projects who actually know what they are doing
You generally can't really just join a team and be productive within 2 weeks. It takes a long time to get used to the new code, architecture, formatting, etc. So even if Blizzard did add more people, we shouldn't have seen the result of that yet.
I think it's just a lack of proper testing procedures combined with strict estimates. These have been small fixes which have helped a lot for the overall quality, that they should have seen and done themselves, but for some reason didn't. The fact that they were quickly fixed really underlines how badly the whole project is being handled.
Reminds me of my old job, where we weren't allowed to write unit tests because it would eat into our ability to write new features. The only bug fixing we did was when customers reported something back to us. It eventually resulted in a bug where our app failed to report that a sensor had died, eventually resulting in several hundred thousands fish being killed due to a lack of oxygen in the water. That's about the time when I started to look for work elsewhere.
I'm by no means an IT crack, but I guess there is also a lot of "legwork" to do which basically every intern can do (like testing and bug reporting. But really who needs to do that if you can let the customer do it for you ).
The amount of stuff they have fixed and the various improvements here and there just shows how completely careless they have been with the release. They should have delayed it by 1 or 2 weeks to fix major bugs and it would not have been such a disaster. What a waste…
I think they are just bandaiding now and not really looking for the deeper issues. They worked on this so long, I don't think 1-2 weeks would have made a difference TBH
Or maybe it would. I guess since the shitstorm has the size of a fullfledged hurricane they added some guys to the team from other projects who actually know what they are doing
You generally can't really just join a team and be productive within 2 weeks. It takes a long time to get used to the new code, architecture, formatting, etc. So even if Blizzard did add more people, we shouldn't have seen the result of that yet.
I think it's just a lack of proper testing procedures combined with strict estimates. These have been small fixes which have helped a lot for the overall quality, that they should have seen and done themselves, but for some reason didn't. The fact that they were quickly fixed really underlines how badly the whole project is being handled.
Reminds me of my old job, where we weren't allowed to write unit tests because it would eat into our ability to write new features. The only bug fixing we did was when customers reported something back to us. It eventually resulted in a bug where our app failed to report that a sensor had died, eventually resulting in several hundred thousands fish being killed due to a lack of oxygen in the water. That's about the time when I started to look for work elsewhere.
I know how you feel. Thankfully my team is now re-writing a big product with proper tests etc. The old code has more tests than actual code, but the tests don't actually test anything since over the years they're just mocks upon mocks that have nothing to do with how the system works
And Blizz should actually delay W3R for about a year or so. No one would be mad. Kinda like Ubisoft did with Beyond Good and Evil 2, which we won't see until at least April 2021 I think.
The amount of stuff they have fixed and the various improvements here and there just shows how completely careless they have been with the release. They should have delayed it by 1 or 2 weeks to fix major bugs and it would not have been such a disaster. What a waste…
I think they are just bandaiding now and not really looking for the deeper issues. They worked on this so long, I don't think 1-2 weeks would have made a difference TBH
Or maybe it would. I guess since the shitstorm has the size of a fullfledged hurricane they added some guys to the team from other projects who actually know what they are doing
You generally can't really just join a team and be productive within 2 weeks. It takes a long time to get used to the new code, architecture, formatting, etc. So even if Blizzard did add more people, we shouldn't have seen the result of that yet.
I think it's just a lack of proper testing procedures combined with strict estimates. These have been small fixes which have helped a lot for the overall quality, that they should have seen and done themselves, but for some reason didn't. The fact that they were quickly fixed really underlines how badly the whole project is being handled.
Reminds me of my old job, where we weren't allowed to write unit tests because it would eat into our ability to write new features. The only bug fixing we did was when customers reported something back to us. It eventually resulted in a bug where our app failed to report that a sensor had died, eventually resulting in several hundred thousands fish being killed due to a lack of oxygen in the water. That's about the time when I started to look for work elsewhere.
I know how you feel. Thankfully my team is now re-writing a big product with proper tests etc. The old code has more tests than actual code, but the tests don't actually test anything since over the years they're just mocks upon mocks that have nothing to do with how the system works
And Blizz should actually delay W3R for about a year or so. No one would be mad. Kinda like Ubisoft did with Beyond Good and Evil 2, which we won't see until at least April 2021 I think.
Scumbag corporate types would be mad about not having that additional money on their end of fiscal year bullshit.
On February 12 2020 18:43 Manit0u wrote: I know how you feel. Thankfully my team is now re-writing a big product with proper tests etc. The old code has more tests than actual code, but the tests don't actually test anything since over the years they're just mocks upon mocks that have nothing to do with how the system works
And Blizz should actually delay W3R for about a year or so. No one would be mad. Kinda like Ubisoft did with Beyond Good and Evil 2, which we won't see until at least April 2021 I think.
Depending on what systems you use, you can download something like dotcover (This one's just for c#), which tells you exactly what parts of your code has tests, and how many % of your code is tested. It's super powerful.
On February 12 2020 18:31 Harris1st wrote: ROFL what dafuq did you guys do? Poor fish
For fish farming, young salmon is grown indoors in big pools, before they're big enough to be released into containers in the sea. These pools needs to be constantly monitored and updated to make sure they have enough food, cleanliness, and enough oxygen in the water. The sensor which monitored the oxygen failed, and just stopped reporting values. Our application was the monitoring solution for the whole system, which should pick up on something like "Hey, this sensor hasn't reported anything in a while, I wonder why?". It resulted in the fish literally drowning due to a lack of oxygen. The bug was of the nature that a simple unit test would have picked up on it. We also didn't have any other type of testing or any form of code reviews. People who wrote their code just merged it directly into master when they felt they were done.
Our same software was also used to monitor elderly patients, ventilation systems, and the sea part of fish farms. I was just waiting for someone to lose their lives. The closest we got before I left was some guy nearly losing his arm because our system decided to randomly start up a big machine while it was under maintenance.
Nowadays I'm in the position as a consultant where I can and do refuse to pick up a contract unless they let me write tests. So far this has only been met with enthusiasm by everyone.
sounds less like a coding and much more like a managing issue. Code will always have bugs, that's why you test to get rid of them. I can't understand the "we don't need to test that" mentality, there will be real issues eventually and then the damages will far outweigh the time gained by not testing.
Then again managers aren't exactly known for their foresight.
On February 12 2020 21:09 Archeon wrote: sounds less like a coding and much more like a managing issue. Code will always have bugs, that's why you test to get rid of them. I can't understand the "we don't need to test that" mentality, there will be real issues eventually and then the damages will far outweigh the time gained by not testing.
Then again managers aren't exactly known for their foresight.
Because you sell a product and then squeeze them further for "tech support" and "maintenance." Why waste money on labor cost for bug-testing if you can do that after you sell the product? The customers are usually more interested in the features, not if it's bug-tested. The bugs are usually found much later.
On February 12 2020 21:09 Archeon wrote: sounds less like a coding and much more like a managing issue. Code will always have bugs, that's why you test to get rid of them. I can't understand the "we don't need to test that" mentality, there will be real issues eventually and then the damages will far outweigh the time gained by not testing.
Then again managers aren't exactly known for their foresight.
Because you sell a product and then squeeze them further for "tech support" and "maintenance." Why waste money on labor cost for bug-testing if you can do that after you sell the product? The customers are usually more interested in the features, not if it's bug-tested. The bugs are usually found much later.
Yes, I foresee no immediately problems with this line of thinking. Instead of finding bugs, let the bugs find you! (And bite you in the ass, destroying any reputation you software and company might have had)
Happy and Infi played an amazing UD mirror today on NetEase. Must see. It's the first game here (from Happy's stream): https://www.twitch.tv/videos/550801720 — it starts around 4 minutes
Edit—By the way, Dreamhack revealed today their list of invited players:
Looks like there will be a pro tour stop in Melbourne, Australia. Going to see if I can get myself a hosting gig for it because I am keen as fuck to contribute.
The amount of stuff they have fixed and the various improvements here and there just shows how completely careless they have been with the release. They should have delayed it by 1 or 2 weeks to fix major bugs and it would not have been such a disaster. What a waste…
I think they are just bandaiding now and not really looking for the deeper issues. They worked on this so long, I don't think 1-2 weeks would have made a difference TBH
Or maybe it would. I guess since the shitstorm has the size of a fullfledged hurricane they added some guys to the team from other projects who actually know what they are doing
You generally can't really just join a team and be productive within 2 weeks. It takes a long time to get used to the new code, architecture, formatting, etc. So even if Blizzard did add more people, we shouldn't have seen the result of that yet.
I think it's just a lack of proper testing procedures combined with strict estimates. These have been small fixes which have helped a lot for the overall quality, that they should have seen and done themselves, but for some reason didn't. The fact that they were quickly fixed really underlines how badly the whole project is being handled.
Reminds me of my old job, where we weren't allowed to write unit tests because it would eat into our ability to write new features. The only bug fixing we did was when customers reported something back to us. It eventually resulted in a bug where our app failed to report that a sensor had died, eventually resulting in several hundred thousands fish being killed due to a lack of oxygen in the water. That's about the time when I started to look for work elsewhere.
I'm by no means an IT crack, but I guess there is also a lot of "legwork" to do which basically every intern can do (like testing and bug reporting. But really who needs to do that if you can let the customer do it for you ).
ROFL what dafuq did you guys do? Poor fish
Testing and bug reporting can be done via proper processes automatically. There has to be some people to restart the machines from time to time and to observe other people are actually fixing what the machines are reporting. Or fixing invalid reports of the machines
You can check the continuous integration and its best practices if you wanna know more. long story short in lamen terms - every developer commit before being added into the final product is being checked against tests. Many tests. And if any of it fails it cannot be added into the product Automatically, no need for interns
On February 13 2020 07:53 TheDwf wrote: Happy and Infi played an amazing UD mirror today on NetEase. Must see. It's the first game here (from Happy's stream): https://www.twitch.tv/videos/550801720 — it starts around 4 minutes
Edit—By the way, Dreamhack revealed today their list of invited players:
On February 13 2020 08:50 GTR wrote: Looks like there will be a pro tour stop in Melbourne, Australia. Going to see if I can get myself a hosting gig for it because I am keen as fuck to contribute.
The amount of stuff they have fixed and the various improvements here and there just shows how completely careless they have been with the release. They should have delayed it by 1 or 2 weeks to fix major bugs and it would not have been such a disaster. What a waste…
I think they are just bandaiding now and not really looking for the deeper issues. They worked on this so long, I don't think 1-2 weeks would have made a difference TBH
Or maybe it would. I guess since the shitstorm has the size of a fullfledged hurricane they added some guys to the team from other projects who actually know what they are doing
You generally can't really just join a team and be productive within 2 weeks. It takes a long time to get used to the new code, architecture, formatting, etc. So even if Blizzard did add more people, we shouldn't have seen the result of that yet.
I think it's just a lack of proper testing procedures combined with strict estimates. These have been small fixes which have helped a lot for the overall quality, that they should have seen and done themselves, but for some reason didn't. The fact that they were quickly fixed really underlines how badly the whole project is being handled.
Reminds me of my old job, where we weren't allowed to write unit tests because it would eat into our ability to write new features. The only bug fixing we did was when customers reported something back to us. It eventually resulted in a bug where our app failed to report that a sensor had died, eventually resulting in several hundred thousands fish being killed due to a lack of oxygen in the water. That's about the time when I started to look for work elsewhere.
I'm by no means an IT crack, but I guess there is also a lot of "legwork" to do which basically every intern can do (like testing and bug reporting. But really who needs to do that if you can let the customer do it for you ).
ROFL what dafuq did you guys do? Poor fish
Testing and bug reporting can be done via proper processes automatically. There has to be some people to restart the machines from time to time and to observe other people are actually fixing what the machines are reporting. Or fixing invalid reports of the machines
You can check the continuous integration and its best practices if you wanna know more. long story short in lamen terms - every developer commit before being added into the final product is being checked against tests. Many tests. And if any of it fails it cannot be added into the product Automatically, no need for interns
Yes, and it's good practice. Unit testing is especially helpful later on to check if you broke someone else's code. But it's no substitute for actual wam-body testing. The developers write the tests themselves, which generally ends up testing for things the developer already knows works. It's the things he didn't think of that tends to slip past the automated tests.
There's also the problem of what can be tested. The further towards the user you get (aka, the further towards the front-en rather than the back-end), the less easy things are to test. Games are the absolute worst for automatic tests, because the variety of things you can do is too big. You can't automate "And then he hit A and D simultaneously while 3/4 trough a backflip while on the edge of a platform, but only on map 3 between cutscene 1 and 2". Instead you just end up with simple tests that check for "Is player on map after spawn?" or "Can he continue shooting when he's out of ammo?"
Any good players from Classic wanna play team games together? Good/ decent players are welcome. Server: America, Acc: Covetous#1106. Add me for some casual 2s, 3s or 4s
I watched the above tournament and this was also the first time I actually witnessed WC3: Reforged in-game, outside of promotional YT material like individual unit graphics showcase and... oh boy. I am SO glad I did not bite and preorder. This shit legit looks amatourish and I'd even go as far as to say the original WC3 had better graphics (when zoomed out and watching the whole picture, not viewing the individual units in a vacuum).
Today Grubby attempted to stream some 2v2s with Cassandra but they encountered so many problems (game crashing for one of them, disconnects, join game bug etc) that they gave up and switched to play Heroes of the Storm instead after managing to only play a couple of games over a period of multiple hours. Blizzard has made a true travesty of this game with Reforged.
EPT
). 
Automatically, no need for interns 
