Arlon's CSUMB Blog

This journal's required reflection is to list the five most important things I learned in this course, (Java II, CST-438 Spring Boot Framework with React/Software Engineering at CSUMB) and why I chose them: Trunk based development in conjunction with Agile development is a correct paradigm, or at least a broadly applicable one. The reason is that I have discovered this on my own, in independent projects, and class material has reinforced this as being the paradigm in use by Google, and the paradigm Google engineers belive is most widely applicable. Spring Boot Framework with Java, MySQL and React using RabbitMQ for a service manager is quick, easy and a robust methodology to develop with. What we built has user authorization, a rich front end with easy build-ability, a MySQL connection with lots of database functionality automated for us because of the framework, and a back end built in Java with Eclipse which is pretty speedy because of all the auto-fill and problem checking Eclip

These pelicans use both Agile as well as Plan and Document methodology for catching fish for lunch. This week's assigned reflection is to compare and contrast the methodologies of Agile vs. Plan and Document (Waterfall). Plan and Document (Waterfall) is a process used for project management which focuses on the end product goals and the steps assumed that will be needed to get there. (ProjectManager, 2021) Agile methodology focuses on incrementally nudging features into a project so it's never broken, merges don't lose features, and everyone is working on close to the same code-base as often as possible. Plan and document methodology aims at a linear progression of adding features until the final product is finished, while Agile methodology aims at adding small cohesive features with correctness assertions backed by unit and end-to-end testing schemes. Plan and document is a tried and true methodology which would be used for things like government initiatives, where a speci

The important things I learned this week were many. We learned adding OAuth2 login to our Spring Boot Framework website to enable user authentication for the website through the Google login. We also reviewed an overview of Spring framework, adding front to back mods to enable the OAuth2 login with Google. The chapters we read in the book were great on encouraging effective collaboration, but I was not particularly a fan of the way chapter 2 started out by knocking independent effort. Google wouldn't be Google without Linus's operating system, Python wouldn't be Python without Guido Van Rossum, and one of the people reading the book is the creator of AccountBlaster , my favorite program of all time and also my own program, which I created entirely on my own. If it had been a corporate endeavor it would probably have been corrupted away from its true purpose. Being built in pure JavaScript and JQuery it is entirely a front end application running entirely at the client, with

Our required contemplation for the week is to compare and contrast unit tests with end-to-end testing paradigm: Post an entry to your journal contrasting unit testing with end-to-end testing. Unit tests go with each feature, documenting it and testing hopefully just it and as little other things as possible. Dependencies are mocked, faked and doubled and the unit test can pin the test to the behavior of only the thing it's trying to test. The purpose of unit tests are to not only make sure each feature works but to create a working example use to go with the feature, not only continually verifying the functionality but providing a window into what the expected behavior is if it breaks down. Database interaction is mocked, user interaction is mocked, just the logic in the feature being tested is under focus. The engineer that writes the feature is usually the engineer that writes the unit the test for that feature. End-to-end tests also provide a window into expected behavior bu