SShortSingh.
Back to feed

DEV Community Updates Challenge Rules: One Submission Per Prompt, Stricter Deadlines

0
·10 views

DEV Community has announced updated guidelines for its challenge program, effective for all future challenges after this post. Going forward, participants will be limited to one submission per prompt, though a single entry can still qualify for multiple prize categories. Projects must also be created within the official challenge timeframe unless an exception is explicitly stated in the announcement. Any code commits made after the submission deadline will not be considered, and participants who cannot account for late commits in their readme risk disqualification. The changes do not affect currently running challenges, such as Bug Smash and Frontend Challenge: Comfort Food Edition.

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)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Punk: A Perl MVC Framework That Compiles All Routes at Boot Time

Punk is a new Perl MVC web framework designed to shift as much processing work as possible from request time to application boot time. By resolving all routes, controller methods, and middleware guards during startup, the framework reduces per-request overhead and surfaces configuration errors before the app begins serving traffic. The framework supports standard HTTP routing, WebSockets, Server-Sent Events, signed cookie sessions, CSRF protection, CORS handling, and OpenAPI 3.1 integration. It uses layered YAML configuration with built-in secrets redaction, and is built on a set of companion C-backed modules including a preforking PSGI server called Hyperman. A CLI tool, punk new, generates a fully functional application scaffold rather than a bare stub.

0
ProgrammingDEV Community ·

Developer finds three personal verification scripts passed while the code they checked was broken

A solo developer who relies on self-written scripts to verify his work discovered that three separate checks reported success even though the underlying content or action they were meant to validate had failed. The first script validated row structure in a markdown log by counting separators, but passed a row where a status value was placed in the wrong column, catching shape rather than meaning. A second script failed to detect a missing paragraph because it measured separator counts, which remained unchanged after a botched insertion. A third and most consequential check confirmed an article had been saved in a web editor, but was reading the in-window state rather than the actually stored draft, causing a key disclosure paragraph to be silently lost. The developer concluded that passing checks can mislead when they are too shallow, aimed at the wrong location, or read transient rather than persisted state.

0
ProgrammingDEV Community ·

Study: Human Reviewers Miss 1 in 3 Dangerous AI Agent Commands in Testing

A study simulating 40,000 AI agent approval scenarios found that human reviewers failed to catch approximately 33% of genuinely harmful commands. The research focused on 'human-in-the-loop' checkpoints, where a person must approve or reject an AI agent's proposed action before it executes. Investigators found the core problem is not reviewer negligence but a lack of contextual information at the moment of decision, as dangerous commands often appear harmless without visibility into prior steps in the agent's chain. For example, a file-deletion command targeting a seemingly safe directory could be catastrophic if the agent had earlier redirected that path to a production environment — a detail typically hidden from the approver. Researchers suggest that surfacing full action traces alongside approval prompts, combined with automated critic models to pre-filter high-risk commands, could significantly improve oversight reliability.

0
ProgrammingDEV Community ·

Tutorial: Build an Encrypted Command-Line Password Manager in Python

A new developer tutorial on DEV Community walks through building a custom command-line password manager using Python 3.11 and the cryptography library. The project uses Fernet symmetric encryption to ensure stored credentials remain confidential and tamper-evident, even if the underlying file is stolen. Developers are guided through creating a PasswordManager class with methods for key generation, adding passwords, and retrieving them via decryption. The tutorial also integrates pyperclip to automatically copy retrieved passwords to the clipboard for everyday convenience. The guide targets developers who want full control over their credential storage without relying on browser-based or plaintext solutions.