On sprint 4, we the team started some with the project. That’s the search project. We were all able to install the angular materials including all other stuff attached to it. At first, getting things started was very coming a big problem. Implementing the angular materials was not working on my computer. after installing it, it brings up a lot of warning. But with times i have to install most of the stuff manually. After all the manually works on the angular material, it started working perfectly. Now that we are all got things started and working, we have to study the angular material on how to implement the text field, button and any other things that we will need in the project especially the google’s material. During the sprint, while working on the search field, i decided to learn more about the google material and a little more about the angular material. I notice learning all these, the angular material has made it very simple for any one using angular project to create a web site or to create an application in angular. There is not need to start from scratch as the angular material has everything made ready to use compared to the old way of creating an web application or a website. I also did some practice on most of the angular materials. They were very interesting. Before ending the last day of the sprint, we decided to work on who will be doing this or that. as in dividing the work according to the group members. We also started preparing for the final presentation of the project. How it should be presented, things that will be needed and who is going to say this or that. We talked about it but never brought up and a conclusion to it. So probably, next sprint or during class meetings, we will be discussing about it. So far things are going well will the project, everyone in the team is putting much effort for the progress of the project. Which is very a good things. This whole project has made me learned a lot about how team work is doing in the real world job. I have gotten some understanding on how consistency, and keeping up has much contribution to the team. All these bring up a good productivity. We the team member make sure or ensure that deadlines are met and that there is high quality work. When one team member falls behind, there is another to pick up the pieces. When work is divided up among members of a team, it gets done faster, making the overall business operate more efficiently. During this sprint, i notice the collaboration of the us make work go faster, which is very a good thing making us also focus on other sections of the work. hope next sprint we accomplish everything or be done with the project and start fully working on the final presentation.
This week on apprenticeship patterns, i read on breakable toys. From the readings i learned, experience is built upon failure as much as (if not more than ) success. From the readings, i got some importance of failure and the reasons why we should allow ourselves to fail. And also, at the same time what if you are working on a real job. And the real world job, you are not allowed to fail. But yet you will eventually will fail one way or the other. So in this case, you will need a special space to practice on your work. That will be playing with your toys. For examples, you are working on computer tools or you are on a real job working on how to fix computers. Since you will always want to put up with good production without no mistakes. I will be advisable to get computer devices either good or spoil device and be practicing on it. with much practice and also with a lot of failure, you will get all the tricks of fixing on the device. Also be very good at it. I also learned apart from all these, you must love your toys. That is to say, you should love what you do. In that case through your many failures, you just don’t give up easy. All because you love what you do. In the other way, if you do not love it. You will just give up on your toy(what you are working on). With the pattern solution with the breakable toys, give us some ways on how to use our breakable toys in order for a team to grow or as individual growth. from the readings, i got the understanding of the important lesson gained from failure is experience.What happens when we fail? When we go through something and can walk away with firsthand experience, it helps us to develop a deeper understanding for life. The experience of failing at something is truly invaluable. It completely changes our frame of mind through the induction of pain. It makes us reflect on the real nature of things and their importance in our lives, transforming and improving our future selves.
On sprint 3, as i said on sprint 2. which i was working on getting my angular to work and also getting more understanding on the angular. I finally made it worked with the help of a team member. During our sprint 3, a lot of things needed to be changed. New kind of a project had to be done. The project called simple app.
During our meeting, we discussed more about the Zeplin. We check whether we all on point as to see if we were all on point with the Zeplin. It was a little bit strange for me. But with time i got the understanding and it is very very helpful for our project. So upon all the split tasks, we the team chose the search button. As I look through, i thought it will be very simple to do. Because all we need to do it to get a text field and a small button after that we label them as a search field and that will be all. If my thought is right, then we probably we should be done within a hour if we get it started. If not and my second guess is, we might need a back end to work with. Something like getting an information from a database, a file and any source of data or information. So at least the search field can be useful by playing the role as a search engine pulling out info from any data source. Either ways, we will go through all the step by step, dealing with the issues on github and wait for what the prof will have to say to us. Whether to add or changed something.
i also notice our styling of the project will be from google. It is good for us in the case of fast project be done. the only problem with that is i have no idea of were to start or begin with. So the plan is to learn or search on tutorial on it so i can get more understanding on it. And if anything, hope the team up me get through.
For as we the team, we are planning necessary stuff/tools as in the type of IDE we will all agree to be working with so in case a team member has a coding problem or wants help with the use of the IDE, we will be able to help him or her. Also getting the understand of the whole project. Getting to know the main types of languages that will be needed. We are also checking who will be working on a particular part of the project. The reason is so we all can get something to contribute and also make the work more faster rather than leaving it for one person or a few people in the group. We hope the next sprint which is sprint 4, we should be able to be half way or almost done with project.
For this week, i read on “sweep the floor”. I found it very interesting. As a programmer, there are a whole lot of unfinished project you eventually will not complete on time or not will not complete it at all and will abandon it. As i was reading i saw some of the things why developers forget, why they decide not to complete a project or why they think this particular project is not a that necessary.
From the readings to my understanding, having finished projects demonstrates to potential employers or employers that you can deliver what you set out to deliver, but it depends on what you mean by “project”.
If you are doing the project with a view to having a complete product that showcases all of your skills and may be something you want to make money out of eventually then yes you should finish it, or at least show that it is actively being worked on.
If you are doing the project to learn specific things (how to stream video, password encryption, what ever) then once you have that aspect working it’s less vital to have a fully functional product as you have effectively completed the project. What you should have is something that can you can show prospective employers to demonstrate your skills.
For example, this might just be a web site that says “Welcome back, Derek odam” after successfully logging in and nothing else – but that’s fine as you are showing off the code behind the website that demonstrates you understand password encryption and secure connections etc.
Sometimes because of a code statement or situation that can not be solved, a project is left unsolved. Which most of the time from the beginning of the project all the information given were to make the project a successful one or even sometimes the better one of the new project. In my small knowledge or opinion i think checking for all unsolved situation will be very helpful in a very long run.
I actually enjoyed reading this part of the pattern because, it makes my know that without the love for the work you are doing, you will always be procrastinating leading to unsolved issues. Which is very bad. Sometimes not very bad since maybe you are a deadline to which a project has to be completed. In that case skipping a small problem will be a wise decision to take.
This week, i read on “record what you learn”. On the reading, i got the importance of recording what you have learned. As it is generally said, it is good to keep notes. During your craftsmanship or the process leading you to the real word job. You will need to jot what ever you learn, whether from your master, from colleagues or from your own researches. By doing this you are able to learn more skill faster.
For instance, you have learned a new computer language just because you want to create a new project. But in order for you to complete the project, you will have to learn an additional language. Since it is a new language, it is likely you will forget a whole lot of stuff. And at the same time you will need to learned this new second language as well. So in this case, while learning the computer language for the project. It is required for you to jot up some notes just in case you are learning the second language and its time to join both languages together to complete the project, you will be able to recall all what you have learned or what actually you might have forgotten.
if you want to become the best in your field, taking notes is your ticket to making it happen. As you build your career and keep track of what you’re learning, you’ll have easy access to your very own refresher courses.
Quality notes not only help you build a strong arsenal of knowledge, but they can help make a difference in the lives of those you care about. If a new co-worker needs to get caught up on a project they’re working with you on, they can refer to your notes to catch up without feeling overwhelmed. If a friend misses class due to a family emergency, your notes can help them get back on track. It’s a win-win situation for everyone involved.
Taking records is a nice action that reveals much about a person’s patience, determination, and attention to details. It also shows you’re efficient and don’t allow what’s important to fall away. From the this pattern, i have come to realized, the reasons for all the blog pages and a whole lot most instructors guide us through.
Hi readers, on my sprint 2, we planned making sure everyone’s was ready to start with the testing. some team members were able to start with the angular and get the sever up and running. Some were stuck, like me. With me, i was able to get most of the things to work, like installing the latest java, nodejs/npm, the karma and the angular itself. Everything felt alright till i tried building the up the project given to us. When i did run the build command, it gives a lot of warning and also many errors. Did not no where i went wrong, so i consulted one of my team member who has finished with his set up and was able to build and also run the server command. He went through, noticed my @angular-devkit/architect was not installed. And also many many of the angular packages were not installed. So he decided for me to uninstall it and reinstall it back.
So i tried uninstalling it but to no avail. So i decided to use the vmware application to install linux OS since i was not able to uninstall the angular. I also learned, linux is pretty very cool when it comes to these kind of stuff. So after installing the linux OS, i did the same process as i did on the windows. Installing the latest java, nodejs/npm, protector, karma and angular. Everything worked fined and when i test for the angular as in the version. I noticed maybe all the packages were installed. That was great till i tried building on the project. when I run the build command, it game me a whole lot of warnings. But this time, it did not give me errors unlike the windows.
For now I am just stuck with making my angular work. Hoping will get help from a team member to see if that will help. If not, i will have to share with someone who’s program is working fine.
While i was also trying to fix my “angular problem” , i was also learning a whole lot of things on angular. Did a whole lot of search, searching on what could be the problem why my angular is not setting up. This made me start learning from scratch. It was really annoying. But i had no choice if i wanted to make this work. I followed most examples and also practiced most of them on my own. I notice when i tried creating a new angular application, it works fine but when i tried running an old project or building on an old project, it give me all kinds of warnings.
This week i picked the pattern, “your first language”. I was very interesting reading it. I got to know more about why you should learned your first language to perfection. At least master it well before learning another language. From the reading, get a language you like and very easy to use, is the best way to be a better programmer by mastering it. The reason is because all the programming languages follow the say pattern. Only different statement but the same principle. So by mastering one and feeling very comfy about it, make it very easy for you to learn new programming language with ease.
From the readings, to my understanding. I got to know by becoming very good at your first language, you need to ;
- Use the language all day, every day. Usually this means being full-time employed in the language.
- Read all you can about the language. Especially, “best practices” and idioms.
- Join a users group to talk with others about the language and what they do with it.
- Work with other people’s code! There is no faster way to learn what not to do in a language than to have to clean up after someone who did something awful.
- Support the code you write – every bug becomes a tour of your worst decisions!
- Study computer science and languages in general
- Learn a very different language. A great compliment to C would be a functional language like Lisp. This will turn the way you think about your procedural language inside out.
- Learn to use the frameworks and APIs available for that language.
- Take the time to do your own experiments with the language. SICP is not applicable to C, but the attitude of learning a language by testing its limits is a very productive one.
- Read the history of the language to learn why it was made the way it is.
- Attend conferences to hear the language authors speak, or to hear what industry leaders are doing with the language.
- Take a class in the language.
- Teach the language to others
As I said, reading this pattern made my understanding broadened. I really know by following the pattern given from the book will be a great fit for anyone who want to have a better and easy life at work in the future as a computer software or programmer.