I can't speak for other streaming services, but at Apple Music we did pay musical industry professionals a lot of money to do human evaluation of specific searches. We had people with specific deep knowledge of genres and niches. At least in my little corner Apple that was quite a bit of effort put into this.
HN user
bradly
Ruby on Rails since 2006. Walnut and leather since 2022. Hypertext since birth.
Small software developer
bradlyfeeley.com
bradly@rails247.com
Currently: BirdyMusic.com
Recipin
Bacon Wrapped Urns
Synth Recipes
Ono Kura 斧蔵
Homers Only
Todone List
Runway
Dark Black
Burn Box Woodworking
Heron's Nest
Aloha Condo
Previously: Shopify
Apple
SWAP
Intuit
Digitaria/STL/212 Interactive/Mirum/Lymber
Futurely: Good Mourning!
Goodbye, World!
Always: Lot, Camden, & Brown
Coffeewalk
San Diego, California & Lopez Island, Washington@̶b̶r̶a̶d̶l̶y̶
Gift cards do not expire because laws were passed to prevent it. No such laws exist for AI credits, so companies will do what is most profitable.
Location: San Diego, California / Lopez Island, Washington
Remote: Preferred.
Technologies/skills: Ruby, Ruby on Rails, RSpec, Git, Turbo/Stimulus, TailwindCSS/TailwindUI, AWS, Kamal, HTML, CSS, JavaScript, SQL, APIs, people
Resume/CV: Ruby on Rails professionally since 2008 at Shopify, Apple, Intuit and a bunch of startups as well.
Email: bradly@rails247.com
Open to consulting/contract work or salaried positions. Please reach out for specifics. More info at https://bradlyfeeley.comLocation: San Diego, California / Lopez Island, Washington
Remote: Preferred.
Technologies/skills: Ruby, Ruby on Rails, RSpec, Git, Turbo/Stimulus, TailwindCSS/TailwindUI, AWS, Kamal, HTML, CSS, JavaScript, SQL, APIs, people
Resume/CV: Ruby on Rails professionally since 2008 at Shopify, Apple, Intuit and a bunch of startups as well. Open to consulting/contract work or salaried positions.
Email: bradly@rails247.com
More info: https://bradlyfeeley.com
Location: San Diego, California
Remote: Yes. With travel up to one week a quarter.
Willing to relocate: No
Technologies: Ruby on Rails, Git, Linux, Tailwind, Hotwire/Turbo, SQL/Postgres, Cloud infrastructure, people
Résumé/CV: Seasoned Rails developer with extensive experience at Shopify, Apple, Intuit as well as many start ups. You can read more at https://bradlyfeeley.com
Email: bradly@rails247.com2020 they had $2m+ ARR
You've got an extra "R" in there. In 2020 their only revenue from was non-recurring lifetime software purchases. Like SaaS if you had a 100% churn rate.
Location: San Diego, California
Remote: Yes. With travel up to one week a quarter.
Willing to relocate: No
Technologies: Ruby on Rails, Git, Linux, Tailwind, Hotwire/Turbo, SQL/Postgres, Cloud infrastructure, people
Résumé/CV: Seasoned Rails developer with extensive experience at Shopify, Apple, Intuit as well as many start ups. You can read more at https://bradlyfeeley.com
Email: bradly@rails247.comI’ve had swiftbestpractices.com forever and still haven’t done anything with it. Meanwhile I’ve been going ham on my latest purchase of myfacespacebook.com. It’s weird the things that actually motivate us.
If anyone would like to add some Christmas lights to their site I made a little web component to add a little cheer to any site.
https://github.com/bradly/christmas-lights.js
You can see it in action at https://bradlyfeeley.com and https://birdymusic.com
Thanks, I’ll check this out!
Dang… I don’t even use React and it still brings down my sites. Good beats I guess.
I recently implemented dark/light mode for the first time and was really surprised to find that in order to add a toggle I had to duplicate a both of vars/styles and use JavaScript. I'm looking forward to not having to deal with that cruft in the future.
Would be interesting to hear from Cloudflare the extent of exploitation before today. I'm assuming they can see if/when this started being exploited.
Also, the "Sub bass" link might be broken
Thank you! It is now fixed <3
I did not! Very cool. Thanks for sharing. Is there a way to see the source for the sounds?
One of my best and most productive work situations was remote with a week[0] together every quarter. Key to this was scheduling the next trip while we were together to make sure it was on the books. We got to meet new team members, share some meals together, work through new architecture designs with a whiteboard, and plan. Not much got done during that week, but we sure got a lot done each quarter.
[0]: This was actually Monday-Thursday with travel on Friday
That does make sense given the prompt "What is the current year and is 2026 next year?" provides the correct answer.
Good question. While I had a fairly narrow view of a very large system, I'll give my personal perspective.
I worked on systems for evaluating the quality of models over time and for evaluating the quality of new models before release to understand how the new models would perform compared to current models once in the wild. It was difficult to get Siri to use these tools that were outside of their org. While this wouldn't solve the breadth of Siri's functionality issues, it would have helped improve the overall user experience with the existing Siri features to avoid the seemingly reduction of quality over time.
Secondly, and admittedly farther from where I was... Apple could have started the move from ML models to LLMs much sooner. The underlying technology for LLMs started gaining popularity in papers and research quite a few years ago, and there was a real problem of each team developing their own ML models for search, similarity, recommendations, etc that were quite large and that became a problem for mobile device delivery and storage. If leadership had a way to bring the orgs together they may have landed on LLMs much sooner.
LLMs would help a lot, but there was a lot of low hanging fruit. During my time at Apple I worked on some of the evaluation of Siri's quality and saw first hand how the org issues affected Siri's path forward.
Thanks for sharing. I've been on a path of algo music with JavaScript (I also do not enjoy JavaScript) and have mostly just guess-and-checked my way through it. I'm going to work through this as my advent of code project.
Yesterday I put up a little dictionary of synth sounds that I'm building out to help me on my journey (https://synthrecipes.org). The goal to be able to export any particular sound in a format for different live coding environments. Sounds are defined in a JSON format like https://synthrecipes.org/recipes/acid-bass.json. I'll open source it today so other can submit sounds.
--
Edit: I've open sourced the repo so others can improve existing sounds and add new ones. https://github.com/bradly/synth-recipes/tree/main
Great sound!
This Sonic Pi example really blew my mind when I first heard it. Such a rich sound out of three notes.
use_synth :hollow
with_fx :reverb, mix: 0.7 do
live_loop :note1 do
play choose([:D4,:E4]), attack: 6, release: 6
sleep 8
end
live_loop :note2 do
play choose([:Fs4,:G4]), attack: 4, release: 5
sleep 10
end
live_loop :note3 do
play choose([:A4, :Cs5]), attack: 5, release: 5
sleep 11
end
endA lot of great recs in this thread, but I'll a couple others I didn't see listed yet:
Mort Garson: Mother Earth's Plantasia
Hiroshi Yoshimura: Surround
Satoshi Ashikawa: Still Way (Wave Notation 2)
Shameless plug... Search BirdyMusic.com in Spotify/Apple Music/YouTube Music to hear some ambient music algo generated based on realtime Birdnet detections and weather in my backyard.
Steve Jobs passed away the day after Siri’s release, and I don’t think anyone else had the confidence and internal credibility to push the hard organizational changes Siri needed, similar to when he moved Apple to a single P&L when he returned.
No problem. I'm confused by it as well. I migrated a repo that is more source available than open source and didn't realize that it probably is against ToS until afterwards.
From the current Terms of Service:
Private repositories are only allowed for things required for FLOSS projects, like storing secrets, team-internal discussions or hiding projects from the public until they're ready for usage and/or contribution.
They are also allowed for really small & personal stuff like your journal, config files, ideas or notes, but explicitly not as a personal cloud or media storage.
So the ToS says only private repos that support FLOSS, but then backdoors into "small & personal stuff" which is pretty loose and up to Codeberg's discretion so probably not the best place for your private side project repos.I also wasn't understanding the value looking at the first two examples, but the pricing packages example I do think I would struggle to implement in a clean way using traditional css.
What if the company selling the screwdriver kept telling you your could use it as a hammer? What if you were being bombarded with marketing the hammers are being replaced by screwdrivers?
Would this be similar to how Charlie and Jules work?
This is what Fog and other cloud agnostic libraries promise. The problem is they you get tied to the lowest common feature set or writing different code paths to take advantage of latest features.
I had a similar experience when I asked him what he thought about vars being able to end in a question mark. Very nice guy who probably hears a lot of very bad ideas.