While I certainly relate to some of your points, and I'm not an AI maximalist by any means, a few thoughts: > You join a meeting with a coworker. Your coworker has enabled an AI tool to automatically take notes and summarize the meeting. They do not ask for consent to turn it on. The tool mischaracterizes what you discuss. Asking for consent to what is more or less meeting transcription (already enabled, presumably)…
Do I belong in tech anymore?
81–90 of 147 posts
Re: Do I belong in tech anymore?
#82I think a lot of people relate with this but kind of sit with this silently for reasons the author mentioned: “ Would initiating these discussions result in interpersonal stress? Should I just let things slide? Would I become known as a “difficult” coworker for pushing back on AI use? Does any of it really matter? Does anyone really care? “
Re: Do I belong in tech anymore?
#83Earlier quoted context omitted.
My response is probably controversial. But I genuinely think it’s generally helpful advice. Ofc I don’t have any other information than the comment about this person.
You literally said they should do something.
Re: Do I belong in tech anymore?
#84Earlier quoted context omitted.
[flagged]
Huh, weird that you can't reply. I'm tailoring my resume to individual postings a good portion of the time. My "default" resume is by ChatGPT; it's essentially my human-written resume, jazzed up a bit for ATS-friendliness. There are no hallucinations in it, and I feel it accurately represents my experience.
Re: Do I belong in tech anymore?
#85Earlier quoted context omitted.
You can just... not live in California. Most other places are doing just fine and experiencing the usual moderate economic instability that happens every decade or two along with the rest of the world. If we do consider the ethics, there's a lot of contradictions built into why someone would want to live there so badly to do the kind of work the blog post is concerned with. Their efforts are better rewarded moving th…
I actually considered that, myself. The thing is, California is where the jobs are for me. If I move out of California, I may never be able to come back. That could cost me a lot.
Re: Do I belong in tech anymore?
#86"The psychic toll of AI" -- It's sad, but each of these scenarios (barring the AI notetaker, which I haven't found to be an issue personally but ymmv) are indicative more of the culture of the company than the tool itself. From my experience it seems like the most frontier companies have the best AI-use culture. I work at a very 'AI-pilled' company, but: - Everyone reads and reviews every PR and leaves human comments…
Are there any companies that aren't AI-pilled at this point?
Re: Do I belong in tech anymore?
#87> The point of a code review is not simply for good code to make it into a codebase, but to build institutional knowledge as people debate and iterate and compromise, slow as it may be. I feel like this is a very profound insight. Of course processes like this can become about the immediate utility. Reviewing is then checking work so, it can be merged and used. But the process is more about us than the code. And we l…
There's a Dutch idiom: no shine without friction. AI is all about losing every possible bit of friction, severely underestimating the value that friction brings.
And it's not just AI, the removal of friction seems to be pursued mindlessly in all areas, with not even an attempt to understand what value it might be providing.
Re: Do I belong in tech anymore?
#88Re: Do I belong in tech anymore?
#89The way AI is being used feels like it is proving that, in many orgs, what has always mattered has been the appearance of work, not results of work. Will we wake up in a few years and find out we’ve fired all the doers and are now overloaded with the fakers?
Imagine that you're given a business problem to solve. You represent the process of writing the code with a graph - each vertex is a git commit. We consider the space of all possible git commits, so the graph is infinite. All vertices are connected with directional edges, and each edge has a value "cost". If you are in commit A and you want to go to commit B, you have to pay the cost from A to B. Your goal is to find a relatively short path from empty git commit to any vertex which contains code that has some specific observable business properties.
You might notice that not everyone is equally smart, so when giving this task to real people, we'll associate "speed" with each person. The higher the speed, the lower the paid costs when traversing the graph. I'll leave the specifics vaguely undefined.
Since a part of the task is to discover information about the graph, we also need to specify that every person has some kind of heuristic function that evaluates how likely given node is to get you closer towards some vertex that can be considered a goal. Obviously, smarter people have heuristic functions that are more closer to ground truth, while stupid people are more biased towards random noise. This also models the fact that it takes knowledge to recognize what a correct solution is.
This model predicts what we intuitively think - smart specialists will quickly discover connections that take them towards the goal and pay low costs associated with them, while idiots will take the scenic route, but by and large will also eventually get to some vertex that satisfies the business requirements, even if it's a vertex that contains mostly low-quality code, because for idiots the cheap edges that seem good at first glance are the only edges they can realistically traverse.
Obviously, if you have a group of people working on the same task, you'll reach the business goal faster. Therefore, a group of people is equivalent to one person with higher speed, and some better heuristic.
This conclusion suddenly creates a well-known, but interesting situation - each smart specialist can be replaced by a group of idiots. Or, the way I heard it, "the theorem of interns - every senior can be replaced by a finite number of interns".
What AI does is it increases people's speed. Not the heuristic function, but the speed. Importantly, the better the heuristic function, the smaller the speed gains. Makes sense - an idiot who doesn't know shit and copy-pastes things from ChatGPT will have massive speed gains, while a specialist will only modestly benefit from AI.
From business perspective though, by having more idiots write more slop with more AI we traverse the graph significantly faster. Sure, we still take the scenic route, and maybe even with AI we take the really fucking long scenic route, but because the speed is so high, it doesn't matter.
And because AI supercharges idiots more than smart specialists, we have a situation where the skill of working with idiots is more valuable on the job market than the skill of doing your job right. Your goal isn't to find the shortest path, or the prettiest code, your goal is to prompt AI as quickly as possible to get you to any vertex that satisfies the business requirements.
Re: Do I belong in tech anymore?
#90The way AI is being used feels like it is proving that, in many orgs, what has always mattered has been the appearance of work, not results of work. Will we wake up in a few years and find out we’ve fired all the doers and are now overloaded with the fakers?
I find that to be a very defeatist take. It always mattered how much value you provide to the business. Writing pretty code or arguing about some implementation detail never really mattered. If you are good at coming up with solutions to problems AI is just one additional tool in your toolbox and personally it allows me to do much more than before. There were fakers before, and there will be fakers after.
True, in the same sense that sharpening your tools if you're a trader doesn't matter to your customers: what matters is that the job you deliver is good.
Making sure you put all electrical wiring in conduits rather than buried in plaster is not what most customers care about, but it will mean easier repairs and quicker improvements in the future.
Writing good (not necessarily "pretty") code and arguing about implementation details means you will have an easier time delivering your work, both now and in the future. You have a better chance of delivering code that can be maintained and understood by yourself and others, including the people who come after you.
Furthermore, when done right, these discussions keep a trace for understanding bugs and for code archeology when in the future you're trying to understand how decisions were made and the tradeoffs considered, which could massively help refactors, rewrites and decisions to drop certain parts of the code base.
Of course, you can sharpen a tool too much or at the wrong angle, or you can make a mistake and fill up your conduits with plaster, but you stand a much better chance of ending with a better, cleaner, more maintainable and understandable product if you do practice those steps than if you skip them altogether.