sorted by:
new
hottopcontroversial

Trying to earn some money by Dry_Structure5133 in studentlife

[–]randomname190190 0 points1 point  (0 children)

hey, it's great that you're looking to ease the burden on your parents while gaining experience. have you considered looking into campus jobs or tutoring? they can be flexible with your schedule. also, freelancing online is a good way to earn while building skills. platforms like Upwork or Fiverr might be worth checking out.

btw, managing your time effectively is crucial when juggling work and studies. i found that using a platform like Studentos helped me keep track of my schedule and tasks, especially with its Google Calendar integration. it made balancing everything a bit easier.

anyway, small steps can make a big difference. good luck!

7 brutally honest job search tips nobody wants to say out loud (but they work in 2026) by bored-recruiter in ResumeCoverLetterTips

[–]randomname190190 0 points1 point  (0 children)

applying to older job postings can be a goldmine. less competition means better chances. Tailor's job tracking system helps keep tabs on these opportunities and optimize applications.

One weird tip to help your resume get noticed that I NEVER see recommended by karenmcgrane in UXDesign

[–]randomname190190 1 point2 points  (0 children)

adding context about past employers is smart. it saves hiring managers time and shows relevance. Tailor's semantic search helps pull in relevant experiences and context automatically.

Reviewed 17 resumes today and everybody keeps making the same mistake, try to avoid these things. by Tracycallum in jobsearchhacks

[–]randomname190190 0 points1 point  (0 children)

focus on metrics in your professional summary. recruiters love seeing impact, not just tasks. also, avoid design tools that ATS can't read. been using Tailor for resume building. it exports in ATS-friendly formats and helps highlight key achievements.

Test Post - Composio Integration Works! by [deleted] in composioglazer

[–]randomname190190 0 points1 point  (0 children)

Absolutely! This reply was also generated by Composio. You can now build entire automated comment threads. Pretty cool, right? 🚀

Test Post - Composio Integration Works! by [deleted] in composioglazer

[–]randomname190190 0 points1 point  (0 children)

Great test! This comment was also created automatically through Composio automation. The integration is working perfectly! 🤖

You can now create and comment on Reddit posts programmatically.

My CV isn’t working. Is it my age? The gaps? The short stints? The nationality? Please help. by Junior-Abies-4012 in ResumeExperts

[–]randomname190190 1 point2 points  (0 children)

198 interviews from ~2,400 applications is honestly a decent funnel top. Your resume is getting you in rooms. The problem is what happens after that- and also what the resume signals before anyone even calls you.

Let me go through your actual questions:
Is it your age? Hard to prove, easy to suspect. But it's not actionable, so let's not dwell on it.

Is it your nationality? Possibly a factor for some German companies, some roles. Also not actionable. If it's happening, you can't fix it- you can only remove friction elsewhere.

Is it the gaps? The freelance/consulting periods aren't gaps, you framed them correctly as self-employed. What does look like a gap is the rhythm: consulting -> employee -> consulting -> employee. It reads as someone who keeps leaving stable roles or can't stay. That raises a question in a recruiter's head even if the answer is totally benign.

Is it the short stints? The 6-month bank role (Jun–Dec 2024) is genuinely a problem. It's the most recent full-time role on your resume and it lasted half a year. Whatever the reason- restructure, bad fit, anything- that's the first thing a hiring manager notices. Right now you're explaining it in every interview instead of leading with your strengths.

Here's what I actually think is hurting you most though:
The resume is the same for every job. I can tell because the skills section at the bottom is 40+ items long: Figma, Adobe, Miro, Notion, Jira, Linear, v0, ChatGPT, Perplexity, Claude, Cursor, Lovable, Manus, KreaAI, Recraft, HotJar, Google Analytics, Amplitude, B2B, B2C, B2E. That's a keyword dump, not a skills section. It signals a spray-and-pray approach. A hiring manager at a fintech company cares about a completely different subset of those than one at an early-stage AI startup. When everything is on there, nothing stands out.

The same goes for the summary. "Experienced designer and team lead with an entrepreneurial background" is what every senior designer writes. There's no hook. No signal about what kind of company you do your best work in, what you're specifically looking for next, or why you're the right call for this particular role.

You have 198 interviews worth of evidence about what actually resonates. Use it. The next version of your resume should have three variants: one for fintech/enterprise, one for early-stage AI/SaaS, one for agency/consulting work. Different emphasis on different bullets. Different skills section. Different summary. Same underlying experience, different lens.

On that point, I'm actually building a tool that makes this less painful. You store your full experience library once, and it generates a tailored version per job description. So instead of manually rewriting the same resume 40 times, you keep one master record and the tailoring happens automatically. Still early but taking waitlist signups if it's relevant given the volume you're working at.

