Age Trumps Gender in Photo Ratings, Reciprocity Myth Busted: 24M Data Points

·1 views

An analysis of 24 million photo ratings from the app Rate Me reveals that a subject's age is the strongest predictor of their score, with ratings declining steadily from the 18–24 bracket through to 55+, a drop of up to 1.9 points. Men rating women showed the largest age-related decline, while women rating men peaked at same-age pairings and fell sharply when rating older men. Age-gap patterns also differed by gender: men gave higher scores the older they were relative to the woman rated, whereas women and same-gender raters both peaked near same-age pairings. A separate test involving 5,207 users with at least 100 ratings given and received found virtually no correlation between generosity as a rater and scores received in return. The findings suggest that so-called rating karma does not exist, likely because raters and subjects are matched randomly rather than reciprocally.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Nile uses session variables to isolate Postgres tenants in multi-tenant B2B apps

Nile is a Postgres-based platform designed for multi-tenant B2B applications, allowing developers to isolate tenant data within a single database using a tenant_id column and a session variable rather than separate databases per customer. A developer testing the free tier found that setting the session variable correctly filters rows by tenant, and cross-tenant writes are actively blocked with an explicit error. However, connections without the session variable set can read rows across all tenants by design, a deliberate choice to support admin and migration workflows. This means the responsibility for setting tenant context on every request falls on the application layer, which could be a risk in pooled-connection environments if not handled carefully. Nile raised an $11.6 million seed round led by Benchmark in January 2024 and was co-founded by Sriram Subramanian and Gwen Shapira.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How InnoDB Uses a Hybrid MVCC Approach Across MySQL Isolation Levels

MySQL's default storage engine, InnoDB, uses a hybrid approach to concurrency control — applying MVCC only to read operations while relying entirely on locking for updates, inserts, and deletes. Unlike PostgreSQL, which stores full row versions in the same heap structure, InnoDB stores only the delta (the difference between versions) in a separate structure called the undo log. When a transaction reads a row, InnoDB builds a snapshot of in-flight transactions at the first SQL statement and keeps it frozen for the transaction's lifetime to determine row visibility. For write operations, InnoDB acquires the appropriate lock and fetches the latest row version directly, bypassing the version chain altogether. Repeatable Read is InnoDB's default isolation level and serves as the foundation from which other isolation levels differ only in minor ways.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

A Practical Guide to Mastering No-Code Web Development in 2026

No-code development has evolved far beyond simple landing pages, now powering production apps, MVPs, and full businesses across tools like Webflow, Bubble, and Zapier. A newly published 2026 guide outlines a structured learning path for both developers and non-developers looking to build real products without writing traditional code. The guide emphasizes starting with low-stakes projects to understand how tools handle data, logic, and UI before tackling serious builds. It identifies poor data modeling — not design — as the most common reason no-code projects fail, and advises learning conditional logic as the core skill. The guide also warns against common mistakes such as choosing the wrong category of tool, ignoring mobile optimization, and trying to force a single platform to handle every function.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Shield Node.js AI Agents from Supply Chain Attacks Using Sandboxing

AI agents capable of executing code or installing packages are vulnerable to supply chain attacks, where compromised dependencies can exfiltrate data or escalate privileges without any malicious prompt from the user. The 2019 RubyGems 'strong_password' incident demonstrated how pre-install scripts can silently steal environment variables and sensitive files — a risk that directly applies to autonomous agents. A developer building AI systems such as FarahGPT and NexusOS spent weeks designing a Node.js-based mitigation strategy called the Execution Context Guardian. The approach uses Node.js's built-in vm module to run agent-initiated code inside a strictly isolated context, whitelisting only approved globals and blocking direct access to dangerous functions like child_process.exec. The goal is to prevent agents from inadvertently triggering malicious package scripts or making unauthorized network calls, even when acting with seemingly helpful intent.

0 comments Read more at DEV Community