CodeClimate Reviews

i3 Reviews

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

i3 mentions (90)

• Automatic Visual Feedback for System Volume Change in I3wm via Dunst

  I switched to the i3 tiling based window manager. Because it's a whole different environment and thinking, it was very different from what I was used to. The volume buttons were working on my keyboard, but I didn't get any visual feedback. Furthermore, the volume percentage could go down below zero and increase up to more than hundread percent. There were times when I was confused why the keys stopped working, but... - Source: dev.to / 2 days ago

• "We understand" ;)

  This is partially why I use tools like i3 (/ sway). I like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. It just works. It is boring in the best way possible. Source: 7 months ago

• what machines have you used for development, and what do you prefer?

  I use MacBook Pro (Retina, 15-inch, Mid-2014) with Manjaro as OS using i3 as a window manager. It isn't perfect, but I'm thrilled with it. I have been a Mac OS user for the last 15 years and wouldn't change what I have now for a Mac OS because I don't need more than what I'm using for development. Source: 12 months ago

• Machine for pentesting and general use?

  For daily usage I really like kubuntu with i3wm, but it takes some configuration and getting used to the shortcuts, but it's well worth it. Source: about 1 year ago

• What's the difference between Gnome and KDE? Do applications written for one work in the other?

  Some window managers are meant to be used as-is, and provide a minimalist yet functional environment that use very little resources or give power users an almost HUD-like interface. Examples of those window managers are OpenBox and i3wm for X, and Weston and Hyprland for Wayland. Source: about 1 year ago