Skip to main content

A JILL OF ALL TRADES

I guess our ancestors we're right, although I don't really want to admit it. I like to disagree with stuff like this. It's hard to accept defeat sometimes.

These days I've been struggling with having a lot of interests. I think I always have. So many things to do. So many things I want to do. So many things I wish I could do. It's a plus one whenever I see something I like. I proceed to wish I could do it and most times actually add it to my learning list.

Out of my learning list is the priority list. There was definitely a time I decided to focus on just one thing (i.e., Python) till I mastered it. It sounds easy because why would somebody want to learn a couple of things when they could just stick with one. It's less work to do. I have always struggled to stick to one hobby or activity or whatever.

I have too many interests making it difficult.

I did fail to stick it out till the end with my new companion Python. One was just not enough. I wanted more. And why not??

Just yesterday, I thought to myself and I quote because I wrote it down. "I suddenly get the concept of Jack of all trades, master of none. Jeez. I think I might be a Jill." At that moment, I seemed to not hate it at all. It felt right until I spoke to a friend hours later.

He had more experience in general. Both with life and with Software Engineering. I think I've mentioned it before in one of my posts that he advised me to focus on Python and leave every other thing for now. I did listen. It felt right at that moment, but days passed and I got enticed again.

I felt bad at some point because it was a conversation we've had several times before, but I'd love to commend his patience. He did succeed in proving to me once again, the power of not being a Jill. Monogamy at its best.

Somethings he said, and I quote because I wrote them down. "You have to think of what value you have, and what kind of value you want to have and work towards it", "It's difficult but worth it".

I kept on saying I was slacking because the classes were quite difficult (Classes especially, OOP). I sort of thought to myself whether I wasn't born to like challenges during our conversation, but who was anyways.

Life is also a challenge. Haha :)

I've definitely been beating around the bush all this while. As the title says by the way, this article is about my conflict between choosing to accept to be a Jill of all trades or not.

For now it's a no but who knows what tomorrow holds for me, for you, for us??


:)

Comments

Popular posts from this blog

365 DAYS OF CODE - DAY 0

DAY 0 THOUGHT PROCESS Day Zero of the 365 days of code highlights my state of mind before the actual start of the program. Yes, it is a program. A program I set for myself to make sure I actually put in the work on a daily. I have tried coding before but have never been quite consistent with it. A friend advised me to try coding daily if I really wanted to be great at it someday. He also stated that it would take a long time and I should be prepared for it. During the same period, I noticed he was on a year's worth streak of chess which made me realize I could also do the same but with coding. I signed up for the 100 days of code course on Udemy and plan on starting my coding journey with Angela Yu and the thousands of students also taking the course. I also drafted my own copy of the pledge, copied and modified from the 100 Days of Python Pledge from the course materials. It is currently pasted on my wall as a constant reminder. Finally, I will also be recording my process here...

365 DAYS OF CODE - DAY 13

What is wrong with this code?? Can you tell what it does?? import art n1 = 0 n2 = 0 selected_operation = "" solution = 0 def add (n1, n2): return n1 + n2 def subtract (n1, n2): return n1 - n2 def multiply (n1, n2): return n1 * n2 def divide (n1, n2): return n1 / n2 operations = { "+" : add, "-" : subtract, "*" : multiply, "/" : divide } def rest_of_calculation (): print ( "+ \n - \n * \n /" ) selected_operation = input ( "Pick an operation: " ) n2 = float ( input ( "What is the next number?: " )) for key in operations: if key == selected_operation: solution = operations[key](n1, n2) print ( f" { n1 } { key } { n2 } = { solution } " ) print (art.logo) n1 = float ( input ( "What is the first number?: " )) rest_of_calculation() while True : new_calculation = input ( f"Type 'y' to continue calcu...

365 DAYS OF CODE - DAY 10

I realized that I have been tagging each day in accordance with the 100 days of python course . Now, I am one day behind (it is day 10 of the 365 days of code but day 9 on the python course I am taking right now) because I made sure to review unclear exercises yesterday. It is fine regardless. On day 9 of the python course, we looked at dictionaries, its table-likeness (2 columned) One tiny forgotten comma leads to 4 different errors and 1 warning, the prominent one being the SyntaxError. But shouldn’t it highlight line 3 instead of line 4?? Comma added, Error fixed. My Grading Program Code: student_scores = {     'Harry': 88,     'Ron': 78,     'Hermione': 95,     'Draco': 75,     'Neville': 60 }   student_grades = {}   for key in student_scores:     if student_scores[key] > 90:         student_scores[key] = "O...