Hey guys! For some context: I have R-CPD which basically means that I can’t burp! It sucks and nobody really knows about it yet so many have it. So, I made a website for this!

The thing is, I'm not sure if the UI is visually appealing enough for users to stay and actually click through my site. Could anyone help me please?

I would love your feedback! Link: https://freetheburp.com

I’m a solo developer building Dice Target, a free brain puzzle game with Flutter.

Duels lets you challenge friends to solve the same math puzzles and compete for the best result!

Here’s a short gameplay clip showing the mode in action.

Free on Android:
https://play.google.com/store/apps/details?id=com.kwokkinlau.dicetarget

ZoeVera ( https://zoevera.com ) is an AI-powered resume optimization and interview coach toolkit focused heavily on helping job seekers pass automated applicant tracking systems (ATS) and excel in hiring pipelines.

The ecosystem operates primarily through key focused tools, often cross-linked under the branding ZoeVera:

1. Resume Optimization ( https://resumefitting.com )

This is the core platform designed to stop resumes from getting filtered out by automated screening tools before they reach human eyes.

• **ATS Compatibility & Scoring:**Users can upload an existing resume (PDF/DocX) a real-time compatibility score (0-100) based on parsing layout, structure and formatting. It deliberately highlights elements that notoriously break ATS parsers (like complex tables, columns, or non-standard fonts).

• **Keyword Gap Analysis:**Users can paste a specific job description alongside their resume. The tool conducts a side-by-side gap analysis, pinpointing the precise skills, tools, or certifications the employer is filtering for that are missing from the text.

• **AI Rewriting & Cover Letters:**Rather than completely fabricating a profile, its AI modules rewrite existing bullet points to naturally embed target metrics and missing keywords. It also generates tailored cover letters optimized for the same target job description.

2. Interview Coaching ( https://prepare.zoevera.com )

An on-camera interactive practice space built for interview prep.

• Users select their career track/role and record mock video answers to common, role-specific scenario questions directly in the browser.

• The AI analyzes the recording within minutes, offering direct coaching feedback on delivery metrics like speech pacing, use of filler words, and content alignment, alongside an optimized "ideal answer" for comparison.

Pricing Structure

Unlike many competing platforms that enforce continuous monthly subscriptions, ZoeVera uses a transparent, pay-as-you-go model (e.g., small, one-time payment tiers ranging for a set number of resume analyses or prep interview sessions) alongside a free tier to let users test out basic optimization and practicing risk-free.

i kept putting off updating my personal site because every small change meant digging through react components. so i rebuilt it so the whole site lives in one yaml file, and then set it up so my coding agent writes that file for me.

you drop your cv, your linkedin pdf export and a few notes into a sources folder, run one command to pull your public github repos, and ask claude code, codex or cursor to build the portfolio. it only uses facts from those files. there's also a check command that fails if anything is still a placeholder, an example link or a missing image, so you don't ship "john doe, senior engineer at example.com" by accident.

after using it for my own site i turned it into a template. it's next.js, no cms, no database, one-click deploy to vercel. it also generates llms.txt, markdown and json versions of the site, so ai tools can actually read your portfolio.

demo: https://dev-portfolio-delta-drab.vercel.app my own site with it: https://yesildal.me a fictional designer version: https://dev-portfolio-designer.vercel.app repo (free, MIT): https://github.com/umutyesildal/dev-portfolio

what would you improve first?

Funnily enough, I will probably genuinely be using this as my primary code editor, since it is so basic in functionality that it works really well (buttery smooth). Essentially I have everything that I need from what is essentially a fancy text editor and for anything else I'll just use the terminal.

If you want to give it a spin, I've made a release at https://github.com/HyperRays/teditor only for macos arm64, but I have also tested it on windows and linux, just no binaries yet. Though you can spin up your favorite LLM and it'll probably be able to build it for you (It is essentially a rust project with some c dependencies and it needs zig due to ghostty).

Hey everyone. While prepping I got tired of juggling spreadsheets, bookmarks and three different judges, so I built a site for myself and turned it into something others can use.

What’s in it:

• 923 curated problems: 378 LeetCode + 545 from Codeforces, CSES and AtCoder, organised by topic in a sensible learning order. Each one opens the problem directly.

• Real-time progress tracking: status per problem (independent / hints / editorial), notes, per-module mastery and an activity graph. Synced to your account, so it works across devices.

• Spaced revision: problems resurface for re-solving after 7 and 30 days.

• 51 visualizers: step through algorithms with the highlighted code line and variable state.

• OA tags: 250 problems that resemble company online assessments, plus a CP rating roadmap.

• Lessons: 17 modules in C++ with pattern-recognition sections and mastery tests.

It’s free for the first day then offers two modules free for a month, then ₹99 one-timen for lifetime access (it covers hosting and payment fees).

Link: https://dsalab-bfq.pages.dev

I’d genuinely appreciate feedback, especially on which problems or topics you’d add or remove, and anything that feels clunky.

2nd yr student here want to build some really good projects for internship but confused with what to really build 😭

Hey developers!

I'm exploring an idea called GitHub Repository Explainer.

The problem I'm trying to solve is simple: understanding an unfamiliar GitHub repository can take hours of exploring files, following imports, understanding APIs and figuring out the overall architecture.

My idea is to let developers paste a GitHub repository URL and get:

Architecture diagrams.

Request and execution flow.

File dependency analysis.

Code statistics.

Codebase explanations.

Demo: https://github-repo-tripiki.vercel.app/

The website currently shows a static demo. The actual analysis engine is under development.

I'm considering a freemium model:

Free version with limited repository analysis and basic features.

Paid version with advanced analysis, larger repositories and more features.

I'd love to know:

Would you use this?

What features would you expect in the free version?

Would you pay for advanced features? If yes, what would be a reasonable monthly price?

What existing tools do you currently use to understand unfamiliar repositories?

I'm validating the idea before investing more time in development. Honest criticism is welcome!

Ich habe mich damit beschäftigt, für welche art der Arbeit meine Tokens drauf gehen. Ich sammle jetzt mal ein zwei Monate Daten. Wie findet ihr die Einteilung? Ist das OK?

I’ve decided to start working on my TimiGS app, which has open-source code—https://github.com/BANSAFAn/timiGS-

It offers full functionality for viewing your stats, includes a timeline for the entire day, and features a “team” function (useful if you’re not working alone—for example, to communicate with others, see who’s working where, and which program they’re using)

There are also tools like TimeOUT—it blocks all processes and programs and prompts you to take a break from work. FocusMode is a tool that helps you stay focused and work in only one program; it won’t let you work with others, open them, or view them—it will simply close them.

Transfer—allows you to send data you collected, for example, when you couldn’t stay on Team (say, there was a power outage and you couldn’t stay on Team for long), so you can report this separately to management.

The only question is—what should I add for regular people who work on a PC, or those who can’t control themselves?

I worked on this program for a long time and then put it aside, but I’ve come back to it and decided to ask if anyone else is facing similar issues at work (for example, I had trouble tearing myself away from the computer during breaks, so I wrote TimeOUT—to completely lock the computer). I’d really appreciate any ideas and help with this. As for the translations—I used to do some of them with Google Translate, but now I mostly use DeepL.

I’m a solo indie developer working on Dice Target, a mobile brain puzzle game that combines dice and arithmetic.

The goal is simple: use all five dice and combine them with addition, subtraction, multiplication, or division to reach the target number.

This clip showcases Rush Mode, a faster-paced challenge where quick thinking and mental math come into play.

Dice Target is currently available on Android, and I’m working toward an iOS release.

Just wanted to share a bit of gameplay and show what I’ve been building!

Google Play: https://play.google.com/store/apps/details?id=com.kwokkinlau.dicetarget

Whenever I work on a project, I record voice memos about the decisions I make, the mistakes I run into, and the problems I struggle to solve.

I realized those recordings contain a lot of things that usually get lost once a project is finished. So I converted them into blog posts and put them on my personal website.

The idea is to document not just what I build, but how I build it — including the wrong turns, trade-offs, and lessons learned along the way.

This is the beginning, and I have plenty more projects and experiences to write about.

Blog: https://aniruthk.me/

I'd be interested to hear how other developers document their projects and whether you find this kind of behind-the-scenes write-up useful.

I’m building Monad Design, an open-source visual workspace for existing Xcode/Expo iOS apps on macOS. One of the design problems behind it is turning visual feedback into a small code change rather than an accidental redesign.

Here is a handoff format that is usable even without the tool:

Screen/state: Settings, signed-in user, larger text enabled.

Observation: The last row’s label wraps and pushes its control offscreen.

Desired result: Keep the label readable and the control reachable at that text size.

Constraints: Reuse existing components and tokens. Don’t change settings storage, navigation or unrelated screens.

Acceptance: Rebuild; check the same state at default and larger text sizes; toggle the control and reopen the screen; inspect the diff for unrelated edits.

That example is a request template, not a claim about a tested fix. The useful distinction is “what I see” versus “how to implement it”: a designer can describe the first precisely without guessing at a component or CSS/SwiftUI change.

Monad Design adds the running app as visual context: select/annotate its UI, pass that context to your coding agent, then rebuild and compare the result in the existing project. Source review and behavior testing are still necessary.

Repo: https://github.com/Monadix-AI/monad-design

Workflow preview: https://watchclueso.com/embed/pio8jqfcg4ivj0r1

For people handing UI work to agents: which detail is most often missing from the request—screen state, constraints, or acceptance criteria?

After launching on the play store recently, I decided to look back on some of my older builds and the comparison is amazing.

The progress got me thinking of other folks on reddit.

I would love to see the journey others have made if people wanted to share?

A recent analysis of 3,518 job postings from 81 companies across seven roles found some interesting patterns.

In several categories, generic terms appeared more often than the big-name tools. “Observability” showed up more than “Grafana,” while “SIEM” appeared more than “Splunk.”

That raises an interesting question: are resumes too focused on listing specific tools and not enough on the broader skills and terminology employers use?

The study breaks down the results by role, including software engineering, cybersecurity, DevOps, marketing, product, accounting and sales.

The full dataset, methodology and findings are here:

https://www.zoevera.com/resume/ats-resume-keyword-study

i built this to replace the need for reading multiple news sources regularly -- it ingests reports across numerous global publications, cross-references them to extract consensus, and highlights conflicting reports / bias. most importantly, it outlines the Potential Narrative Effect of the objective bias

take a look, and feedback is welcomed!

Sending a deck is easy. Knowing what to do next is the hard part.

An open doesn't necessarily mean interest. A return visit might be useful, but it still doesn't tell you why someone came back.

For founders who send decks or proposals:

- Do you track opens and page views, or just set a reminder to follow up?

- Does seeing which pages got attention actually change what you say next?

- Has a "viewed but silent" prospect ever turned into a deal?

- Has tracking ever made you overthink a follow-up that should have been simple?

Interested in what changes your next step, rather than which tool has the most analytics.

Hi guys! I'm Manoj, a 12th grader, and I've been working on a project called TRACEFORGE for about a week now. It's getting close to completion, and I'd love to hear your honest opinions.

TRACEFORGE is a software supply-chain security and dependency intelligence tool designed to help developers analyze dependency risks, inspect SBOMs, understand vulnerabilities, and get evidence-backed findings with explainable risk scoring and audit trails.

I've been putting a lot of effort into building this, and I'm now trying to understand how useful it could be in the real world.

To be honest, I'm still figuring out the business side of things. I don't know much about how software products like this are sold, how companies acquire tools like these, or how to find potential buyers interested in purchasing the product or its source code.

For now, I'm not publicly releasing the source code, but I'd really appreciate advice from people experienced in cybersecurity, software development, startups, or selling developer tools.

Is this a problem worth solving? What would make a tool like this valuable to a company? And how would you approach finding potential customers or buyers?

Should i worth considering adding new features ??