Day 4

Completed - Completed a HankerRank challenge with basic numpy shape and reshape
- Completed PyBites Code Challenge 4 - Twitter data analysis Part 1
- Almost completed PyBites Code Challenge 5 - Similar Tweeters

I had done the PyBites Challenge 4 before, so that one was a refresher. Challenge 5 was really tough, this was my first dive in to natural language processing, and gensim is giving me some TypeErrors.

Day 3

Completed PyBites Code Challenge 3 - PyBites Blog Tag Analysis.

Thoughts: This is my first use of itertools product and difflib SequenceMatcher. It took me a while to figure out I needed to read() from the xml file instead of trying to open it line by line. It also stumped me that the tests were putting the tag pairs in to a set, and I needed to sort the tuples so that I didn't get duplicates. Goal: speed up my coding in the next few weeks to work on other projects too!

I'm committing to starting 13Jan2019. I want to level up and expand the breadth of my Python skills with PyBites, complete porting Gaphor to Python 3 and GTK+3, and commit more to BeeWare. It would also be cool to learn more about using GTK+ in C in order to understand PyGObject more in depth. Maybe by contributing something to Nautilus.

Days 1 and 2: completed PyBites 1 and 2 by building a Scrabble game.

Dan Yeaw boosted

has the design I was always hoping for using Vim Vixen on Firefox. A truly modal input design. I'm enjoying it!

I just submitted my first Pycon talk proposal!

I'm learning more about functional programming in Python: I understood that Tuples were an immutable data structure, which allows you to create objects that can't change. Now it came together for me that mathematical like functions require immutability in order to ensure there are no side effects (operates on the inputs, and produces an output with no changes in state). So using Tuples ensures that your data doesn't change at run time to support this programming style.

Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either! We adhere to an adapted version of the TootCat Code of Conduct and have documented a list of blocked instances. Ash is the admin and is supported by Fuzzface, Brian!, and Daniel Glus as moderators. Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!