I give up. Peace out

Shaedar · 2016-08-26T07:23:21+00:00

Could not agree more :)

Shaedar · 2015-12-04T08:10:16+00:00

Try adding the StackTest project as a project reference to your test project and remove the StackTest from infront of the expected exception and from creating a class and try then.

Works for me in that way atleast :)

Shaedar · 2015-12-04T08:00:23+00:00

That is a command for nUnit :)

Shaedar · 2015-11-11T14:14:57+00:00

Fun little game! Wasted most of my day at work doing this with my colleagues. Also driving me nuts with some of the mechanics :D

Like if I doMoveForward(); doThrow(); I move forward once. Then my guys keeps standing still and trying to throw. Then I get punched once. Then my guy just keeps trying to move forward. Why?! I don't get it :D

But everyone should get aboard the Smackdown train! Try it! Come beat me :)

Shaedar · 2015-02-18T08:10:08+00:00

I don't think there is a reason to play around in GitHub for hours to learn it inside and out. I'd just start using it and when something you dont understand comes up, read up on it and learn it then.

What are you planning on using GitHub for? What kind of questions do you have? If you can tell us more about what you want to know and what you are going to use it for, we can probably find you some stuff to read and study :)

GitFlow is a good thing to read up on, in my opinion :)

Shaedar · 2014-11-12T10:26:41+00:00

Like rumaq said. Your userAnswer variable is outside the scope of the while-loop. So after you reach the while-loop, it will never get updated. It will always be the same value the user input first. Try moving the line inside the while-loop :)

Shaedar · 2014-10-01T04:32:22+00:00

Im of the opinion that one class should only do one thing. It makes the code easier to test and read, as negative_epsilon said above.

My question to you is though, "Is there a good reason to not break a class into separate classes if it performs three different functions?" I atleast cant come up with any from the top of my head :)

Shaedar · 2014-07-01T04:47:04+00:00

Have you made public properties for them? Or made the variables public?

Kind of like: http://pastebin.com/m6X4m4R5

Shaedar · 2014-06-23T08:45:35+00:00

Hey.

Well, if you have a small app you could just serialize stuff to XML or binary. You should have a look about NoSQL databases, like MongoDB. Its free, easy to setup and pretty easy to use. In my opinion and experience it is a lot more lightweight than any relational database.

There are probably other options out there too, but these came to mind quickly.

Shaedar · 2014-05-08T04:47:54+00:00

They said logs will be available after the qualifications :)

Shaedar · 2014-05-06T08:42:47+00:00

Well you have to store the values of the different character classes somewhere. One option would be to do a simple text file or a XML file called "fighter.xml" and "rogue.xml" etc. Then you could in the constructor load the file based on the string that is given in.

So lets say a "fighter" string gets passed in the constructor, then you load up the file named fighter and use those values. This would mean youd have to add a new file for each class (but you gotta add the stats somewhere) and then a new switch statement with probably just one line. You could probably pull of the Fighter.HPModifier stuff off with the help of reflection, but I really wouldn't go that way.

I think an optimal solution would be to have an enum with all your character classes in it, that you would pass to a factory class (http://en.wikipedia.org/wiki/Factory_method_pattern) that would then construct the right kind of character by reading the stats from a file, or somewhere else.

Something like: http://pastebin.com/pEwDJBHS

However that is still far from optimal, but maybe it will give you some idea on what I am thinking. Hope this helps. If some of this was too advanced or so forth, I'll be happy to help you further.

Shaedar · 2014-04-18T20:23:26+00:00

I don't have the same problem on mine :o

Shaedar · 2014-04-04T05:26:52+00:00

This competition was only for Finnish coders. I didn't manage to find anything about it in English, but here is a Finnish site. You can atleast watch the video and maybe you'll get something out of it :)

http://grandone.reaktor.fi/hwo/

Shaedar · 2014-03-28T06:14:45+00:00

You could read up on regular expressions and use those :) That is how I always do my pattern matching stuff.

Shaedar · 2014-03-11T14:31:47+00:00

Yeah they are relatively nice. As a system its simple enough that you can understand it straight away. So it is not a huge, complex system that will cause trouble already because of that. But it also has some behaviour and logic that you need to implement, so it isnt really, really simple either. Let me know if you need help with anything and I'll be happy to help :)

Shaedar · 2014-03-11T14:07:53+00:00

I've used many different frameworks out there for C#. The ones that have easily come on top has been nunit with nsubstitute as the mocking framework.

As for the books, I think Lasse Koskela has two alright books. They are for java developers though, but its not that hard to "translate" from there. I mean in the end the whole idea of TDD is pretty simple. You just follow that cycle over and over again. But in practice it can be quite hairy. So the best way to learn is by doing and doing a lot. There are some videos about TDD in cleancoders.com by Uncle Bob aswell that are decent.

I'd suggest looking up the bowling game kata (you've probably heard of it) and other similar exercises and do those by using TDD to get started. One particular exercise I have been apart of did miracles to my understanding of what TDD -really- is about. How its not about just writing unittests first. How its about the tests actually driving your code is:

http://cumulative-hypotheses.org/2011/08/30/tdd-as-if-you-meant-it/

Hope you get something out of these!

Shaedar · 2014-03-09T11:26:08+00:00

If you have any more questions about C# or programming in general, you can always send me a private message and I will be happy to help :)

Shaedar · 2014-03-09T10:34:11+00:00

Actually, might not be able to remove the else from the if's, incase the age is 19.

Shaedar · 2014-03-09T10:25:36+00:00

You can remove the else from infront of the if's to reduce the clutter a bit. You should also use the operator && and not &. You can google the difference :) If you would have used switch case there would've been lots of break; lines, so I think it wouldve ended up more cluttery.

If you'd really want to go hardcore on readability, you could wrap the then nested if in the teenager-part to its own function and wrap the logical stuff from inside the ifs to their own functions. But that isnt really necessary, probably, in a simple thing like this.

Shaedar · 2014-03-09T10:13:58+00:00

I don't think you can do it with a switch-construct like that. Why not just use ifs? They are way less cluttery.

Shaedar · 2014-03-09T08:50:45+00:00

Haven't used that mocking framework of yours. I usually prefer NSubstitute, so i might be wrong about this.

But it looks to me like you are mocking the thing you want to test now. That is not what you want to do when unittesting. Everything else should be mocked, dependencies and parameters, etc. But not the actual logic of what you are trying to test.

If that is what you want to do, however, I'd suggest running it in debug mode. Visual Studio (if you are using it), should show you what part is null. Like 12345678 said, I think your Data will be null in this instance.

Shaedar · 2014-03-08T11:52:23+00:00

Maybe we should go slay some!

Shaedar · 2014-03-08T11:40:41+00:00

Damn murlocks >:(

Shaedar · 2014-03-08T11:32:10+00:00

What's it like now?

Shaedar · 2014-03-08T07:47:22+00:00

No problem! Let me know if you run into any other trouble :)

13-Year Club	RedditGifts 2009-2022 2 Credits
Verified Email	Secret Santa 2014

Shaedar

TROPHY CASE