I think AI made development less async.
Earlier you could receive a task and code it over night, ask questions next day, then re-iterate.

But now coding part is done faster, so you need to be more in touch with the team.

Also your teammates are iterating faster, feedback loops are shorter, you need to talk and align more often.

Now when your code can be written by AI, you are not expected to deliver code. It has always been not about code. You had to talk, align and check status of the job on CI, press buttons, etc.

If your work was only about writing the code, pushing it and waiting for review - then you will lose your job very soon. If you also handled and cared about the meta tasks, that are part of the process, then you will still be wanted.

I think this is going to become my main work playlist for the next couple of months.
It's fred again & who? google it

https://youtu.be/gfF8jzBVWvM

You may be seeing this new https://github.com/chenglou/pretext thing everywhere recently.
First I didn't get the point, but here are some examples showcasing it very well, I think:
https://fixupx.com/solarise_webdev/status/2038330971397697895
https://fixupx.com/ukint_vs/status/2038236738477531636

UI is dead?
Really interesting talk, especially the first half

in case you are looking for the next playlist to vibe to while vibe coding
https://youtu.be/0sZF6YzhrRU