Less stressful because of workload, more stressful because the future looks dramatically less secure.
Work keeps coming in, so that's good and great but realistically speaking... if your in the web-development space working on a platform or site that's handling like ~20-30 million visitors/day your kind of not needed to some extent.
I think once the costs with AI settle-down and it's well known what the spend rate looks like we are going to see growing adoption of tools like https://paperclip.ing/ where you have a significantly smaller engineering team just overseeing technical projects and helping to draft requirements to feed into some automation pipeline for code generation and deployment.
Basically how work is today, just write a prompt, wait for it do most of the work, test, write another prompt, test, tell it to push and open the PR, attach screenshots to PR, wait for automated review, tell it to advance the ticket, wait for someone to approve, the merge-bot then takes it away and gets it into the UAT environment.
It's "awesome" in the sense I can work on like 3-4 big major tickets at a time with a high degree of confidence, but it's scary because like... it's right there... only thing missing is a smarter more technically focused business team (thankfully they kinda suck at using AI and fumble around with it, was often referred to as magic in some circles prior to AI when we built things quickly but now they literally say it's insane how quickly we churn out updates because we mostly just keep asking them for more).
We are in a new frontier of software development, and that's kinda scary for me because I entered when these processes today were being trialed and used to maturely develop applications... now I am blazing the trail of what the new SDLC looks like.
Less stressful because of workload, more stressful because the future looks dramatically less secure.
Work keeps coming in, so that's good and great but realistically speaking... if your in the web-development space working on a platform or site that's handling like ~20-30 million visitors/day your kind of not needed to some extent.
I think once the costs with AI settle-down and it's well known what the spend rate looks like we are going to see growing adoption of tools like https://paperclip.ing/ where you have a significantly smaller engineering team just overseeing technical projects and helping to draft requirements to feed into some automation pipeline for code generation and deployment.
Basically how work is today, just write a prompt, wait for it do most of the work, test, write another prompt, test, tell it to push and open the PR, attach screenshots to PR, wait for automated review, tell it to advance the ticket, wait for someone to approve, the merge-bot then takes it away and gets it into the UAT environment.
It's "awesome" in the sense I can work on like 3-4 big major tickets at a time with a high degree of confidence, but it's scary because like... it's right there... only thing missing is a smarter more technically focused business team (thankfully they kinda suck at using AI and fumble around with it, was often referred to as magic in some circles prior to AI when we built things quickly but now they literally say it's insane how quickly we churn out updates because we mostly just keep asking them for more).
We are in a new frontier of software development, and that's kinda scary for me because I entered when these processes today were being trialed and used to maturely develop applications... now I am blazing the trail of what the new SDLC looks like.