DAY SEVEN- ”DISCUSSIONS GALORE!!”

I’m now used to getting ready for the regular warm-ups, the first activity in the morning.

The first discussion of the day was titled ‘Web Request-Response cycle’. The class had a really interactive session with the Boss himself, Ikem. He generously gave insights on HTTP requests which include: parsing the URL, sending the request and getting response using status code that aligns with the condition of the request sent…interesting one there!!

Next discussion was on ‘M.V.C Frameworks’. Ikem enlightened the entire class on how the model(M) processes and validates data from the database before it passes into the controller(C) which controls what’s rendered in the view(V). He also included an important component known as ‘The Routing Engine’. The routing engine uses verbs, requests and works directly with the controller (the power horse..lol!). He explained how important it is to apply the standard rules when using Frameworks to build applications, it makes the solution effective and result-oriented. I learn so much from this, considering how I used to implement solutions with Frameworks before Andela. “I have learnt from the best so expect the best…Amen to that!!!”

The next discussion was on Software Engineering paradigm titled “Agile Methodologies”. The discussion started with a widely practiced software development model in my country, titled ‘The waterfall model’. There was a comprehensive discussion on how it’s being practiced and its many flaws. The conclusions on this model led to a more efficient software development practice called ‘The Agile Model’ which is a combination of several waterfall model-modules and also supports modular programming.

Agile Methodologies were sub-categorized into four Meetings:
Daily Startup: Its an evaluation mechanism with examples like: “What did I do yesterday?”, “What am I doing today?”, “What are the blockers preventing me from doing these things?” 
Sprint Planning Meeting: where the product owner discusses project planning with the entire team.
Sprint review: It happens at the end of the project sprint, where the project owner must be available to review what has been done.
Retrospective Meeting: Like evaluation of the existing project. It happens once every sprint

Next discussion was on API(Application Programming Interface), and how it works as web services(Q:…”like RESTFUL web services huh?…”, A: “…yeah, something like that”…) in applications. APIs are sets of requirements that govern how one application can talk to another. It makes use of our first discussion of the day too, remember the web request/response cycle? Yeah that’s it. There are several kinds of APIs(twitter api, facebook api, github api, etc.) and we practiced on some of them too.

Finally, there were discussions about a workflow interface known as “Trello”. Trello is a project management platform where you document your progress on software projects(and other kinds of project too).

The awesome instructor, Ikem provided samples on how to make use of these software development resources discussed above and I’m having fun learning so much, its been awesome all the way. Cheers to that!!

Show your support

Clapping shows how much you appreciated olayemifolakemi’s story.