Promyze Reviews

LaunchDarkly Reviews

Promyze mentions (28)

• 7 frustrations to avoid with code review best practices

  Comments should target what’s necessary to update in the code before it gets merged. All other discussion topics should be addressed in a dedicated session gathering all developers in the team. That’s the framework suggested by Promyze, whose code review extensions offer a smooth way to convert code review comments into coding practice suggestions; this practice will be discussed and validated (or not) during a... - Source: dev.to / about 1 year ago

• How to accelerate your code reviews?

  Promyze is a knowledge-sharing platform for developers and provides integrations with IDE and code reviews (GitHub, GitLab, Azure DevOps, Bitbucket, and Helix Swarm). With the code review plugins, you can create a best coding practice from a comment, and the code is sent to Promyze along with your best practice proposal. You thus avoid long 1:1 discussions during code reviews. - Source: dev.to / over 1 year ago

• Writing clean code in Python

  At Promyze, we recently ran a webinar with our partner Arolla (the replay is in French) on How to write clean code in Python? We share in this post an extract of the discussed practices. - Source: dev.to / over 1 year ago

• 20 knowledge types and information sources for developers

  Developers’ gestures in writing source code according to the team practices. This is about properly writing the source code in the developer’s context. These best practices should be precisely defined in a team and at the company level, continuously maintained, and regularly discussed. Integration during code reviews and in the IDE are a must-have. Tools: Promyze. - Source: dev.to / over 1 year ago

• What’s a best coding practice, and when to create it?

  With this in mind, we created Promyze, a solution that centralizes your team’s best coding practices. - Source: dev.to / over 1 year ago

LaunchDarkly mentions (37)

• How to Add Paid Features to Your SaaS Apps

  This kind of goes without saying since it's the opposite of the first don't I listed, but it's worth restating and giving some examples. Using tools from third parties means taking advantage of what they have done so you don't have to do that work. This means you are free to build things that make your app special. I like to use feature flag tools for this. Some examples are LaunchDarkly, Split, and AWS App... - Source: dev.to / about 1 month ago

• Pivoting a million dollar DevTool startup

  Taplytics is a broad A/B testing platform for marketing teams. While DevCycle is a feature flagging tool built for developers. Taplytics actually has feature flagging, but DevCycle is much more focused and plans to compete directly with incumbents like LaunchDarkly by building a better developer experience (more on how later). But with Taplytics they built so many features and every customer was using them in a... - Source: dev.to / 5 months ago

• Arc Update - 1.20.1 (43987)

  I had a custom rule added to Little Snitch that blocked the following domains: launchdarkly.com, clientstream.launchdarkly.com, mobile.launchdarkly.com. Source: 6 months ago

• Feature flags implementation in Nest.js 😻

  There are however Saas to implement directly a feature management system. Several solutions exist like LaunchDarkly, Flagsmith or Unleash.io. Using a SaaS (Software as a Service) feature flagging solution offers the advantage of a faster and more straightforward implementation process. These services are readily available and can be quickly integrated into your project. - Source: dev.to / 9 months ago

• Boost DX, Enhance UX, and Skyrocket Profits! Dive into a sub-50ms world with Edge Feature Flags 🚀

  Currently, there are numerous feature flag systems available. Options include our own company's open-source system, "Bucketeer", and the renowned SaaS "LaunchDarkly" among others. When comparing these, the following considerations might come into play:. - Source: dev.to / 9 months ago