i have 20+ projects in total across various stacks, as i was freelancing, people gave me all kinds of work, from design to serverless inference

i don't know how recruiters will react to freelance. never done a job except internship

i haven’t applied anywhere yet — i want the resume to be solid first

should I apply for 0 Year of experience

i have one major project still to add in core ml: Govt freelance. i still need to write a case study

been running this on my codebase for a few weeks. readability goes up every time it runs. here's the whole thing

agent's default is:

• patches instead of redesigns
• keeps legacy code “for compatibility” that nothing calls
• duplicates codes across files
• gets lazy with names

you have to override them every time.

when to run it?

right after you fix a bug or ship a feature, while the agent still has full context. do it consistently and the debt never compounds

---
name: zero-tech-debt
description: Rework a change as if the intended UX and architecture existed from day one, deleting compatibility cruft and accidental complexity.
user-invocable: true
---

# Zero Tech Debt

Rework the change from the intended end state, not from the historical path that produced the current patch.

## Steps

1. State the intended end state in one or two sentences.

2. Search for real callers before preserving compatibility.
   If a mode, prop, wrapper, route alias, or fallback has no current caller, delete it.

3. Reshape around the final product surface.
   Prefer one clear component or flow over mode flags. Split only when it creates an obvious boundary such as state, layout, controls, or domain commands.

4. Move shared rules to one place.
   Feature flags, permissions, route gating, URL state, and command naming should not be duplicated across pages or hidden in view components.

5. Verify the intended flow.
   Test the new behavior and any deleted assumptions that affect navigation, permissions, or persisted state.

## Rules

- Optimize for the code that should exist, not the smallest diff from the old shape.
- Delete dead compatibility paths instead of making them better.
- Do not invent a generic framework for one feature.
- Keep the refactor scoped to what makes the final shape coherent.
- Prefer names that describe product intent over implementation history.

install:

npx skills add jnsahaj/skills

full breakdown with more context: https://reetlab.substack.com/p/the-zero-tech-debt-skill

Make your LinkedIn profile pop in seconds.

Upload your photo, pick a bold frame (CHILL GUY, WAGMI, COMEBACK, LOOK MAXING & more), tweak, download, done.

Stand out in the feed. Try it now 👉 https://linkedinframe.com

inspired from inframe.stephcraft.net (it was annoying, i really can't download the image)

Chinese AI companies are releasing their models as open source back onto the public internet, completing the cycle. in how many days it will happen ?

so i gotta share this because i almost lost my mind last week

im running a few solo saas projects on the side. nothing massive but its my whole income right now. had everything sitting on this OVH vps and i thought it was chill. then 4 days in they just terminate the entire instance. gone. all my configs, databases, env files, everything

i had backups but restoring was a nightmare and i spent the whole weekend sweating bullets trying to get back online. customers were emailing me like "is the site down" and i was dying inside. never again

that whole disaster made me realize i was treating my infra like a side project when its literally how i eat. open ports everywhere, ssh sitting on port 22, password auth still enabled. basically had a neon sign saying please hack me

so i rebuilt from scratch but went full zero trust this time. nothing touches the public internet unless there is literally no other option

tailscale runs the whole private network now. all my devices talk through the mesh. laptop, phone, vps, all connected privately. ssh is completely hidden from the public internet

moved ssh to some random high port and disabled passwords entirely. keys only. i dont even want to imagine how many brute force bots were hammering port 22 before. probably thousands a day easy

fail2ban just watches in the background and auto bans anything sketchy. its lowkey therapeutic checking the ban logs sometimes ngl

set up honeypots too. fake ports that catch scanners and log what theyre trying to hit. its honestly creepy how fast bots find a fresh server. like literally minutes. the internet is just bots scanning constantly its wild

for public web stuff im using cloudflare tunnel. users can access the app fine but nobody knows where the actual server lives. zero direct traffic hits my box

the mental difference is huge. i used to wake up and check server stats before i even got coffee. now i forget about it for days. so much more brain space to actually build instead of playing sysadmin

you could use zerotier instead of tailscale or ngrok instead of cloudflare tunnel. but this particular combo just works seamlessly and its basically free besides the vps cost. hits different when youre solo and dont have a devops team

if youre running your own infra as a solo founder please do this audit. even if you think youre fine. pretend your server dies tonight and rebuild it paranoid

wrote the full breakdown with exact configs and lessons. founder here

https://reetlab.substack.com/p/the-solo-devs-zero-trust-vps-stack