i've built a profitable full stack SaaS application, from scratch, by myself, that requires 0 maintenence

and you dont think i have the skills required to hire me?

🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡

0 maintenance how? 🤔

Everything needs updating/changing at some point

@MammaNeedHummus you can automate that. But yes I don't believe zero maintenance is possible. Extremely low maintenance yes but zero nope.

If you ain't getting the job, you ain't getting the job.

You can make the company a million dollars profit on day 1 but if they have decided not to hire you, then it's your bad luck.

The argument would be more convincing if it was profitable enough for you to not need a job anymore...

@hjk101 automate updates?
If a library changes its methods and your code is using them, won't that always require manual code changes?

I get bug fixes and minor ones but what about major?

@MammaNeedHummus yeah security updates. At some time an API may need upgrading and then it does need action. Our when tests fail on the security update. Hence the zero maintenance being impossible. With AI or rolls like go fix we might get even closer but still.

@MammaNeedHummus not on my stack 😎

ok ok you got me, i did upgrade the backend from .NET 5 to 6 back in march

and added a pipeline deploy

otherwise, haven't done anything

@horus yeah but i feel like this almost has a reverse psychology effect like the corporates are like "oh this guy is not desperate enough to work for us, better not try and hire him anyway"

@fullstackclown and maybe you're exactly right. They might be afraid to leave out of the sudden.

@horus I mean I get it from their perspective, but for me it totally sucks!

Maybe open source it and send the repo before interview so they have an idea what you're made of

@fullstackclown Mergify and dependabot automate that. Buuuuut sometimes there's breaking changes.

@gagan-suie i wouldn't trust dependabot with my life, IMO exact definition of bad AI:

-> finds any package which isn't absolutely the latest version

-> automatically upgrades that package to latest version, doesn't check for possible conflicts

-> force commit to production build

-> production down

sounds like an automated intern / junior to me

@fullstackclown I have it creating PR and automate merge to main via Mergify (but prevent it from deploying to production). Once a version is ready for production, merge from main to dev and check everything. Then merge dev into main and make a production release.

GitHub actions allows you to check if dependabot made a PR, and prevent it from running the deployment script.