Comment by SirensOfTitan
3 days ago
It's utterly unreal to me to hear so little discussion about labor organization within software during these nascent moments of LLM deployment. Software engineers seem totally resigned toward reduced salary and employment instead of just organizing labor while still in control of the development of these systems.
I really don't get it -- is it that people think these technologies will be so transformative that it is most moral to race toward them? I don't see much evidence of that, it's just future promises (especially commensurate with the benefit / cost ratio). When I do use this tech it's usually edutainment kind of curiosity about some subject matter I don't have enough interest in to dive into--it's useful and compelling but also not really necessary.
In fact, I don't really think the tech right now is at all transformative, and that a lot of folks are unable to actually gauge their productivity accurately when using these tools; however, I do not believe that the technology will stay that way, and it will inevitably start displacing people or degrading labor conditions within the only economically healthy remaining tranche of people in America: the white collar worker.
I've been writing software for 30 years, a part of it had success in the sense of being widely known and adopted for a long time. Writing software is difficult, consumes time and is difficult as you get older to focus the needed time away from other matters like a professional life and family.
With LLM, my productivity suddenly went up x25 and was able to produce at a speed that I had never known. I'm not a developer any more, instead feels like project manager with dedicated resources always delivering results. It isn't perfect, but when you are used to manage teams it isn't all that different albeit the results are spectacularly better.
My x25 isn't just measured on development, for brainstorming, documentation, testing, deployment. It is transformative, in fact: I think software is dead. For the first time I've used neither a paper notebook nor even an IDE to build complex and feature-complete products. Software isn't what matters, what matters is the product and this is what the transformation part is all about. We all here can write products in languages we never had contact with and completely outperform any average team of developers doing the same product.
Replaces the experts and domain specific topics? Not yet. Just observe that the large majority of products are boringly simple cases of API, UI and some business logic inside. For that situation, it has "killed" software.
What tool do you use, which languages? Could you give us an example of something you’ve built and how you did it 25 times faster?
You'd be surprised what you can do with Claude Code. Pick any mature programming language, including niche ones like Ada and treat the project seriously. Write detailed agent files, features spec files, start from the bottom with CI/CD and set up a test suite, coding guidelines, static analysis. Be careful to create a consistent architecture and code base early.
You'll get a lot further and faster than you'd expect.
Things will probably plateau as you master the new tech, but it's possible you'll not write a ton of code manually along the way.
Oh, your general software development experience should help with debugging the weird corner cases.
I imagine it's really hard to do this with 0 software dev experience, for example. Yeah, you'll build some simple things but you'll need and entire tech education to put anything complex in prod.
2 replies →
Using Claude code Pro with a maxed subscription and ChatGPT Codex with the business subscription.
The code is written in Dart and never wrote a line of DART in my life, I'm a veteran expert around Java, C++. The reason for choosing DART is simply because it is way readier for multi-platform contexts than Java/C++. The same code base now runs on Linux, Android, iOS, OSX, Windows and Web (as static HTML). Plus the companion code in C++ for ESP32 microcontrollers. It also includes a CLI for running as linux server.
Don't ask me for a hard analysis and data proving x25 performance increase, what I know is that an off-grid product was previously taking me two years of research/effort to build in Android/Web and get a prototype running. Now in about a month went far above all previous expectations (cached maps with satellite imagery, bluetooth mesh, webRTC, whatever apps) and was able to release a product several times per day that works as envisioned. Iterating quickly and getting direct feedback from users.
The repository: https://github.com/geograms/geogram
Overview of the apps being written: https://github.com/geograms/geogram/tree/main/docs/apps
IMHO, Codex is far superior at the moment for complex tasks, Claude is cheaper and still good enough quality for most tasks. In addition to keep several terminals with tasks in parallel, this gives me time throughout the day for other tasks with family/friends and a lot of motivation like a coding-buddy to try different routes and quickly implement a prototype instead of always being alone doing this kind of work. For example, it added an offline GPT bot but wasn't what was needed so could quickly discard it too.
These tools get lost on API implementations and the documentation folder is mostly there to provide the right context when needed. I've learned to use simple markdown documents with things to keep in mind like "reusable.md" or "API.md" to make sure it won't reinvent them. Given my experience, there are parts that I'd implement with higher quality on my own, the trade-off is that I can't touch the code by myself now. One of the reasons is that it would make more difficult for these AI to work since my naming and file structure would make it difficult for the AI to work with, the other reason is because I don't want to waste a full day on a single problem like before. As the product grows more stable is when more attention is given to the finer details. On early stages, that type of quality is still more than good enough for me.
You can try the Android or Linux versions if you are so inclined. Never in my life would I ever be able to build so much in 5 weeks.
6 replies →
If you think the profession has enough time to organize reasonable unions, you’re an optimist. Pessimists are changing careers altogether as we speak.
Either way it’s been a fun ride.
Part of being in a union tends to be lawyering up and "nailing down" exactly what everyone's duties in detail and what fair compensation might be, and what terms / conditions might be etc.
Personally I don't think they're a great fit for the software industry where the nature of the job and the details are continuously changing as technology evolves.
That's not an intrinsic part of being in a union, just a particular way they have been implemented in US.
The fundamental point of the union is to be able to negotiate as a group. That is valuable regardless of the industry.
12 replies →
Before I get into it: what careers do you think are most compelling? Especially if you think all white collar work is going to be undermined by this technology.
I wrote this up a bit ago in my essay fragments collection. It's rough and was just a thought I wanted to get down, I'm unsure of it, but it's at least somewhat relevant to the discussion here:
LLM or LLM-adjacent technology will never take over the execution of work in a way that approaches human where humans continue to guide (like PMs or C-suite just "managing" LLMs).
The reason is that spoken language is a poor medium by which to describe technical processes, and a well-enumerated specification in natural language describing the process is at-least synonymous with doing the work in skilled applications.
For example, if someone says to an LLM: Build a social media app that is like Tinder but women can only initiate.
... this is truly easily replicatable and therefore with little real business value as a product. Anything that can be described tersely that is novel and therefore valuable unfortunately has very little value practically because the seed of the short descriptor is sort of a private key of an idea itself: it will seed the idea into reality by labor of LLMs, but all that is needed for that seed's maturation is the original phrase. These would be like trade secrets, but also by virtue of something existing out there, its replication becomes trivial since that product's patterns are visible and copyable.
In this way, the only real outcome here is that LLMs entirely replace human labor including decision making or are tools to real human operators but not replacements.
I'm curious how this seed/hash/prompt of an idea relates to ladders of abstraction?
Consider "Uber, but for X"
This wasn't a thing you could deploy as a term pre-Uber.
I'm not sure what this means for your analogy, but it does seem important. Somehow branding an idea reifies a ... callable function in? ???
Maybe something like (just spitballing)
The specification-length needed for a given idea isn't fixed - it's relative to available conceptual vocabulary. And that vocabulary expands through the work of instantiation and naming things?
Which maybe complicates the value story... terseness isn't intrinsic to the idea, it's earned by prior reification work?
Hmm
Basically it seems that "Like Tinder but" is doing a lot of lifting there... and as new patterns get named, the recombination space just keeps expanding?
1 reply →
If programmers think they can just learn a trade, they’ll bein for a rude awakening when Elon comes for their jobs next. Optimus will be doing your plumbing by the time you graduate from trade school and get your paper and internships.
2 replies →
Unfortunately, it's futile to try to convince the median HN poster that labor organization could help them. They've drunk the entire pitcher of corporate anti-union koolaid.
People could be directly in the middle of losing their own job or taking on the responsibilities of 5 other laid-off coworkers, and they would still ask "what could a labor union possibly do for me??"
Big tech laid off 150,000 people last year despite constantly beating wall st expectations and blowing more money than the Apollo program on a money losing technology with the stated goal of firing even more people. Totally insane that most people I talk to still don’t think they need a union.
Two things:
1. Like most labor organizing, I think this would be beneficial for software engineers, but not long-term beneficial for the world at large. More software that is easier to make is better for everybody.
Would you still want to live in a world where your elevator stops working when the elevator operator is sick, or where overseas Whatsapp calls cost $1 per minute, because they have to be connected by a chain of operators?
2. Software engineering is a lot easier to move than other professions. If you want to carry people from London to New York, you need to cater to the workers who actually live in London or New York. If you want to make software... Silicon Valley is your best bet right now, but if SV organizes and other places don't, it may not be your best bet any more. That would make things even worse for SV than not organizing. Same story applies to any other place.
Sure, companies won't more overnight, but if one place makes it too hard for AI to accelerate productivity, people will either go somewhere else, or that place will just end up completely outcompeted like Europe did.
The "world at large" mostly consists of workers, so things that are beneficial to workers are also beneficial to it.
> your elevator stops working when the elevator operator is sick
Can you point somewhere outside of US where this is the case with unions?
The "world at large" mostly consists of workers, so things that are beneficial to workers are also beneficial to it.
When dockworker's unions are able to prevent port automation, is that beneficial to society?
So do you believe that the gains from this technology will be broadly distributed? Or will capital capture the majority of those gains?
what technologies has "capital" captured the majority of gains from?
7 replies →
> It's utterly unreal to me to hear so little discussion about labor organization
Never lived in the US, where I assume you are from. It's the same country that contrary to most countries, does not have May 1st as a Holiday. Same country that has states with at will employment, etc etc.
unreal? nope, totally coherent and expected.
The ownership class sure did a number on the white collar working class.
“I don’t need a union, I can negotiate my wages and working conditions just fine on my own”
“I’m a special rockstar guru ninja 10x dev, being held to the standards of the normals will just hold me back from my true potential”
I wish I knew which union to pitch. All I can say is what I know which is if you are dispirited with this state of affairs a great way to figure out where to go with it is to connect with your local democratic socialists of america branch, or maybe the joint union dsa effort:
https://workerorganizing.org/
[dead]
Yes, labour unions are immoral. Curtailing growth (especially in industries where it can prevent unnecessary death) for your personal needs is plain evil. I say that as someone who is both very stressed by pressure to sustain my family while cushy life is slipping away.