Self taught developer
Previously known as @yourstruly@dataterm.digital
Come hang out with me on Mastodon
Check out my blog, where I write about what I have learned
@programming.dev
Self taught developer
Previously known as @yourstruly@dataterm.digital
Come hang out with me on Mastodon
Check out my blog, where I write about what I have learned
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.
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.
Hey Thanks for reading, and I'm glad you found it interesting.
To my understanding, Webfinger provides a standard API for discovering the user profile details no matter the software running on the node.
For example,
$ curl https://programming.dev/.well-known/webfinger\?resource\=acct:snowe@programming.dev | jq
{
"subject": "acct:snowe@programming.dev",
"links": [
{
"rel": "http://webfinger.net/rel/profile-page",
"type": "text/html",
"href": "https://programming.dev/u/snowe"
},
{
"rel": "self",
"type": "application/activity+json",
"href": "https://programming.dev/u/snowe",
"properties": {
"https://www.w3.org/ns/activitystreams#type": "Person"
}
}
]
}
Haha this is exactly me. That habit of losing the knowledge rapidly post investigation is something I'm trying to break, and that's part of the reason I banged out this blog post immediately after my itch was satisfied.
The "I have to tell people about this NOW" vibe also carried me through completing my website (just so I could publish this blog post)
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.
This is a FastAPI feature - Autogenerated documentation using Swagger.
You can turn it off by setting docs_url=None
In your linked main.py:
app = FastAPI(
title="IslabTweet",
description=__doc__,
docs_url="/", # change this to None to disable the docs
version=VERSION,
)
Hope this helps!
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
OTOH, the more pythonic one will probably perform worse, but I'm not familiar enough with Python internals to make that claim without benchmarks.
I'll try it out and add the data in the article
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
thanks for using Leebra!
go to feed...