|
Level 01.08 got me stumped. Can't make any sense out of those numbers. Who got that one so far?
|
|
|
|
|
I got that one.
It's 1.10 and 1.13 I haven't worked out yet.
This is more a guess the formula game than any kind of programming challenge.
I'll give the answer to 1.08 below in small text in case you want it....
((2 * y) + x)
|
|
|
|
|
Any luck with 1.10, 1.13?
|
|
|
|
|
1.10 spoiler ahead
x + y/3
|
|
|
|
|
|
|
Can't really click a button entitled 'Play' at work! Might check it out later.
|
|
|
|
|
It seems less like a learn to code game than a pattern recognition practice game. I develop in C# all day, so I expected to just breeze through (the beginner levels at least). The coding isn't the hard part, it's determining the relationship between the numbers. Once I know that, there's a small challenge to getting the skill rating to 3 bars, but that takes guessing and googling. There's no hints, no teaching.
|
|
|
|
|
Jeremy Hutchinson wrote: There's no hints, no teaching.
Just like real life then?
You'll never get very far if all you do is follow instructions.
|
|
|
|
|
_Maxxx_ wrote: Interested in your thoughts.
It bores me, but then again I'm not new. I like the concept, just as long as it builds up to something useful like a project. Building a project is the best way to learn IMO.
Jeremy Falcon
|
|
|
|
|
Yeah - I agree.
When I first looked at it I liked the concept of providing running code and failing test cases - but it didn't seem to be going anywhere after a while, and was relying on the user spotting patterns - so was more of a "what is this function meant to be doing" than "how would you implement this function"
I'd like to see the same concept with, as you said, a program building up
Something simple like, off the top of my head, calculating the area of various shapes.
Functions for rectangle, triangle, circle etc. etc.
Arguments of side lengths/radius whatever
You can then introduce the IShape interface, and Square, Circle etc. classes.
Hmm - I really should get into this!
|
|
|
|
|
Hi!
I wonder if I should name my class either "TymlNormalString" or "TymlStringNormal", taking into account that these classes among 20 others describe an syntax tree for my custom language "Tyml" and that there is a base class "TymlString" and there will be normal strings, escaped strings and implicit strings.
The first has the advantage that it is more natural, the last that IDEs will sort the types and files alphabetical which will simplify finding the wanted type.
I know that this cannot be answered finally, but I am interested in your opinions and your arguments.
|
|
|
|
|
A naming war! It has been a while.
Call it TymlNormalString, I'm sure you can remember the names of the three types of string, no IDE assistance required.
|
|
|
|
|
It was not my intention to start a naming war, I was just unsure how to decide.
But since almost all permutations were suggested, it seems that it doesn't matter how I will decide.
However, the majority seems to prefer "TymlStringNormal" which I now prefer too.
|
|
|
|
|
|
My vote is for "TymlStringNormal" ... I think having sorted object names is very useful in debugging, and in using IntelliSense.
cheers, Bill
“I speak in a poem of the ancient food of heroes: humiliation, unhappiness, discord. Those things are given to us to transform, so that we may make from the miserable circumstances of our lives things that are eternal, or aspire to be so.” Jorge Luis Borges
|
|
|
|
|
What use does it have during debugging?
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
If it weren't there, the program wouldn't run, so debugging would stop.
Seems pretty cut and dried, to me.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
NormalTymlString
You'll never get very far if all you do is follow instructions.
|
|
|
|
|
TymlStringNormal
TymlStringEscaped
TymlStringImplicit
...would be easier to read and understand...
|
|
|
|
|
Make Tyml and String a namespace
Thus Tyml.String.Normal 
|
|
|
|
|
This will fail since "String" (and "Array" for "TymlArray" and "Object" for "TymlObject") is a keyword in many programming languages and the abstract class "TymlString" then would be Tyml.String.String. Having a class and a namespace with the same name is possible but not recommended (at least in C#).
|
|
|
|
|
It won't fail if you use full namespace declarations but it will cause bugs which is surely the purpose of any naming scheme
|
|
|
|
|
Having 'Tyml' in all your class names is ugly. The classes should, imo, be called BaseString and NormalString, in a namespace like Tyml.SyntaxElements or Tyml.Domain.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
