Reviewable Reviews

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

Reviewable mentions (21)

• A list of SaaS, PaaS and IaaS offerings that have free tiers of interest to devops and infradev

  Reviewable.io — Code review for GitHub repositories, free for public or personal repos. - Source: dev.to / over 2 years ago

• The GitHub for Code Review UI Needs Serious Innovation

  Yep, I agree! I work at, and use, Reviewable (https://reviewable.io) and we're the best way to review code on GitHub because we've focused on making the whole process better at every step. We've improved diffing, not only for large files (we support larger files than GitHub does) but also for understanding that diff. Have you ever reviewed a PR twice, but the second time around all your comments are gone and you... - Source: Hacker News / almost 3 years ago

• Software Engineering at Google

  Https://reviewable.io is the earliest full-powered Critique alternative for GitHub. It supports some cool things Critique doesn't/didn't, such as reviewing multi-commit branches (also across history-rewriting force-push cleanups), and indicating exactly the nature of your comment (just FYI, or you want this to be changed before you'll give your approval). (I was an intern in the initial making of Critique, and... - Source: Hacker News / about 3 years ago

• Codereview: Should the Go project stop importing GitHub PRs?

  The linux kernel, which is open source and does want contributors, is doing more-or-less just fine with an email-based PR and review flow. If it's an open source project, it should be using an open source review platform that allows improvements and specialization of the code hosting too. Using github, where the review tools are bad and can't be improved by an outsider, is a slap in the face to open source.... - Source: Hacker News / about 3 years ago

• Show HN: Visibly – More Collaborative and Efficient Code Reviews on GitHub

  >See reviewer presence so that you can see if someone is already reviewing and avoid unnecessary pings. >Visibly values privacy and security above all else These two things seem squarely at odds. Personally, I don't want my code review tool announcing to developers when I'm looking at their PR. The fact that it's a Chrome extension would also be a big blocker for me. I run a dev team, and I wouldn't... - Source: Hacker News / about 3 years ago

DEV.to mentions (664)

• 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 / 1 day 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 / 8 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

• Domain Search to Render: How the web works behind the scenes

  To think that all of this happens under the hood when I’m just trying to access YouTube to listen to my favorite music playlists to go through the day is insane! It all happens so quickly… to think that all eleven of these steps occur instantly when I was first entering a website like https://dev.to, for instance, is mind-blowing. - Source: dev.to / 13 days ago