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

Linear Reviews

DEV.to mentions (665)

• Woof Are You, Really? A Dog Personality Quiz Built in a Weekend

  This is a tiny, silly personality quiz built for the DEV.to Weekend Doggos challenge. Answer questions about your Saturday mornings, your feelings on doorbells, and your ideal compliment — and find out which dog breed you truly are today. (Not forever. Today. Check back tomorrow, you might be a different dog.). - Source: dev.to / about 5 hours ago

• Stop Arguing About Which Model Is Best. Build a Two-Tier Habit Instead.

  Verifiable only with effort. Anything touching the filesystem, package installs, CI config, database changes. Wrongness here is quiet and expensive. These get the strongest model I have and a sandboxed dry run before anything executes. I wrote a separate piece on dry-running assistant-written shell commands because this category keeps hurting people. - Source: dev.to / 2 days ago

• My Comment-Reply Pipeline Picks One Winner Per Thread. Two Commenters Broke That.

  Def _pending_leaves(comment): if not comment["children"]: if comment["user"]["username"] != ME: yield comment return for child in comment["children"]: yield from _pending_leaves(child) Def _pending_entries(comment, drafted_codes): for leaf in _pending_leaves(comment): if leaf["id_code"] in drafted_codes: continue yield { ... - Source: dev.to / 2 days ago

• Your first Fitz LiveViews component, twice: SSR and WASM from one source

  In part 1 I made the pitch: real-time UI in one language, no JavaScript build. Now let's build something and ship it two ways from the same source. - Source: dev.to / 9 days ago

• My Comment-Reply Queue Draft One Reply to a Thread and It Went Deaf to Every Follow-Up After That

  Def pending(): try: drafted_text = open(DRAFTS, encoding="utf-8").read() except FileNotFoundError: drafted_text = "" drafted_codes = set(re.findall(r"^## (\S+)", drafted_text, re.M)) out = [] for a in api(f"/articles?username={ME}&per_page=100"): if not a["comments_count"]: continue for c in api(f"/comments?a_id={a['id']}"): if not... - Source: dev.to / 12 days ago

Linear mentions (162)

• The Tradeoff That Slows Production Teams Down: Flexibility vs Actually Shipping

  Speed matters. Not speed in sprint or linear dashboards. Not speed in story points. - Source: dev.to / 3 months ago

• Freshworks Just Shipped an MCP Gateway Inside Its ITSM Platform. Here's What That Actually Changes.

  Model Context Protocol, for context, is the emerging standard for letting AI agents pull live data from external systems without custom integration code. Freshworks has implemented it as a native layer in Freddy AI, which means agents can now reach into Notion, ClickUp, Linear, Workday, Rippling, and the rest of the enterprise stack — not through brittle webhooks or bespoke connectors, but through a standardized... - Source: dev.to / 3 months ago

• How to Document and Track Technical Debt

  Issue trackers: GitHub Issues, Linear, or Jira work well because technical debt records live in the same tool as feature work. This makes them easier to pull into sprint planning and keeps the debt backlog visible alongside the feature backlog. The main risk is that debt issues get buried under feature issues without careful labeling and triage discipline. - Source: dev.to / 3 months ago

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

  Linear and similar tools can track velocity metrics per area of the codebase over time, making the before/after comparison straightforward to document. - Source: dev.to / 3 months ago

• Master the in demand of salary negotiation and system design: What Fails

  Most engineers fail salary negotiations because they use vague statements like "I work hard" or "I’m a good teammate" instead of quantified, verifiable impact. After 15 years of negotiating offers, I’ve found that engineers who tie their ask to concrete business outcomes land 30% higher offers than those who don’t. For example, instead of saying "I improved the API", say "I reduced API p99 latency by 400ms, which... - Source: dev.to / 3 months ago