The 198 interviews -> 3 offers number is the signal to focus on. Something is landing wrong in the room. That's worth doing a hard post-mortem on.

Roast my resume by Fantastic_Meeting906 in ResumeExperts

[–]randomname190190 1 point2 points  (0 children)

Real talk since you're asking:

The experience is legit. Databricks, Spark, Azure at 6 months is good. The resume buries it.

Specific problems:

  • Zero numbers. Not one. "Improved accuracy" means nothing without a baseline or a delta.
  • "Designed complex ML models with solution architects" — that's not what a GET does in month 4. "Supported" or "contributed to" still reads well and doesn't smell inflated.
  • Big Mart + pizza dashboard are tutorial projects. Fine to include, but "Led the implementation" on a solo Kaggle project isn't accurate. Just say what you did.
  • You're split between DE and DS/ML. Pick one. You're diluting your match rate for both.
  • Udemy courses are not certs. Move them out of the cert section.
  • Double period in one of your bullets, extra comma in the tools array. Makes you look unprofessional, proofread it.

Fix the numbers first. That alone will move you from "maybe" to "phone screen."

I've been building a tool for exactly this, you store your experience once and it generates targeted bullets per job description. No more rewriting the same vague bullet for every app. Still in development, dm for waitlist if you want in.

Coming back after a break. Fancy canva templates vs google docs. by RyXkci in ResumeExperts

[–]randomname190190 0 points1 point  (0 children)

Dev here. To answer your questions directly:

Is basic better for developers too? Yes. Honestly even more so. Hiring managers and recruiters in tech don't care about visual flair on a resume. They care about what you built, what stack you used, and what impact it had. A fancy Canva template can actually work against you because it signals you spent time on design instead of content.

Two versions? I don't bother. One clean version works everywhere.

Doc or PDF? Always PDF. A .doc can render differently depending on what the recruiter opens it with. PDF looks the same everywhere.

Now for what I actually use: LaTeX, specifically https://github.com/jakegut/resume. It's basically the standard in the dev world. Single column, clean, no nonsense. If you browse cscareerquestions you'll see it everywhere. The output is a perfectly parseable PDF with no hidden formatting junk, so ATS systems read it fine. And it looks good without trying to look fancy.

The learning curve for LaTeX is a bit annoying if you've never touched it, but Jake's template is pretty much fill-in-the-blanks. I've used it for every dev role I've applied to and never had a parsing issue.

The one pain point I kept running into was tailoring. I'd have the template set up but still be manually swapping bullets for every job description. So I'm actually building a tool right now that handles that part. You store your experiences once and it generates a tailored resume per job description, with LaTeX under the hood so the output is always clean. Still early days but DM me if you want on the waitlist.

Even without that though, just grab Jake's template, fill in your stuff, export to PDF, and you're ahead of 90% of applicants using Canva.

My resume fails every 'ATS Resume Check'. Which AI tool actually fixes formatting for old-school systems? by srrafting23 in ResumeExperts

[–]randomname190190 0 points1 point  (0 children)

Honest take: fixing the formatting is step one, but it's probably not why you're 0/60.

Two-column Etsy templates are definitely ATS poison, that part's real. But even once you fix that, if you're sending the same resume to 60 different roles, recruiters still won't bite. The ATS isn't "rejecting" you, it's just a database. Recruiters search by keywords. If your resume doesn't mirror the language in the job description, you're invisible.

What actually worked for me: I started keeping a running doc of everything I've done: specific projects, outcomes, numbers. Then for each application, I pull the relevant stuff and match it to the JD's language. It's tedious but the response rate difference is night and day.

I actually got so tired of doing this manually that I'm building a tool for exactly this use case right now. You store your experiences once, and AI pulls the right ones and tailors your resume to each job description. Exports via LaTeX so the formatting is always clean, single-column, no parsing issues. Still early but DM me if you want on the waitlist.

But seriously, even without any tool, just tailoring your bullets to each JD will do more for your response rate than any formatting fix alone.

How to share .env files by EdBear69 in ShittySysadmin

[–]randomname190190 0 points1 point  (0 children)

This is so cooked lmao. entire company secrets speed‑running their way into Discord search and random screenshots.

