DEV Community: Richard Munyemana

TaskForce Week 5

Richard Munyemana — Mon, 04 Oct 2021 08:18:06 +0000

last week was awesome we have learned different connection of backend and frontend known as integration not only that we have learned we also agile communication.

Front-end and Back-end Registration

fetching the api is always awesome part for the front-end developers where you integrate with api response and status and you decide what to show the client and handle errors that comes from the backend(api).
we have integrated LoT Dashboard with its backend where we had worked on CRUD functionalities. I personally at the end of the week I have integrated authentication process and consumed all data from the backend.

Agile Project Management

Thursday we had an interesting session with Thomas which was about agile project Management.
we have played a game where we had to act the role that we are given, I had a developer role in this game where I had to as a lot of question to the scrum master and project owner so that as a team of developers we can understand well what the client(project owner wants).

Friday is always awesome this is where we wrap up what we did for the whole week and also plan for another.
As we approach approach the last week of the taskforce we have to brainstorm our final project where we have to demo on the graduation day.

We have reached the end of week 5 and started week 6 which is the last week of our task force and we are working on the final project.

hands crossed let's meet this Friday in project presentation.
thank you.

Task Force 3.0 Week 4

Richard Munyemana — Sun, 26 Sep 2021 10:05:30 +0000

This is the end of week 4 of our task Force and it is amazing to realize how you can accomplish many things with a small period of time.
Good developers are not those who can code and develop a site in one or two days but those who also knows how to communicate to outside world of his/her field.

Agile communication World

communication in agile world we have seen different ways agile methodology uses to convey message
we have looked into 2 methodologies and compared them.
1.Scrum
2.Kanban

Scrum

scrum is method a where we have sprint depending on your team you decide how long the sprint would take and each sprint should have a scrum master scrum master is responsible to know that team mates are working on their tasks and he/ is supposed to review his/ her teammates codes.

Kanban
on the other hand there is kanban it is also an agile methodology where we have boards with tickets.

most of the time taking advantage of both scrum and kanban methodology is very efficient.
For the boards you can use trello board,.

Time Management
Managing your time helps you understand well the priority matrix
and when you manage your time well you get to do all your tasks on planned time deadlines are no longer problems and you can not take a lot of tasks since you have a routine of how your day starts and ends,
I also helps to avoid procrastination and imposter syndrome.

complex UIs
complex UIs sharpening skills is something you got do a lot if you want to grow that why in this week we have been introduced to another complex UIs to build.
It is amazing to have great team around you to review your codes and give you feedback to help you grow your skills and think out of the box to accomplish the challenge.

Communication skills is always the first thing you need to be notice in the community and when combined with better time management you can achieve a lot.

thanks next week it is.

TaskForce week 3

Richard Munyemana — Sun, 19 Sep 2021 07:32:12 +0000

This week was a very disturbing week, I had very pressing things that I had to finish off. But thanks to my teammates I have been brought up to speed.
In this journal we are going to discuss the outcomes of this week experience to working with UX designers.

Developer Basics

As a frontend developer when you have a good UX designer then you can develop best and beautiful sites or apps we have been challenged to use vanilla javascript, HTML and CSS. using Frameworks speeds up your work but I have been reminded not to forget some basics.

Fast Learning and Flexibility

Let's come back to frameworks, There are many frameworks out there and you can not know every single one of them this week I have been introduced to a framework that is the first time to use and I had to learn it faster and use it as it was required in the assignment. The take away here is that as Developers we should be fast learners and flexible to what a clients want you to use or your supervisor.

Professional Skills are Critical

Professional skills are the very crucial things and without them you are not well equipped. You can have all the required technical skills but without professional skills you can not be able to work with a team, your team may have teammates whom you do not share expertise and with professional skills you will be able to communicate and work with them well.

Conclusion

Foundation is what makes you standout and frameworks makes your life easier but you can't know them all you need to be a fast learner all in all professional skills always comes first and then your technical skills and without them not many doors are going to open for you.

Git workflow best Practices and project containerization

Richard Munyemana — Sat, 11 Sep 2021 11:44:56 +0000

Git workflow encourages developers and DevOps teams to to leverage Git effectively and consistently, it offers flexibility and good way of tracking and managing changes from time to time.

containerization combines application and its dependencies into one infrastructure.

Why do we need to write conventional commits?

communicating the nature of changes on your project to your teammates, public and stakeholders, makes it easier for people who want to contribute to your project by allowing them to explore a more structured commit history so that it is easy for them to understand what changes you made and where you have done that.

here is how conventional commit is structured:

<type>(scope):<brief description>

// `<type>`:here you put the type of the fix you did
// whether it is a **feature**, **chore** or a **bug** you fixed.
//`scope`:this introduces breaking API changes
 - [add detailed body]

finishes #storyId
//references to closing an issue that you were working onto.

But How would I describe what my pull request or Merge request for those who use gitlab so that it is easy for the reviewer to know what he/she is going to be looking for?

below is the list of questions that you need to be answering when describing you PR or merge Request

in your PR description before creating a Pull request.

# What does this PR do?

# Description of Task to be completed?

# How should this be manually tested?

# Any background context you want to provide?

# What are the relevant pivotal tracker stories?

# Screenshots (if appropriate)

# Questions:

How would you run different versions of your application on the same server? what would you do or how would you do it?

to answer these questions this is where docker comes into play,
Docker enables you to run different versions of your app on the same server without interference.
then how do I setup docker for windows:

Download docker for desktop here
follow instruction and install docker.
create a docker file in your project directory

FROM node:version

    // Create app directory
    WORKDIR /app

    // Install app dependencies
    COPY . .
   //depending on package manager you are using in your project
    RUN npm install or yarn install

    // Binding to PORT 3000
    EXPOSE 3000

    //starting your project start script
    CMD ["npm or yarn", "start"]

run build to create docker image

//to make sure that your docker daemon is up and running in your terminal run 

docker ps
//start building your image by running

docker build -t tag-name

//then run 
docker run -p PORT:PORT -it tag-name
//make sure that the port you use is the one you have in your docker-file.

Git workflow and dockerization makes thing easy when working with a team and even on your own projects you may need to refer to a past commit you made months ago and it will be much easier to know what were the changes you made the same for Pull request description.
And while sharing the OS containers provide workload isolation.

Task-force week-1 Outcomes

Richard Munyemana — Sat, 04 Sep 2021 03:44:50 +0000

First things first thanks to @awesomity and for putting together this task force. We have learned a lot, working with an amazing team, it was very exciting.

so let's start with the technical part.

Did you know that good user stories help a developer to develop websites, app and systems which are user friendly and makes it for the developer to understand what are the tasks the he/she have to work onto?

This week I was introduced to the best approaches of writing user stories that explains well what a user story should look like

And also developing them and meeting the expectations(Acceptance criterias).

As a developer you frequently will need to stand in front of either your bosses or sales team at your company explaining what you have developed how does it will it work when it get to the market right?

fun fact did you know that it is not about what you present but it is how you design your presentation and how you present what you have got, due to this I have been introduced to the following good presentation best Practices:
[*] Keep it simple.
[] practice your presentation before pitching
[] Do not exceed your given time
[] Have a well designed power point and points should be short

To sum up we learned a lot in this week and was very interesting excited for the next coming weeks

see you next week guys :)