Cool. Is there a simple "howto" on running this repo with training on W&B for a programmer like me who has never done model training flows? Maybe you could share the steps you took?
There's not much to it... it took longer to spin up the cloud machine than it did to kick off the training run. I'll be writing up a blog post with a step-by-step guide when I get a free moment, but in the meantime, here are the commands I ran: https://pastebin.com/sdKVy0NR
Hey saaaaaam . I'd love to pick your brains a bit on this. I'm working on a web3 protocol ("Legato") relating to many of these issues. Any way we can connect? (I can't find a way to DM you on HN). roy at osherove .dot [com]
Open Source Blockchain music registration & Royalties: I'm a fullstack dev working on a blockchain project (eth/polygon) for music registration and royalties on chain. Would love to work with anyone with web3 backend(solidity) / frontend(react) experience, that is passionate about disrupting the music industry - for now it will just be a big open source permissionless project. But it could end up being a nice startup with many hooks to use for profit on top: from distribution to integrations - it's a blue ocean. (email in my profile)
I believe we need to stop, as developers, to contribute our expertise to enabling such blatant surveillance that hurts much more than it helps. We're ruining our own and our children's future by writing the code that enables this, by teaching people how to write such code, how to test such code, how to deliver such code. It's on us.
You can't teach someone how NOT to write a program, speaking on the technical side. The more you know the more capable your programs can be. It's about one's morals after that.
I'll add after 20+ years:
- Being able to communicate ideas > Being a great technical developer
- For every great developer that's an asshole, you can find a great developer that won't be an asshole. Don't keep assholes. Google the "no asshole rule".
- Making the team feel safe to discuss stuff they don't know freely and ask questions that might seem stupid in other teams makes for a great team that's not afraid to challenge assumptions and break through with new skills.
- TDD is a skill just like refactoring. Learn when it makes sense.
- 80% of architects in enterprise don't have the skills needed from them. including the things stated above.
- Learning the Theory of Constraints and applying it to find bottlenecks in the process, pipelines and structures of your teams/projects is one of the most useful things you can apply to become more productive.
- Learning what to measure and what not to measure, lagging vs leading indicators can help you communicate to management about what changes truly need to happen to make your team work more effectively.
- Whiteboards (and remotely, miro boards) are very effective and can be used for easily 50% of meetings. But aren't.
> Whiteboards (and remotely, miro boards) are very effective and can be used for easily 50% of meetings. But aren't.
I agree that it's great to have a visualization aid, especially in remote meetings. But in my experience, for the needs of most meetings, Miro boards are a cumbersome, over-featured sink of time and effort. Then they invite you to leave them standing as sole documentation of the details of a meeting's outcome, which they're not very good at. Use them wisely!
Metrics in software is a bag of issues in most companies I see. But there ARE useful ways to use metrics that actually help (software). I did a talk about this at GOTO: Lies, Damned lies, and metrics.
https://www.youtube.com/watch?v=goihWvyqRow
Where is the music being sourced from? As a music creator, how can I add my music to be visible here?
Another question (which contradicts my first question):
Aren't you helping to create another "race to the bottom" where free music always wins over paid?
