#20: Final post.

Hello there, dear friend. So here we are, in our final blog post. Somewhat sad, isn’t it? I mean, in the beginning, this was just a project that we had to do in the course of a lecture. Sure, we had something big in mind. Choosing sides against amazon, the biggest online shop in the … Read more

#19: Installation.

We would suggest running at least the backend in linux (or via wsl under windows) in order to prevent issues with npm under windows. Install mariaDB: TutorialBe sure to leave the port set to 3306. Also, we assume the username and password to be root. If you choose to use a different username or password, … Read more

#18: Metrics.

Hello again! This week, we had a look at the code metrics from codacy. As we already integrated codacy in our workflow, it makes sense to look at the change proposals so we also have a more stable and more secure application. The following screenshots show you the issue dashboard as well as a detailed … Read more

#17: Retrospective. Part 2.

This week, it was time for another retrospective, evaluating our sprints for this semester. You can also read our last retrospective here. This time, we did our retrospective together with TaskHub. You can read their blog post about the retrospective here. We began by noting the things we found positive, negative, confusing and not-so-good. After … Read more

#16: Design Patterns.

In the end, it all comes down to 0 and 1 Vineet Goel But a good developer should care about other software developers and not about machines. Since we, software developers, are used to be very lazy it is a good idea to get acquainted with design patterns. Wait, what?! New information again (Figure 1)? … Read more

#15: Refactoring.

Hello and welcome back, fellas! This week, it was all about learning how to properly refactor existing code. Therefor, we worked through chapter one of Martin Fowler’s book “Refactoring: Improving the Design of Existing Code”. In this chapter, he starts with some example code and explains the first steps he takes when refactoring code. We … Read more

#14: Tests.

Hey guys and gals, this week we worked on our testing. Since it’s close to impossible to get full test coverage in just on week, we worked on testing our Frontend. We used Jasmine for Unit Tests and Karma to execute these tests. Below you can see a screenshot of our test coverage: The tests … Read more

#13: Function Points.

This week we are going to calculate function points both for already existing and for the upcoming Use Cases. These FPs will help us to create a diagram for better time asigning. Here is an example of it: Function Point 0.o “What are those function points?” would be a reasonable first question. Here is a … Read more

#12: Risk Management.

As part of our weekly chores, we assessed the risks to our project. While we thought of those, we became aware of some risks that we weren’t prepared for. We didn’t have a regular database backup in place for example. Below you can see our finished table of risks. Name Description Probability Impact Risk Factor … Read more

Betterzon sells to Amazon!

Today, besides us being back from our practical stage, we got some exiting news for you!As our website grew bigger and bigger with an average visitor count of almost 10 per day, we got an amazing offer from our friends at Amazon. Jeff Bezos contacted us personally a few weeks ago and offered to buy … Read more