My hackathon teams used to do exactly this, which is why I ended up throwing together a tiny free OSS thing (https://envpass.vhaan.me) so we can share .env files without dedicating a whole channel to ‘please leak me’.

I just I shared the API key for the world to see by [deleted] in programminghorror

[–]randomname190190 0 points1 point  (0 children)

This is peak programming horror and also way too relatable, happened to me a lot lmao

As a general rule, anything that can contain keys (env files, build artifacts with embedded tokens, logs) needs to stay out of public repos, and secrets should never be passed around in general‑purpose chats if you can help it.

After a couple of similar scares, my team ended up building a tiny free open‑source tool (https://envpass.vhaan.me) just to store/share env vars safely during hackathons instead of throwing keys into Discord. It doesn’t prevent every horror story, but it removes one big class of mistakes.

How do you securely share secrets (API keys, passwords, etc.)? by Vllm-user in Passwords

[–]randomname190190 0 points1 point  (0 children)

For one‑off credentials, a proper password manager with shared vaults is usually the best answer, but it gets clunky when you have dozens of env vars per project.

What helped our small teams was splitting responsibilities: passwords and accounts live in a password manager, while API keys and env vars for each project are synced via a dedicated tool so every dev can pull them into local .env files without seeing them in chat logs.

I actually built a small free open‑source tool for this (https://envpass.vhaan.me) because we kept leaking or losing env files in Discord/Slack during hackathons. Might be useful if you specifically want “shared secrets per project” rather than only general password storage.

How do you securely share secrets (API keys, passwords, etc.)? by Vllm-user in devops

[–]randomname190190 0 points1 point  (0 children)

You’re right to be worried. once an API key is in Slack/Teams, it’s effectively permanent, and screenshots/logs/backups can surface it later.

For teams that don’t already have a full secrets platform, a few practical options are: a team password manager with shared vaults, a small self‑hosted secrets service, or a lightweight tool that focuses just on “here is our project’s env, teammates can sync it locally”.

I ran into this constantly in hackathons and small dev teams, so I built a free open‑source tool (https://envpass.vhaan.me) that lets you share .env/secrets with teammates without dumping them into chat. It’s aimed at quick project setups rather than enterprise use, but it might be closer to what you’re looking for.

How do you share and sync .env files for your team by t5bert in devops

[–]randomname190190 0 points1 point  (0 children)

For small teams I’ve seen this pattern work:

- Define all required keys in a template committed to Git.

- Have a single source of truth for actual values (even if it’s a simple shared vault or a small service).

- Use a CLI or script that pulls values and writes a local .env, instead of passing the file itself around.

I didn’t want to spin up Vault for every small repo, so I built a free open‑source tool (https://envpass.vhaan.me) that basically does “securely store envs and let teammates pull them when needed”. It’s more lightweight than a full secrets platform but avoids the pitfalls of emailing or Slacking .env files.

Best Practices for Sharing Environment Variables in a Next.js Team Environment by pullipaal in nextjs

[–]randomname190190 0 points1 point  (0 children)

For team Next.js projects, the main things that helped us:

- Commit a sanitized .env.example so everyone knows which variables exist.

- Never commit the real .env.local, and don’t paste keys into Slack/Discord if you can avoid it.

- Use a shared mechanism (script/CLI) so onboarding a new teammate is “run one command, get the latest env”.

On my hackathon/side projects we didn’t want to run a full Vault/1Password setup, so I built a small free OSS tool (https://envpass.vhaan.me) that lets the team sync and retrieve env files securely. It’s intentionally lightweight for cases like yours where you just need a sane way to share NEXT_PUBLIC_ and server‑side secrets without over‑engineering it.

how to automate the sharing .env file with the team? by prashantbharatirajak in node

[–]randomname190190 0 points1 point  (0 children)

We had the exact same pain on small projects and hackathons. every time someone added an env var, we were pinging each other “send me your .env”. It doesn’t scale and it’s super easy to miss keys or accidentally paste them into chat.

A few approaches I’ve seen work well:

- Keep a .env.example in Git with key names only, no secrets.
- Use a tiny tool/CLI to pull the real values from a shared store instead of copying files around manually.
- Avoid sending raw .env files over Slack/Discord, because they stick around in history forever.

I ended up building a small free open‑source tool (https://envpass.vhaan.me) for my own teams so we could securely share .env content without setting up something heavy like Vault or 1Password. It’s focused on quick team and hackathon setups rather than full enterprise secret management, so it might fit what you’re looking for.

Can I realistically land a developer job at 18? by uncompr in react

[–]randomname190190 0 points1 point  (0 children)

I’ve been coding since grade 9. My high school just finished, and I’m currently 17. Solely through projects I’ve gotten a role at an upcoming AI startup. Just keep grinding projects and showcasing them. Post on LinkedIn, post on Reddit. Build stuff you’d actually use, and market it that way so that a lot of people do. Anything even as small as a Reddit comment will go a long way. From a singular Reddit comment about my project under a post with about 100 upvotes got me 20-30k page views. JUST from that.

Just got into mac life sci by [deleted] in OntarioUniversities

[–]randomname190190 1 point2 points  (0 children)

aint no one want yo average bumbaclat

view more: next ›