|
|
|
|
|
by ahsanhilal
4370 days ago
|
|
Thanks for the well thought out reply! The course layout you have written out is quite thorough. The only thing is that for someone who does not have any programming background, they need to see immediate results to gain an understanding of how powerful code is. That is why I thought Html/CSS is a good starting point and then go in deeper. I am open to other methodologies, and we can talk more on email if you would like. Would love to exchange ideas and resources (email in profile) |
|
I am wiseleo on just about every website and gmail, so feel free to send me an instant message.
For me, seeing an executable test spec for the first time was very surprising and revealing. There is an entire book "Refactoring: improving the design of existing code" that teaches you how to name functions so your code reads like English.
After all, this is valid Jasmine from near the beginning of my test suite:
it("should return an array containing at least one object", function() { expect(menu.length).toBeGreaterThan(0); });
It reads like English. If you can show that code can be written like this rather than like typical code, you will notice an immediate jump in confidence.
If you show that in Rspec, where the alien-looking
function ( ) { };
is replaced with
endand expect('should do something useful') becomes expect "should do something useful"
it becomes even more approachable.