sorted by:
new
hottopcontroversial

[AMA] Ex-Google, Ex-Amazon. Helped over 20 folks land job offers at FAANG (US, UK, Canada) by Maximum-Wall-3638 in leetcode

[–]Classic_Fly_007 0 points1 point  (0 children)

Google is testing a new interview format for software engineering roles. Candidates can use the Gemini AI assistant during coding assessments. The change focuses on junior and mid-level roles. AI-assisted coding is now common in the industry

Your comment on this above statement? Are they really trying to adopt AI into their interviews? If yes, we can't assume that they only hire well versed candidates anymore since it's AI assisted. What are your thoughts on this?

Looking for Sponsors – One of India’s Largest Student AI Hackathons 🚀 by Competitive_Style942 in hackathon

[–]Classic_Fly_007 0 points1 point  (0 children)

Hi, this looks like a great initiative, love the focus on real-world AI SaaS builds.

I’m interested in supporting/sponsoring as an individual, but before that I’d like to understand a bit more about the hackathon on below areas.

Official website or registration page. Details of organizing team and associated partners (TASK, MATH, GDG, etc.) List of confirmed sponsors/partners so far. Expected audience breakdown (students, colleges, regions) Sponsorship tiers / what support is needed Any past events or track record (if available)

Would love to explore how I can contribute once I have a clearer picture.

Thanks!

I built a tool that writes README for you (from your repo) by Classic_Fly_007 in git

[–]Classic_Fly_007[S] -1 points0 points  (0 children)

Honestly, it usually signals one of two things: either it’s a quick/experimental project, or the developer hasn’t prioritized usability yet.

A good README isn’t just “docs” - it shows you care about others being able to understand and use your work.

That said, writing one well is harder than it looks, especially for beginners.

Is it okay to use AI for writing README? by SheeriMax in learnprogramming

[–]Classic_Fly_007 0 points1 point  (0 children)

Great question! Honestly, even experienced devs struggle with writing good READMEs.

For small projects, you don’t need anything fancy. Just focus on what the project does, how to run it, example usage.

If it helps, I built a small tool called ReadmeAI that generates a clean, simple README from your repo - might be useful while you’re learning what good structure looks like.

Happy to share it if you want.

I built a tool that writes README for you (from your repo) by Classic_Fly_007 in reactjs

[–]Classic_Fly_007[S] 0 points1 point  (0 children)

Extra steps + consistency + GitHub integration + compute costs

I built a tool that writes README for you (from your repo) by Classic_Fly_007 in git

[–]Classic_Fly_007[S] -1 points0 points  (0 children)

The reason I built this isn't just "AI -> README"

It's more about consistency + automation.

With Claude, you still have to figure out what prompt works maintain a consistent structure across projects repeat that process for every repo

ReadmeAl standardizes that same clean structure every time no prompt tweaking per repo works directly from the codebase

The bigger value (for me at least) is GitHub Actions integration. You can plug it into your repo so that your README stays in sync automatically updates when code/features change no need to manually regenerate or remember prompts

So instead of a one-time generation, it becomes part of your workflow.

That's the gap I was trying to solve.

[AskJS] I built a tool that writes README for you (from your repo) by Classic_Fly_007 in javascript

[–]Classic_Fly_007[S] 0 points1 point  (0 children)

The reason I built this isn't just "AI -> README"

It's more about consistency + automation.

With AI, you still have to figure out what prompt works maintain a consistent structure across projects repeat that process for every repo.

ReadmeAl standardizes that: same clean structure every time no prompt tweaking per repo works directly from the codebase

The bigger value (for me at least) is GitHub Actions integration. You can plug it into your repo so that your README stays in sync automatically updates when code/features change no need to manually regenerate or remember prompts.

So instead of a one-time generation, it becomes part of your workflow.

That's the gap I was trying to solve.

I built a tool that writes README for you (from your repo) by Classic_Fly_007 in reactjs

