I use binaural beats for types of programming work where it is useful (I've tried Brain.fm and focusatwill.com and prefer the latter). Source: almost 2 years ago

I take focalin in conjunction with listening to music at focusatwill.com. The music has surprisingly been very helpful for me. I used to try to listen to classical and every time there would be a pause between songs, my attention would be disrupted and I'd drift. I did buy the year-long subscription, I think it's around $50, but totally worth it if you can afford it. The music offered is specially engineered to... Source: over 2 years ago

A recent one for me has been Focus@Will. It’s meant that I can reduce the amount of decisions I have to make when it comes to getting on with anything that requires focus. I no longer dick around on Spotify trying to find the perfect focus music - I just press play and crack on as best I can. So far the music has been really good at getting me in the zone (it’s often just getting to the point where I’m ready to... Source: over 2 years ago

Cool stuff. I use brain.fm and focusatwill.com. Brain.fm is my favorite because it's generally higher quality and I managed to snag a life time sub a few years ago. Source: about 3 years ago

I also worked for 8 months on a music discovery webapp called Noiseblend that uses Spotify. We were never accepted for their commercial program and were not allowed to ask for money on the website. Source: about 1 year ago

My most ambitious web project was https://noiseblend.com which is a web app for discovering music on Spotify. It’s a next.js + React slow and memory hungry mess [1] which could have been static HTML with some JS for the dynamic bits. Experience taught me to keep it simple nowadays, but I had to go through the Noiseblend mistakes first. The stack is Python with Sanic for the backend, Postgres for db and Redis for... - Source: Hacker News / over 1 year ago

I’m serving everything from the Spotify API directly on Noiseblend (https://noiseblend.com) and rate limit has never been a problem. When a request fails because of a rate limit, Spotify responds with 429 and a Retry-After header so you know when to schedule the next request. In my tests, that header never had a value greater than 10 seconds, and 429 responses were very rare. - Source: Hacker News / over 2 years ago

I've been using this site ever since I discovered it! I'm glad to see it featured on HN. I started learning to play the Romanian Kaval [1] last summer and Songdata helped me enormously in finding good backing tracks to improvise on. I'm mostly improvising on chillhop tracks right now because I'm trying to develop less traditional rhythms (although I'm still clumsy with the breathing and knowing when to keep the... - Source: Hacker News / over 2 years ago