SoundCloud Developers Blog

>> Bit confused on one point -- so SoundCloud revised their ToS to deny downloads, but they kept the download URL in the API response? Amazing that after two different illegal take-downs it just kept getting back on top of the listings.

> I think they eat their own dogfood here. As far as I can tell, they have no special privileges for their owned and operated clients. If you for example look into the network panel when using the web client, you'll see that they directly access `api.soundcloud.com`.

But it is strange that they in their TOS for the website state:

"You must not copy, rip or capture, or attempt to copy, rip or capture, any audio Content from the Platform or any part of the Platform, other than by means of download in circumstances where the relevant Uploader has elected to permit downloads of the relevant item of Content."

In other words, they seem to allow users to download content that is available for download. So if I write my own web browser, I'm free to download downloadable content -- but not if I write an app for Soundcloud...

Or perhaps, it's this clause:

"(x) You must not rent, sell or lease access to the Platform, or any Content on the Platform, although this shall not prevent you from including links from Your Content to any legitimate online download store from where any item of Your Content may be purchased."

It's unclear to me how Soundcloud cannot get Firefox for Android banned under this clause as well... (well that would be insane, but…

These are some of the top sites' engineering blogs which I collected over a period of time - I removed those which have already been posted:

Google: http://googledevelopers.blogspot.com/ http://google-engtools.blogspot.com/ http://googleresearch.blogspot.com/

YouTube: http://youtube-eng.blogspot.com/

Baidu: http://usa.baidu.com/category/baidutechblog/

Yahoo: http://yahooeng.tumblr.com/ http://yahoodevelopers.tumblr.com/

Wikipedia (closest I could find): https://blog.wikimedia.org/c/technology/

Amazon: https://aws.amazon.com/blogs/aws/

Twitter: https://engineering.twitter.com/

eBay: http://www.ebaytechblog.com/

Microsoft: http://microsoftengineering.com

FourSquare: http://engineering.foursquare.com/

Apple (closest): https://developer.apple.com/

Paypal: https://www.paypal-engineering.com/ https://devblog.paypal.com/

Dropbox: https://blogs.dropbox.com/tech/

Edit: More (collected from this link: http://www.quora.com/What-are-the-top-startup-engineering-blogs):

Yelp: http://engineeringblog.yelp.com/

Quora: http://engineering.quora.com/

Yammer: http://eng.yammer.com/blog/

AirBnB: http://nerds.airbnb.com/

Square: https://corner.squareup.com/

Flickr: http://code.flickr.net/

Soundcloud: https://developers.soundcloud.com/blog/

Cloudera: http://blog.cloudera.com/blog/

Slideshare: http://engineering.slideshare.net/

Heroku: http://engineering.heroku.com/

Pinterest: http://engineering.pinterest.com/

SoundCloud | Senior Software Engineer, iOS / Engineering Manager | NYC | Onsite, Full-time

SoundCloud is an open platform enabling everyone to share and discover audio content all over the world.
Here at SoundCloud NYC we’re expanding our monetization & growth engineering team (currently a team of 23) who help build the platform that helps creators make money from their content, listeners gain access to the world's music, and brands engage with SoundCloud's unique audience. We’re looking to add a Senior Software Engineer, iOS and an Engineering Manager to our growing team!

If you’re interested in learning more about the challenges our engineers have tackled and our lessons learned check out our developer blog: https://developers.soundcloud.com/blog

For more information on the specific roles:

Senior Software Engineer, iOS: https://soundcloud.com/jobs/2017-04-06-senior-software-engineer-ios-new-york

Engineering Manager, Payments: https://soundcloud.com/jobs/2016-10-27-engineering-manager-payments-new-york

Feel free to reach out directly to benjamin.cheung@soundcloud.com if you have any questions!

I like how JSON-LD lets one embed many resources inside a document. And there are plenty of good preludes to this recent emergence: Soundcloud wrote about how they used an instance store 3 years ago in their clientside to extract all relevant models, and push them into an "instance store" where anyone else might find the data when they need it.
https://developers.soundcloud.com/blog/building-the-next-soundcloud

What's really exciting is an expressive model that allows code to state what dependencies it has. The transport and fulfillment of needed data- what intermediary stores the data gets to and how pending views are signaled availability- is a more mechanistic, rote, already faced task, albeit one that each company seems to tackle on their own. The step further- declaring and modeling dependencies, is what makes GraphQL an interesting capabilities.

Soundcloud's 3 year old blog post is a good reference to show that "instance stores"- these clientside object database services- have been around for a good while, and can be done fine with REST as easily as without.

At my company we have a bunch of content that's only archived on SoundCloud. The main barrier I've had to backing up original uploads (only available through the web interface) is the terrible reliability of all the AJAX calls. Even with browser automation, it requires a LOT of error-handling just to navigate between resources successfully.

It seems that all these microservices[1] are there for the sake of blogging about using microservices[2] as there haven't been any new significant new features delivered in years, and the whole application now seems to be delivered through AJAX calls.

[1]: https://developers.soundcloud.com/blog/building-products-at-soundcloud-part-3-microservices-in-scala-and-finagle
[2]: http://philcalcado.com/2015/09/08/how_we_ended_up_with_microservices.html

Backend Engineer (Scala) | SoundCloud (Discovery/Recommendations) | Berlin | Onsite | Full-time | Relocation

I'm an engineer on SoundCloud's Recommendations team. We are looking for scala engineers to help users find lit tracks on the world's largest audio platform. You'll work alongside data scientists and engineers in a stack based on Spark, Scala, Finagle, and Cassandra.

SoundCloud is a wonderful place to work and Berlin is an amazing city to live in. I relocated from Canada and haven't looked back.

Empfehlungen sind die Zukunft!

job link: https://soundcloud.com/jobs/2016-08-04-backend-engineer-discovery-berlin
blog: https://developers.soundcloud.com/blog/tracks

PS - ping me on LinkedIn (https://www.linkedin.com/in/aaronmblevin) so I can refer you!