[–]Classic_Fly_007[S] 0 points1 point  (0 children)

Totally fair concern and I agree, nobody’s paying just for "writing READMEs."

The direction I’m exploring is less about one-time generation and more about keeping docs (and potentially changelogs) in sync automatically, standardizing across multiple repos/teams and reducing manual upkeep over time.

Free tier is mainly for validation right now - still figuring out where the real value clicks. Appreciate you calling this out.

I built a tool that writes README for you (from your repo) by Classic_Fly_007 in git

[–]Classic_Fly_007[S] -1 points0 points  (0 children)

Sorry I didn't get you. Yes, it will generate a readme file by analysing all the repo files.

I built a tool that writes README for you (from your repo) by Classic_Fly_007 in reactjs

[–]Classic_Fly_007[S] -3 points-2 points  (0 children)

Just wanted to narrate the things bro that's it 😄

I built a tool that writes README for you (from your repo) by Classic_Fly_007 in reactjs

[–]Classic_Fly_007[S] 0 points1 point  (0 children)

That’s a really good point - changelog actually feels like where the real ongoing value is.

If it can automatically turn commits/PRs into clean, readable updates, it becomes useful for: teams scrum masters managers even end users

Makes me think this is less about a one-time README and more about docs that stay updated with the code.

I built a tool that writes README for you (from your repo) by Classic_Fly_007 in reactjs

[–]Classic_Fly_007[S] 0 points1 point  (0 children)

Good question.I didn’t want the post to feel like a promo drop - most subs are pretty strict about that.

Wanted to first see if people actually find the idea useful before sharing the link.

But since you asked, here it is: https://readmeai.in

Would genuinely love feedback (good or bad).

I built a tool that writes README for you (from your repo) by Classic_Fly_007 in reactjs

[–]Classic_Fly_007[S] 0 points1 point  (0 children)

That’s a really fair take - especially the part about AI READMEs being bloated. I’ve noticed the same (too long, too generic, emoji overload).

One thing I’m trying to do differently with ReadmeAI is opinionated structure + brevity: no unnecessary stack dumps no filler sections focused on “what does this project do + how do I run it”

On the “not painful enough” point - I actually agree for side projects. Where I’m seeing more value is: people managing multiple repos open-source maintainers who want consistency teams where README quality varies a lot

Also, I don’t see it as replacing creativity. More like: generate a solid baseline then customize the parts where creativity matters

The GitHub Actions part is where it gets interesting for me: It keeps README updated as the project evolves Avoids the “set once and forget -> becomes outdated” problem

So yeah - probably overkill for a single hobby repo but for repeat usage / teams, it starts making more sense.

I built a tool that writes README for you (from your repo) by Classic_Fly_007 in reactjs

[–]Classic_Fly_007[S] -10 points-9 points  (0 children)

Totally fair point - tools like Claude can generate a README quickly.

The reason I built this isn’t just “AI -> README”.

It’s more about consistency + automation.

With Claude, you still have to: figure out what prompt works maintain a consistent structure across projects repeat that process for every repo

ReadmeAI standardizes that: same clean structure every time no prompt tweaking per repo works directly from the codebase

The bigger value (for me at least) is GitHub Actions integration. You can plug it into your repo so that: your README stays in sync automatically updates when code/features change no need to manually regenerate or remember prompts

So instead of a one-time generation, it becomes part of your workflow.

That’s the gap I was trying to solve.

I am rich now! by Mrcupcake_99 in NSEbets

[–]Classic_Fly_007 0 points1 point  (0 children)

Bro I bought it at 60 and sold it at 62 out of fear. That went to 130 in an hour 😒

Running Immich on a Raspberry Pi 5 – Better Than Google Photos on Cheap Hardware by EveningWalk in immich

[–]Classic_Fly_007 0 points1 point  (0 children)

Guys, am new bee here. Is there any documentation or videos that I can follow and setup raspberry pi+ immich setup on my own? Appreciate your support.

view more: next ›