Because platform selection review is mandatory
Rails is an open source web framework build on top of ruby, first released on December 2005. It uses MVC design pattern and emphasize CoC (Convention over Configuration) and DRY (Don’t Repeat Yourself) paradigm. Ruby itself is known as a clear and lean language. So in the ideation phase of this project, when faced with the problem presented to us, we thought that RoR is a suitable solution.
Continue reading “Looking Back to Our Backend”
In rails, there are basically three ways to store server-side information in the client’s browser:
spoiler alert: they’re all actually just cookies
Continue reading “Rails: Behind the Sessions”
It’s literally only one day after UTS.
My last commit is a typo fix.
Continue reading “Nothing to write”
I just got this thought when trying to write test for a controller yesterday: how exactly did you test a controller?
A controller is a route between model and view. It controls the system behavior given user action. But the validity of the data presented was already tested in the model, and whether the data shows right should be tested in the front end. Continue reading “Test for Control”
“The more I read, the more I acquire, the more certain I am that I know nothing.”
Software development is such a wide field. When I first learn to code, I never dreamed about about these continuous integration and code coverage stuffs, and testing was just making sure that your code outputs the right thing.
Actually, I’m still somewhat right on that last part. After all, all those tools ultimately mean to be used for “making sure your code outputs the right thing”. Just more automatic, more rigorous, more thorough, and simpler (or should be simpler, at least).
Enough philosophizing, here are reviews of what I have learned this past week. These might be reiterating what my teammates has write, but oh well, it’s not like I have anything else to do ¯\_(ツ)_/¯
besides MPPI assignment.
Continue reading “Learning: an excuse for not doing anything”
I planned to write about gitlab runner this week but it seems like Adam has already covered it in his post
so no work for me, yay so I decided to make a sequel, or more accurately, an experiment.
Continue reading “Run, Gitlab, Run!”