ishanpage

u/ishanpage@programming.dev
13 posts · 28 comments

Recent posts

Recent comments

Dict keys are case sensitive in python. In your code I can see the key you've used has a capital M in Amarok. Maybe that's the issue here

This is strange. I tried your snippet with your file and it works for me:

(env) ➜  testing cat x.py
from mutagen.id3 import ID3
tags = ID3("myfile.mp3")
print(tags["TXXX:FMPS_Rating_Amarok_Score"])                                                                                                                                               
(env) ➜  testing python x.py
0.78

I started off with a PHP blog based on PageNode which I hosted on a VM I shared with a friend, but later moved to Hugo hosted on Cloudflare Pages. I've had various Wordpress blogs in the past, but couldn't keep any of them around - hopefully this one stays!

I agree that from a completeness point of view, the official manual is better (I've linked it at the bottom of my post as well), however I'd love to hear your specific thoughts about why you feel this particular article is not good- I've tried to include fully interactive examples for the most common tasks I find myself doing with jq everyday. This feedback will help me improve my own skills as well, so I would appreciate it very much.

It is possible to live on that, there are people who live on less than it. Personally all of it went to supplementing my Mom's income so we could survive.

There are plenty of entry level jobs in India that offer those kinds of wages. There are more that offer less.

Yes, it's exploitative.

eBPF is something that I've been exploring recently for work. I was quite blown away when I realized the true potential. I did find it difficult to get started, and while this article is a good introduction, some example code or hands on would be nice to have

The scenario is not ficticious. It's taken straight from my first job, but I had to leave out specific details. The application being developed had something to do with DRM, so that might explain the weird requirements.

The lesson is that sometimes business will require you to force users to update their version, and/or enable specific features for specific subsets of users. So you should have such a mechanism in place before it is required, otherwise you will end up doing hacky things like breaking the server to do what needs to be done.

Systems such as these are actually fairly common in enterprise, but since it was my first job, I had not planned ahead for this because I had no idea.

This is great! I've done something similiar for Laravel in the past.

What I've noticed is that as projects move forward in their development cycle, something like this often becomes necessary for certain functionality to require services to be factored out and then worked on by separate teams.