Noticing an interesting version of gell-man amnesia where people use AI for their job and see all the various things they have to do in the “last mile”, but then look at someone else’s job and think that AI will eliminate it immediately.
We all have a much deeper appreciation for the nuances and complexities of the work that we do every day. We run into issues about accessing data, we know how much context is needed to get AI models to work the way we need, we have to review the output of the AI to make sure it’s accurate, and then we have to incorporate that work into some broader business process. We see all those steps deeply for the work that we do.
Then, a moment later, we see AI do something in a foreign space and think that it can go automate that entire function. We tend to dramatically underestimate the work that goes into making the AI work just as effectively in those jobs.
This is reason to be skeptical about many of the theories of job loss. It’s coming from the lens of being able to automate individual tasks with AI, without understanding all the work that goes into doing the job fully.
@sleighzy Just spent 15min trying to figure out why my feature flag wasn't working in production... turns out it was a typo in the name.
Its always the simple things mannnnn.
hate when engineers complain about “the requirements not being clear”
your responsibility includes figuring out what the requirements should be - the fact that some parts are unclear is information
no good product has ever been built by outsourcing that process to someone else
“The most egregious thing that holds back people's understanding of Git is the concept that "if you don't use git on the command line then you're not a real developer" and this idea it needs to die.” 💯 a good git client just makes life so much easier 😎 - https://t.co/Z26Rv2OroT