4 ms·
Thank you for writing this. You've perfectly articulated the underlying anxiety that many of us in the industry feel but often hesitate to say out loud. It's e
by PaulShin 1y ago
Thank you for writing this. You've perfectly articulated the underlying anxiety that many of us in the industry feel but often hesitate to say out loud.
It's easy to feel alienated when the public narrative is dominated by either blind techno-optimism or a cynical acceptance of value extraction.
But I believe there's a third path. The problem isn't AI itself, but the goal we assign to it. At my company (Markhub), we have one core principle for our AI development: The purpose of AI is not to replace the human, but to replace the boring, soul-crushing parts of the human's job, to free them up for the work that actually requires a conscience.
We often talk about "Architectural Thinking" (the creative, strategic work you enjoy) versus "Translational Thinking" (writing boilerplate, summarizing meeting notes, chasing follow-ups). We are building our AI teammate, MAKi, to automate the latter, so our team can spend more time on the former.
So, to answer your question, "What is one to do?": We build. But we build differently.
We build tools that are not designed to maximize engagement at the cost of well-being. We build AI that is designed to augment, not to replace. We build companies that see users as partners to be served, not resources to be extracted.
We can't change the entire industry overnight, but we can create pockets of the future we actually want to live in. For me, that starts with building a workspace where technology genuinely serves the human, not the other way around.
You're not struggling for having a conscience. You are the immune system this industry desperately needs. Thanks again for starting this important conversation.
- jjice 1y ago> The purpose of AI is not to replace the human, but to replace the boring, soul-crushing parts of the human's job, to free them up for the work that actually requires a conscience. I was so resistant to LLM assisted development until recently because I didn't want to automate away something I love so much (a passion I've held my entire life). But then I realized I could use it as advanced boilerplate generation and I've loved it. No more writing another CRUD endpoint with a slight modification over the one I'm basing it on - give me five minutes of prompting and let me get back to one of the interesting problems. I appreciate how you phrased that.