> I like knowing how the code works, what the data structures are, what APIs are being used, and yes even typing the code into the editor. I'd say it probably

> I like knowing how the code works, what the data structures are, what APIs are being used, and yes even typing the code into the editor. I'd say it probably depends on the kind of work you do - if the low level details are exciting then that's totally understandable. But if you're dealing with more rote CRUD work or soul sucking enterprise bullshit, then probably less so and the low level details are obstacles to getting things done, alongside sometimes unreasonable workloads. I'm reminded of: https://www.stilldrinking.org/programming-sucks https://www.stilldrinking.org/programming-sucks > Every programmer starts out writing some perfect little snowflake like this. Then they’re told on Friday they need to have six hundred snowflakes written by Tuesday, so they cheat a bit here and there and maybe copy a few snowflakes and try to stick them together or they have to ask a coworker to work on one who melts it and then all the programmers’ snowflakes get dumped together in some inscrutable shape and somebody leans a Picasso on it because nobody wants to see the cat urine soaking into all your broken snowflakes melting in the light of day. Next week, everybody shovels more snow on it to keep the Picasso from falling over. That said, AI will probably saturate most CRUD work first, which doesn't make for great job prospects.