Skip to main content

Posts about #100DaysOfCode (old posts, page 5)

A Hundred Days of Code, Day 014

Had time, so finished up the app! Hurrah!
Ok, so this makes up for one of my missed days, so I have to do a hundred and one only.

Running the app, downloads some lolcat images from the net, saves them to a folder and then opens up the folder for you to enjoy :)

The last app taught me how to download text over the internet.

This one

  • taught me to download binary data (images in our program)
  • learnt how to detect what operating system runs on my computer
  • learnt how to reach out to the operating systems shell and run commands

The amount of modules that I am now being exposed to is a bit dizzying.
A long term plan, would be to look at the more common ones and study them in depth.1

The code’s over at Gitlab and Github.

I had lots of fun. Onwards!


  1. Kushal has long suggested, I do this. 

A Hundred Days of Code, Day 013

The program is almost done.
Had lots of fun.

Today was the first time, I went over a huge, run – see error – fix error – run again loop. Drove me absolutely batty.
I managed to get it all up and running.
Documentation pending.

Hope to have it all neatly tied with a bow, tomorrow.


A Hundred Days of Code, Day 012

Started up with a new program.
While the last one dealt with working with text on the internet, this one deals with binary data.
The point to go get some images (lolcats) in my case, download them to a folder and display them.

Watched all the videos today.
More tomorrow.


A Hundred Days of Code, Day 011

Ok the weather app is done.
Er, only it’s not the weather app anymore, it’s just a temperature app.
The program was meant to pull all sorts of details from Wunderground and apparently the site has changed into a different, more complicated (to me) web page.
I did not want to spend all my time, futzing with CSS.
So I figured out how to just pull out the place name and the temperature and display it.

Things I learnt,

  • How to use Requests and Beautiful Soup to scrape and parse web pages.
  • Practiced my documentation skills a bit.
  • Learnt to fend for myself.

The code’s on Gitlab and Github.


A Hundred Days of Code, Day 010

Working on the get tempature / mini weather app.

  • Learnt about type hints.(I intuitively needed this feature as I kept dotting in my editor waiting for stuff to pop up :P glad to know such a thing exists and Python supports it.)
  • Learnt about named tuples. I love anything that will let me name things the way I want.
  • Learnt about sanitising text that we extract from a web page; stripping white space and new lines and crazy characters and what not.
  • Grateful for the batteries included nature of Python. Well, not necessarily batteries included as much as batteries available on demand. Batteries of all shapes and sizes at that. I can only imagine what writing such a program from scratch must involve. To all the generous people, making modules and libraries available to use freely, and to the infrastructure that delivers it, you folk have my undying gratitude.

A Hundred Days of Code, Day 009

Cooking along on the weather project.
Managed to pull down a web page, put it into a object, return in and then create some ‘soup’ out of it.
It handily lets me inspect a lot of stuff, but finding what I want seems to be confusing.
Brains are mush right now.
Will give it another go, tomorrow.


A Hundred Days of Code, Day 007

Started up with a weather app today.
It is supposed to scrape the weather from Weather Underground, parse it a bit and then give you the weather.
Made the template of the app.
For some reason requests does not seem to be recognised in VSCode.
Will do more tomorrow.


A Hundred Days of Code, Day 006

Journal progam done!
Yay! Find the code over at Gitlab or Github.

The program is a lot more basic than I expected.
It does not let me keep multiple journals :)
But I’m happy with what I learnt.

  • How to put together a program
  • How to use modules
  • Found a little extension in VSCode, called VSCode autoDocstring, that makes typing in docstrings a breeze.
  • Oh, I learnt about docstrings, to help document what I am doing.
  • And brushed up on the basics, loops, conditionals, etc.

Here’s to more happy programming.


A Hundred Days of Code, Day 005

Still working on the journal program.

But made significant progress today.

  • Learnt how to read and write from files (lots more practice required)
  • Learnt how to pass variables around between modules, that are spread across files (still find it confusing. guess that’ll ease with practice)
  • Learnt what all that __name__ stuff is all about. (pretty simple actually. if main is not my name, i refuse to run. you call me in vain1)
  • And finally, learnt what docstrings are. They’re basically bread crumbs I leave for myself and other folks reading the code, to figure out, for example, what a function does, what input it expects, what output it’ll poop out and all that jazz. Basically, documentation for programmers, by programmers.
  • Once I document my code up tomorrow, I will be done.

Here’s to more productive days!


  1. Well, not vain really :) the other use case is to import this file into others