This has been the most surprising class that I took this semester. I have learned so much of the patterns and design that I did not know I need it. I went to a CIA internship interview and was in shock that a great part of the questions were targeting design questions like: patterns and decision making in the software. I liked this class more than Requirements and Intro.
Refactoring my Project to fit the Smart UI Infrastructure
After presenting my phase 2 to the class I realize something. My project never fit the layer infrastructure. Most of my layers(domain, application) were just empty layers and most of my logic and constrains were done on the presentation layer. I will work on it on it this weeks before the final presentation.
Overcoming Failure
I was not going to write this blog, but given the circumstances I’m feeling like it. I never thought I was going to make it out of my Bachelors. I became a father at the age of 19 years was not as easy as I expected. Fast forwarding to this semester where I had to be with my son on the hospital for a full week was hard as hell. But I have never gave up on me and will never be. Thankfully now closer to my goal than ever and will continue to work harder and harder to achieve my bachelors and become a Software Engineer to help support my family.
My experience on the tests
In the Software Requirements class, the tests were extensive and exhausting. They were very long, but compared to the Intro class, they were much easier. The fact that this class is more narrower and precise than the Intro class is a full advantage when focusing on these topics. I liked this class in general more than the Intro to Software
Initial UI for VehicleSearchEngine
After working on some projects I discovered Material with angular and it helped me a lot to improve my Presentation layer experience
Learning to work with shareholders
This past months we’ve been talking about the shareholders in requirements. This is by far my favorite topic because we learned how to work with them, ask their requirements, work with conflict, etc. I think this topic is very underestimated because the main point is to keep your clients happy. Here is the human part of the Software Engineering where you have to keep the point of view of the shareholders and how to deal with them.
Learning about Unit testing
These weeks I learned about testing and it was nice. This methods I will apply to my projects.
Layer infrastructure in design
Infrastructure layer design for software was on off the different patterns that we learned in class. In this infrastructure, the software is divided in: Presentation layer, Application layer, Domain layer and Infrastructure layer. I have never though of how different I could design my software in regard of infrastructure but so far I like this one for my project.
Proposal for Design
After deciding my domain and project. I started my proposal of the project. By the time that I discussed it with the professor, I realized that my domain was wrong. I thought that the domain was Marketing, but was rather stock management. Inside my scope the project looks more for to look my available vehicles and, if sold, reloads the backend to maintain countability of them. Will refactor my proposal.
Deciding to choose what domains to choose for my projects
Working on two classes(SD & ST) was nor my smartest idea given the fact that I need to work on two projects simultaneously and hoping that it does not give me conflict. For the testing project I was partnered with a classmate and we decided to choose a project within the music domain. The app would be called MusicTracks and it would be a, sort of, copy of Spotify where you see your playlists and share them with your friends, etc.
For the Design class, I was the only one with no partner for the project. Since I am a very difficult person to choose a topic, I went to the Professor and it help me to choose my domain, marketing domain. My project would be about selling vehicles. It would be called Vehicle Search Engine and it would be about having dealers that manages their vehicles to sell them, reserve them, etc.
Software Engineering Experience 