You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The True and False Statements exercise in the Making Choices lesson would be more clear with some else statements to display the results when the value is considered false.
For example:
if [ ]
disp('empty is true')
else
disp('empty array is false')
end
Also, when learning I found the use of "foo" everywhere in examples confusing and frustrating, using a word that means something to people might make it more accessible.
The text was updated successfully, but these errors were encountered:
Thanks for the ideas @mbdunn!
A PR with some else statements would be welcome!
I don't feel too strongly either way about 'foo'. We only have one example of it in this lesson, but it is widely used in programming as a meaningless placeholder for variable and function names, strings etc, precisely because it holds no meaning. See here for further info https://en.wikipedia.org/wiki/Foobar
Good point. I guess giving a bit of background and introducing it while teaching would help because it will be everywhere when they need to look stuff up for themselves after.
The True and False Statements exercise in the Making Choices lesson would be more clear with some else statements to display the results when the value is considered false.
For example:
if [ ]
disp('empty is true')
else
disp('empty array is false')
end
Also, when learning I found the use of "foo" everywhere in examples confusing and frustrating, using a word that means something to people might make it more accessible.
The text was updated successfully, but these errors were encountered: