Skip to main content

Home/ Larvata/ Group items tagged ai

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
crazylion lee

Approaching (Almost) Any Machine Learning Problem | Abhishek Thakur | No Free Hunch - 0 views

blog.kaggle.com/...arning-problem-abhishek-thakur

ai machine learning

shared by crazylion lee on 30 Jan 17 - No Cached
  • crazylion lee on 30 Jan 17
     
    "Approaching (Almost) Any Machine Learning Problem | Abhishek Thakur"
crazylion lee

GitHub - eriklindernoren/ML-From-Scratch: Bare bones Python implementations of various ... - 0 views

github.com/...ML-From-Scratch

machine learning ai

shared by crazylion lee on 27 Feb 17 - No Cached
  • crazylion lee on 27 Feb 17
     
    "Bare bones Python implementations of various Machine Learning models and algorithms."
kickdesk

禁止Uber之后，日本打算换一种方式解决"打不到车"的问题 - 0 views

www.pingwest.com/o-release-ai-based-taxi-system

shared by kickdesk on 11 Mar 17 - No Cached
  • kickdesk on 11 Mar 17
     
    這也是旅遊指數可能的運用
張 旭

The Squeaky Blog | Why we don't use a staging environment - 0 views

squeaky.ai/...dont-use-a-staging-environment

devops

shared by 張 旭 on 15 Apr 22 - No Cached
  • Pre-live environments are never at parity with production
  • multiple people use staging to validate their changes before release.
  • Branches are then constantly out of sync with each other, and problems often surface when you merge, rebase, and backfill hotfixes.
  • ...10 more annotations...
  • Big Bang releases
  • there is a lengthy suite of tests and checks that run before it is deployed to staging. During this period, which could end up being hours, engineers will likely pick up another task. I’ve seen people merge, and then forget that their changes are on staging, more times than I can count.
  • only merge code that is ready to go live
  • written sufficient tests and have validated our changes in development.
  • All branches are cut from main, and all changes get merged back into main.
  • If we ever have an issue in production, we always roll forward.
  • Feature flags can be enabled on a per-user basis so we can monitor performance and gather feedback
  • Experimental features can be enabled by users in their account settings.
  • we have monitoring, logging, and alarms around all of our services. We also blue/green deploy, by draining and replacing a percentage of containers.
  • Dropping your staging environment in favour of true continuous integration and deployment can create a different mindset for shipping software.
  • 張 旭 on 15 Apr 22
     
    "Pre-live environments are never at parity with production "
‹ Previous 21 - 24 of 24
Showing 20▼ items per page