Generic software development for hire will die. Software experts in specific domains (eg. finanace, nuanced finance like investments, banking etc, medical, scientific, golf club management ... etc) will continue to thrive.
Short answer for anxiety: learn about the business your software skills serve and align with domain subject matter experts.
Personally having been remote for ~8 years it would be difficult to go back to in person or hybrid, this said I am not sure how I could prove I am trustworthy besides "trust me bro" unless I am using somebody in my network as a reference...
Employment is literally the exchange of money for intellectual power and time.
If you hired a security guard to watch your house, would you be okay with that person watching a neighbor's house for a few hours each night because they had free time from watching your house?
Edit - looks like I can't reply to you. A CEO running five companies has a built-in trapdoor. If their companies go under, they lose time, money, and opportunity to have done something else.
Short of screen captures and always-on camera, I don't think it is possible to fully prove that you are, at least superficially, available to the rest of the team.
People use things like responsiveness, turnaround times on requests, comparing timesheets to actual work delivered, and shared resources like updates to a common document to form an opinion about your availability.
I'm sure sales teams have the same issue. How do I know a sales rep on the road is actually making sales calls and not simply at a bar, day drinking? They have solved it by tying incentives to actual results and use CRMs to capture updates from sales reps to figure out if those reps are doing actual work or not.
Maybe remote software work needs to go the same way - tie pay to actual meetings attended and contributed to, tickets closed, issues raised which proved prescient in hindsight, and so on.
LLMs can help this sort of usefulness tracking. E.g., Give an LLM a meeting transcript and ask it to work out how much saimiam contributed to the meeting.
Nope, J++ was on the Microsoft JVM, whereas C# was on top of a full new runtime.
However the language extensions that were the reason for the lawsuit did indeed transition from J++ into C#, with J# being J++ on top of .NET for easing code porting.
The features were events, J/Direct (later P/Invoke on .NET), COM interop (later RCW/CCW on .NET), and Windows Foundation Classes (later Windows Forms on .NET).
And is actually the only thing I’m sad about in this whole thing. Ecstatic about the blue wave sad that they’re going to restrict AI progress. It’s the future, and it would be a horrible move to curtail it.
AI progress doesn't require doing it full ahead right now. Beyond the risks of getting out of control, you get bubbles if hype goes beyond economic reality. AI should be done more slowly with regulation and slower build out. Better to do it slowly than wreck the world with unexamined consequences.
Because it probably was. Pangram say it's too short to be certain but they think 100% of the text is possibly AI.
That doesn't mean the comment is useless, though. There's a whole philosophical discussion to be had here about whether what matters is the comment or the identity of the speaker.
This is what I think is the solution - I've tried it a few times with good results.
1. We need our own project or task plan. A simple forward-thinking TODO list is good enough. This needs to be prepared before the day begins. Daily.
2. Focus and limit scope. Focusing on doing ONLY what's on the list is the discipline I (we) lack and which we need badly.
3. Side quests are killing us. Allowing ourselves to veer off the planned daily tasks should require a complete away-from-the-keyboard planning session with pen and paper. Print it out but plan it away from the LLM. Use the LLM to summarise the problem, by all means, but do the thinking away from the LLM. The current TODO list needs to be the main input of such a deliberation. The output is the new TODO list. The objective of this away-from-keyboard exercise is simply to maintain control of the next steps.
On days where I worked with my TODO lists, I clocked out and joined the family for activities, slept sooner and better. On days I lost control of that list, the exhaustion mounted almost on the same day.
Make a finite list for the day, tick it off and go spend time with the missus, the kids or the dog. 2c.
Agreed. We're still bottlenecked when it comes to feature work because we need to think of the ideas, user test, talk with stakeholders etc. But somehow inventing loads of tasks to feel busy anyways. Those tasks are the side quests, things we normally wouldn't take on. It feels great to finally squash that bug or do that rewrite. But you're adding stuff onto everyone else's plate as well. Discussions, reviews etc, a constant barrage of new things to consider.
I work for myself, and I’d never use AI voluntarily. I mean, have you read the article in question?
I don’t see why I need to subject myself to burnout when I don’t have someone pushing me for higher productivity metrics. I enjoy thinking things through, planning, programming the bloody thing.
In all honestly, if I had to, I’d rather take drugs to be more productive than juggling a dozen agents. Being an overworked manager is no superpower.
There's another reason to go noai in your work, which is protecting your work.
It does feel like practicing being a monk not looking at it as a readily available option for most tasks, but I also believe from experience that the only way to learn is the hard way.
That's great! You do you, no one is trying to force you to do otherwise. My point is that people aren't only using AI because they're being forced to.
I also personally am not experiencing burnout from AI, although I do have to be careful to take breaks and stuff, but I've always been like that when engaged in stuff I find super enjoyable.
> people aren't only using AI because they're being forced to.
I‘d like to counter that. Those of us that don‘t use AI are loosing our jobs, fast. The industry is artificially selecting for AI users. Use AI or loose your job, sounds like a forced choice to me.
I am sure there are many who fall in that bucket, but there are also many employees who actually like AI and are enjoying using it. I know many such engineers.
And then there are people like me, who work for ourselves and aren’t being threatened by job loss. I have many friends in this category too.
That said, I’m sure there are also entrepreneurs who would rather not use AI but feel forced to in order to keep up with their competition or customer expectations. I don’t know, I haven’t heard from any of those.
I like this and then I also timeblock so I write out manually on paper every 30 minute increment, and then as the day goes you mark what you did in the previous 30 minute block. Doesn't need to be perfect but it kind of anchors you when at a desk and then it's interesting to look back at the end of the day and see how productive or unproductive you were.
The first links shows a basic failure of reasoning, which would have gone unnoticed if I was just vibe-coding.
The second link shows weak architectural sense and an inability to see the big picture.
The last link in particular is telling: the agents worked with me (over weeks to months) to implement a db abstraction layer without ever bringing up the fact that as it stands, that would have never worked with any indexes at all. I did not constrain them to my choices, but they never stopped me with that design. It took my eagle-eyed attention to their offhand comments to notice this problem, which then required a lot of rework to fix.
Unfortunately, all three comments have apparently been flagged by somebody for some reason and I can't read them. This is my least favorite aspect of hacker news. It's exhausting, honestly.
Like a sibling comment replied, you can set "showdead" to "yes" on your profile and click update" so see flagged comments. Not sure why they were flagged.
I have read that comments which appear to have been written by an LLM are auto-filtered. As these appear to mostly consist of quotations of LLM output, I expect this would be why.
I suggest putting them on a blog or something and linking to that, rather than HN comments.
Thank you for introducing me to the word "nerd-sniping"[1].
This is, as you say, exactly the paradox of having ourselves assisted by LLMs. We are no different from our cats. Except imagine the cats start making the laser lights for themselves.
That means folks using LLMs starting off with 300 bits KNOW that they lack the full payload of information to transfer to you. IOW, they know they need to transfer much more than 300, so they use LLM to fill those gaps. That's the crux of the slop universe out there. Folks are using LLMs for the 700 bits on top of their 300 bits and passing off the full 1000 bits as their own.
I echo the writer's sentiment. "I don't want to read the clanker's 700 bits. I want only your synthesis." (I can get the clanker to generate those 700 myself. Unless ... unless this whole LLM slop market is all about saving you the time to get an LLM to generate those 700!)
Short answer for anxiety: learn about the business your software skills serve and align with domain subject matter experts.
reply