Ziflow Reviews

1. Guest

   about 4 years ago
   Improved Creative Workflow

   We were in the 'stone age' before Ziflow - we were using email, dropbox and a project management platform to collect feedback on creative files/projects - it was a nightmare to manage. Ziflow helps streamline this process, and much more. Some features we love include... Ziflow accepts so many different creative file types (we haven't found any they don't accept). Workflows with automated stages make sure we have the right people reviewing at the right time. Security was important to our company, and Ziflow goes well beyond what the competitors offer. Customer support is great - if we ever have questions or problems they quickly respond and address.

   🏁 Competitors: Proof HQ

   👍 Pros:    Online proofing|Collaboration|Great customer support|Highly customizable
2. Guest

   about 4 years ago
   Review & approve any creative file

   I've tried other online proofing software but Ziflow is head and shoulders above the others. It's a bit more money than some of the other cheaper proofing solutions but you certainly get you money's worth with features and customer support.

   🏁 Competitors: Proof HQ

   👍 Pros:    Great customer support|Customer support|Easy to use|Secure

CodeClimate Reviews

Ziflow mentions (0)

CodeClimate mentions (11)

• free-for.dev

  Codeclimate.com — Automated code review, free for Open Source and unlimited organisation-owned private repos (up to 4 collaborators). Also free for students and institutions. - Source: dev.to / over 1 year ago

• How To Use Code Climate To Improve Software Quality

  Want to know how to enforce allowing only high-quality software into production? Check out this post on how to use CodeClimate can help you do just that! #DevOps #SoftwareDeveloper #softwaredevelopment #SoftwareEngineering #webdevelopment #codequality. Source: almost 2 years ago

• RFC: A Full-stack Analytics Platform Architecture

  Ideally, software can quickly go from development to production. Continuous deployment and delivery are some processes that make this possible. Continuous deployment means establishing an automated pipeline from development to production while continuous delivery means maintaining the main branch in a deployable state so that a deployment can be requested at any time. Predecos uses these tools. When a commit goes... - Source: dev.to / about 2 years ago

• Adding coverage to CI pipeline?

  The new code should not drop existing code coverage I've found in practice mainly catches changes to existing code that lack proper updates to existing tests. Our company uses Code Climate for these checks, so we don't have to manage / write our own tooling for this purpose. Source: over 2 years ago

• Node.js best practices list (July 2021)

  TL;DR: Using static analysis tools helps by giving objective ways to improve code quality and keeps your code maintainable. You can add static analysis tools to your CI build to fail when it finds code smells. Its main selling points over plain linting are the ability to inspect quality in the context of multiple files (e.g. Detect duplications), perform advanced analysis (e.g. Code complexity), and follow the... - Source: dev.to / almost 3 years ago