Skip to main content

Home/ Larvata/ Group items tagged music

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
crazylion lee

phanan/koel: A personal music streaming server that works. - 0 views

github.com/koel

server music personal opensource

shared by crazylion lee on 08 Dec 16 - No Cached
  • crazylion lee on 08 Dec 16
     
    "A personal music streaming server that works"
crazylion lee

JavaScript Systems Music - 1 views

teropa.info/...javascript-systems-music.html

music javascript audio

shared by crazylion lee on 05 Nov 16 - No Cached
  • crazylion lee on 05 Nov 16
     
    "Learning Web Audio by Recreating The Works of Steve Reich and Brian Eno"
crazylion lee

A.I. Experiments - 0 views

aiexperiments.withgoogle.com

machine_learning AI GOOGLE python

shared by crazylion lee on 24 Nov 16 - No Cached
  • crazylion lee on 24 Nov 16
     
    " Explore machine learning by playing with pictures, language, music, code, and more."
crazylion lee

The Daredevil Camera - 0 views

www.ribbonfarm.com/...the-daredevil-camera

camera daredevil

shared by crazylion lee on 02 Jul 16 - No Cached
  • crazylion lee on 02 Jul 16
     
    "Once upon a time I was reading a Popular Mechanics article, the title of which eludes me. Something about playing different music for different parts of a dance floor. They were describing a way to focus sound towards different people."
crazylion lee

Classifier by bhrigu123 - 0 views

bhrigu123.github.io/classifier

python file

shared by crazylion lee on 02 Mar 16 - No Cached
  • crazylion lee on 02 Mar 16
     
    "Organize files in your current directory, by classifying them into folders of music, pdfs, images, etc."
張 旭

Trunk-based Development | Atlassian - 0 views

www.atlassian.com/...trunk-based-development

git development

shared by 張 旭 on 11 Oct 21 - No Cached
  • Trunk-based development is a version control management practice where developers merge small, frequent updates to a core “trunk” or main branch.
  • Gitflow and trunk-based development. 
  • Gitflow, which was popularized first, is a stricter development model where only certain individuals can approve changes to the main code. This maintains code quality and minimizes the number of bugs.
  • ...20 more annotations...
  • Trunk-based development is a more open model since all developers have access to the main code. This enables teams to iterate quickly and implement CI/CD.
  • Developers can create short-lived branches with a few small commits compared to other long-lived feature branching strategies.
  • Gitflow is an alternative Git branching model that uses long-lived feature branches and multiple primary branches.
  • Gitflow also has separate primary branch lines for development, hotfixes, features, and releases.
  • Trunk-based development is far more simplified since it focuses on the main branch as the source of fixes and releases.
  • Trunk-based development eases the friction of code integration.
  • trunk-based development model reduces these conflicts.
  • Adding an automated test suite and code coverage monitoring for this stream of commits enables continuous integration.
  • When new code is merged into the trunk, automated integration and code coverage tests run to validate the code quality.
  • Trunk-based development strives to keep the trunk branch “green”, meaning it's ready to deploy at any commit.
  • With continuous integration, developers perform trunk-based development in conjunction with automated tests that run after each committee to a trunk.
  • If trunk-based development was like music it would be a rapid staccato -- short, succinct notes in rapid succession, with the repository commits being the notes.
  • Instead of creating a feature branch and waiting to build out the complete specification, developers can instead create a trunk commit that introduces the feature flag and pushes new trunk commits that build out the feature specification within the flag.
  • Automated testing is necessary for any modern software project intending to achieve CI/CD.
  • Short running unit and integration tests are executed during development and upon code merge.
  • Automated tests provide a layer of preemptive code review.
  • Once a branch merges, it is best practice to delete it.
  • A repository with a large amount of active branches has some unfortunate side effects
  • Merge branches to the trunk at least once a day
  • The “continuous” in CI/CD implies that updates are constantly flowing.
1 - 6 of 6
Showing 20▼ items per page