DEV.to Reviews

1. jorge

   · CEO at Escuela de Formación Técnica Chile SPA · over 6 years ago
   It is a nice mini-blog, it's for free and such but

   As a mini-blog, it is a nice alternative for Medium to publish and share information about programming.

   However, the community and the organization are biased toward social justice (and they are open to it). You can read its Code of Conduct, it is so vague and politically leads (I prefer a term of service because it defines fair rules for everybody). So it alienates developers that we don't care about politics in pro of people that want to talk about any other topic such as sexuality, how women are unprivileged, and such. It even mandates to use inclusive language. Good grief.

   My main complaint is the quality of the community. It is not StackOverflow (so we don't want to ask for an answer here), and most of the top topics are clickbait, such as "how to become a rockstar developer in ... days", "100 tips to become a better programmer" (and it doesn't even talk about programming).

   Technically this "mini blog" site allows us to use markdown, and it is okay. However, the whole experience is really basic. Even the template is ugly.

   Competitors: Medium

   Pros:    Free

   Cons:    Social justice|Basic features|Quality of content

CodeClimate Reviews

DEV.to mentions (674)

• Fixing Delicate Cache Mismatches in a Brownfield SPA: A Pragmatic Solution

  On DEV (powered by the open-source Forem codebase), we have a hybrid architecture that blends Rails server rendering, Fastly edge caching, and lightweight client-side navigation (via InstantClick). This setup delivers sub-100ms page transitions, but partial page swaps combined with aggressive edge caching create delicate deployment challenges. - Source: dev.to / 1 day ago

• Building the flagship (3): a packaged UI library, i18n, and one-command Docker

  Parts 4 and 5 showed the flagship's auth and its live grid. This one is about reuse: the app is built almost entirely from packaged components, and this is how you'd build yours. - Source: dev.to / 4 days ago

• Claude Code Attempted 752 /proc/*/environ Reads. 256 Succeeded. Codex: 0.

  Per-syscall interception is the layer that closes this gap. Grith sits between the agent process and the kernel, scoring every operation before it executes - not what the agent claims to be doing, but what it actually does. The process census, the credential file opens, the MCP initialisation, the network connections: all of it is visible, all of it is scored, and any of it can be blocked by policy without... - Source: dev.to / 4 days ago

• Three model calls, and none of them reads a price

  Plinkie is built by Business Data Solutions, a Dutch consulting and training firm that helps organisations put their data to work. This system was built by one person in ten days, runs in two fully separate Google Cloud projects, and costs under $2 per night to operate. The infrastructure is OpenTofu, the services are Python 3.13, and the site is Next.js. - Source: dev.to / 4 days ago

• Baklava: Generate API Documentation and Type-Safe Clients from Scala Routing Tests

  Path("/users/{userId}")( supports( GET, pathParameters = pLong, summary = "Get user by ID" )( onRequest(pathParameters = 1L) .respondsWithUser .assert { ctx => ctx.performRequest(routes).body.id shouldBe 1L }, onRequest(pathParameters = 999L) .respondsWithErrorResponse .assert { ctx => ctx.performRequest(routes)... - Source: dev.to / 7 days ago

CodeClimate mentions (19)

• How to Document and Track Technical Debt

  Automated analysis tools: SonarQube, CodeClimate, and Codacy detect code-level debt automatically: cyclomatic complexity, code duplication, dependency staleness, and coverage gaps. These tools supplement but don't replace the architectural and business-logic debt that requires human judgment to identify and document. - Source: dev.to / 4 months ago

• How to Write a Technical Debt Remediation Plan for Non-Technical Stakeholders

  CodeClimate and Codacy can generate before/after metrics for code quality that make the starting and ending states concrete rather than subjective. - Source: dev.to / 4 months ago

• Stop writing code that future devs will hate you for

  CodeClimate quantifies maintainability so teams can’t hand-wave garbage away. - Source: dev.to / 11 months ago

• Essential Resources for Software Technical Debt Management

  Code Climate: Link - Automated code review and quality analysis for codebase health. - Source: dev.to / about 1 year ago

• 15 unbreakable laws of software engineering that keep breaking us

  Use tools like SonarQube or CodeClimate to spot the high-risk 20%. Then fix one thing at a time not everything at once. This isn’t Dark Souls. - Source: dev.to / over 1 year ago