HOMEWORK 1 REFACTORING AND LEGACY CODE

HOMEWORK 1 REFACTORING AND LEGACY CODE

Related Posts Week 4: I really like the idea of my git history telling the story of my code. I also feel like testing frees up my brain from worrying about every little bit of my application. So all I have to do now is concentrate on writing whatever little bit I’m working on now, instead of trying to keep the entire app in my head and worry about not breaking anything else. So instead of putting all the tests there, I just wrote a few to make sure the controller was asking the model for that information.

There’s probably a lot of other things but these are the easy ones that I can remember off the top of my head And if you’re curious about the code I wrote for this week’s homework, it’s up on Github. This is so different than the way I used to program. Related Posts Week 4: This week, we had to add a new feature! That shouldn’t be a surprise because writing the test is always the hardest part for me!

I spent a LONG time on this homework. SaaS Legacy Homework 2: This week’s SaaS homework has been the most elaborate so far.

SaaS Legacy Homework 2: Lessons Learned · jlc

I also feel like testing frees up my brain from worrying about every little bit of my application. That shouldn’t be a surprise because writing the test is always the hardest part for me!

Then I wrote recactoring unit test for the controller. Then at the very end I wrote the cucumber integration tests for the sad paths. I tried really hard to keep my git commits small, task based, and meaningful this time, which meant I had to do a few git things I’ve never done before like adding specific lines instead of entire files. Even though I could have homeork out the homework in probably less than half the time without testing, I really liked the practice.

  UWE COURSEWORK FEEDBACK

So even though at first they had no idea how to teach this, they set out to do so in this class. And also having the ability to revert any single change without messing anything else up. Twitter Fitter—the tweet generator! And the anf of all previous articles if any will now be comments of this article. Our feature in a nutshell: Instead of working on a new custom app, we are given an existing app homweork Typo blog platform that has a long history, sometimes messy code, and spotty test coverage.

The overwhelming answer was “how to work with legacy code”. You can find out more here.

homework 1 refactoring and legacy code

The body of the new article will be a concatenation of the two previous articles. The hardest part was writing the tests. So all I have to do now is concentrate on writing whatever little bit I’m working on now, instead of trying to keep the entire app in my head and worry about not breaking anything else.

SaaS Legacy Homework 2: Lessons Learned

This week, we had to add a new feature! Only administrators can merge articles.

At last I allowed myself to write some xode code, which didn’t take long. But this time I played around with them in the debugger gem.

This is so different than the way I used to program. If what I’m doing now will break something else, then I’ll know about it soon enough if I wrote my tests right. I am still very new to Rspec and TestUnit syntax, and spend so long trying to figure out exactly how to phrase things. Then I had to write a bunch of unit tests for the model. But I’m homewori to say that I stuck to it this time and wrote refactoriny the tests before writing the actual code except for the view and some skeleton methods so it didn’t throw method-not-found errors–basically I had to get it to the point where the tests failed for the right reasons and not because it couldn’t find some method.

  AH RMPS DISSERTATION TOPICS

Last week we were asked to fix a bug in it. I really like the idea of my git history telling the story of my code. Related Posts Week 4: There’s probably a lot of other things but these are the easy ones that I can remember off the top of my head And if you’re curious about the code I wrote for this week’s homework, it’s up on Github. All other users will not see the option at all.

homework 1 refactoring and legacy code

As the instructors explain in the lectures, after teaching the class for a while, they asked some of the top software companies what one thing they wish graduates of computer science programs would learn before entering the workforce. First I wrote the Cucumber integration tests amd the happy path only.