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

BitDive Reviews

DEV.to mentions (669)

• Building the flagship (2): a live DataGrid that queries Postgres on every keystroke

  Nothing you write. The grid's controls are the same data-flv-* conventions from part 3: the search box is a data-flv-change input that sends {"q": ""}, a filter pill is a data-flv-click with a data-flv-value-estado, a sortable header sends {"sort": "cargo"}. The framework serializes those into the socket message; your loop reads them from frame.payload. The diff engine sends only the s that changed. Keyed diffing... - Source: dev.to / about 13 hours ago

• How to find a device by its MAC address

  You can collect all of that by hand, or let a scanner do it in one pass. DeviceShelf resolves vendor, hostname, services and open ports for every device on the network and turns them into an actual identification; the same IEEE data behind our lookup page ships inside the app. For the full detective story, see the guide on identifying an unknown device. - Source: dev.to / 5 days ago

• "My pending() Function Learned to Draft Against Nested Comments. My audit() Function Never Learned to Look for Them."

  Def _walk_comments(comment): """Yield this comment and every comment in its subtree, at any depth.""" yield comment for child in comment["children"]: yield from _walk_comments(child) Def audit(): ... for a in my_articles(): if not a["comments_count"]: continue for root_comment in api(f"/comments?a_id={a['id']}"): for c in... - Source: dev.to / 8 days ago

• 🍣 Sushi RS: SVG Sushi Components for Rust Frontends.

  So I came across the Frontend Challenge: Comfort Food Edition on dev.to, and I thought: "Hey, what if I build a Rust crate that lets you render SVG sushi directly in your WASM frontend? How hard can it be?". - Source: dev.to / 9 days ago

• 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 / 10 days ago

BitDive mentions (2)

• 5 Jackson Configuration Changes That Silently Break Your Microservices

  BitDive captures the actual serialized HTTP exchanges from your running application. Trigger the same API call before and after the configuration change. BitDive compares the real outgoing payloads:. - Source: dev.to / 6 months ago

• Your Service Passes All Tests But Breaks Production: Detecting Inter-Service API Regression

  TL;DR: The most dangerous bugs in microservices are not inside a service. They are between services. A code change can make a service pass all its local tests while silently altering what it sends to downstream APIs: different payload, missing header, changed error format. These regressions are invisible to unit tests, hard to catch with contract tests, and expensive in production. BitDive detects them by... - Source: dev.to / 6 months ago