person yeah that's super interesting I I think like that might be something that's happening broadly you know um it really ends up being two different roles you need I mean it actually maps to how Engineers sort of self assigned today in that either you're uh you know front end or back end and then back end ends up being about actually infrastructure and then front end is so much more actually being a PM you're sort of um almost being like an ethnographer going into the Obscure underserved parts of the pie of GDP and you're trying to extract out like this is what those people in that GDP Pi actually want and then I'm gonna you know turn that into code and then actually evals are the most important part of that when I was running triple bite this was actually one of the things we noticed it was almost as important as a technical assessment of Engineers when trying to figure out who's a good match for a specific company is there's a certain threshold of techn ability you need but beyond that it was do you actually want to talk to users or not like some Engineers are actually just very a lot more motivated by working on things where they know who the users are and they get to like communicate with them and they get live feedback and they can iterate um and essentially being a product engineer and other Engineers really don't want to do that at all like they find it annoying having to deal with users and they want to just like work on like hard technical problems and refactor back end engineer yeah that's that's what we call a back end engineer yeah sure and that's only a theme that came up in these survey responses right this idea of sort of the llms are maybe going to push people to choose do the actual writing of the code may become less important it's about are you really do you have taste and you want to to solve product problems or are you an architect and you want to solve systems problems oh and interestingly I guess um