How I built a post recommendation feature for my blog using text embeddings, GPT-4 and ChromaDB with LangChain
Understanding Logarithms Better With This Cool Trick
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!
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
I deeply resonate with the sentiments in this article. It brilliantly articulates the topic in a way that I didn't have the language for.
It's more important than ever in today's homogenized internet monoculture to advocate for such things, especially for those outside the tech sphere. Great read!
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
This is the best option. I recommend Nand2Tetris to everyone! It's an incredibly well designed and executed course
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!
Ooh, I hadn't heard of Quarto before, but it looks really good! Thanks for mentioning it!
While jc is a great tool, and I'm definitely a fan, I believe the real solution to the overarching problem lies in a paradigm shift: see nushell
I wanna go to one so bad! But they never happen in my city..
Featured Photo by energepic.com I’ve had a love-hate relationship with Bootstrap for a long time. While I love how fast it lets me get going, I absolutely hate the cookie cutter vibe of most of the stuff that I end up making with it. Bootswatch is awesome, and I know that I could customize my theme...
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.
Learn how to search, query, and modify JSON data with 25 interactive jq examples and explainations
I wrote a guide about jq which has interactive examples
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.
I'm from India so these numbers might be a bit weird. My yearly comp has basically gone like this from 2017 to 2023
$0.7k -> $3.6k -> $4.8k -> $20k
Have you seen all the people just stuffing their profile README full of random graphics and stats and badges
Ohhhh, this site is a great find. Exploring all the articles right now. Thanks!
Unfortunately, no one can be told what a monad is. You have to see it for yourself (then you won’t be able to explain it to anyone)
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.
I had this same problem, after clearing my Jerboa data it worked fine. Hope that helps
Create an infinite amount of straightforward and readable git manual pages.
I use Adminer and PGWeb interchangeably
Transcription of a talk given by Cory Doctrow in 2011
I recently went on quite a rabbit hole regarding the .well-known directory, and wrote about it.
I'll start:
When I was first learning to use Docker, I didn't realize that most tutorials that include a database don't configure the database to persist. Imagine my surprise when I couldn't figure out why the database kept getting wiped!
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