Hey, tech peeps, welcome to my journey into the software engineering Bootcamp series, this is the second in the series of more to come.
During the third week of the training and while we are waiting to be assigned our tech stacks, we were working on the Harvard CS50 problem sets which have been challenging due to the shorter deadline to turn in our solutions to each problem set, we literally have less than 48hours in between to turn in or risk getting zero and you will still be made to turn it in anyways.
So far taking the Havard CS50 course has been challenging and a blessing for me as it has made to understand how stuff works underneath the hood and has challenged me to want to go in deeper on how stuff works as my learning continues.
Aside from learning about the C data structures, the other stuff that really got me hooked is learning about memory allocation and how it can lead to a stack overflow if not free when done before now I knew about stack overflow as a platform that was founded by Jeff Atwood and Joel Spolsky where programmers go to seek for help when facing a difficulty, as I use it every now and then, never knew this was how the name was coined, I am definitely going to the scratch the surface more on memory allocation to get a full understanding of how it works.
In week three we dived into databases using SQL, this was also fun for me as I learned how to query the database to both manipulate and store user information, the Fiftyville problem set was kind of challenging as it did require a lot of logic to solve the case.
Then came Flask, one of the python frameworks which is considered a lightweight web framework server used for back-end development, this was the first time for me working with the back-end, I did learn a lot from this on how to connect the front-end to the back-end which is like having your own local computer that comes with localhost.
Personally completing the Havard CS50 course puts me on my toe and gave me a lot of insight on how to take up any programming language along the way be it a low-level or high-level language and used it to provide solutions to problems.
Lest I forget, we are also doing our daily POD stand-up where each POD is assigned a POD leader which is like your SCRUM master, and in each stand-up, we are expected to give an account of the task we did the previous day, and the task we intend to complete for the day and if there is any blocker on our assigned task, for me doing this daily stand-up makes me accountable and I am already feeling like I am in a formal work environment.
So, tech peeps that are all for this series, until my next post keep punching those keyboards and debugging.