I think the fear is that softwaring engineering becomes a low-skill profession. If the models get good enough you won't need years of experience to be a decent programmer.
IMO the fear is that software engineering becomes a _high_-skill profession.
If the models get good enough to solve all of the low-skill problems, then we only need to keep around the people who are highly skilled. That means a fewer number of software engineers, and a difficult path to becoming someone who is highly skilled.
It's already a fairly high skill profession in general. The seemingly-lower-skilled roles tend to be the ones with higher design/creative requirements on the programmers.
Agreed about the barrier to entry raising though, we're already seeing that in the glut of CS grads who can't actually get a programming job right now. Personally I suspect that this is a cultural issue more than an economic one, though. Companies need to alter their expectation about entry-level engineers and develop a culture of mentorship/apprenticeship so that advanced analysis, architectural, code review, and AI management skills are all passed down successfully.
Maybe I'm misunderstanding you but I believe I'd disagree with your first point on the perceived lower skill roles with higher design / creative requirements. I've seen a lot of the software industry being software factories rather than something closer to craftsmanship or even proper ABET-style engineering and AI is indeed better than the manually written slop that was encouraged in low-creativity / low-innovation environments such as QA and a lot of infrastructure engineering like defining CI pipelines. It seems reminiscent of the waves that hit industries like coal mining and manufacturing in the US except at a much faster rate and with different driving and resisting forces in automation.
Programmer / engineer compensation in the US market at least has been looking bimodal for at least 12 years now and the first one looks even more devastated in terms of labor than the big tech companies based upon (lack of) job postings and from browsing my connections on LinkedIn.
I think its the opposite, the grunt work is done by AI, the remaining skills are difficult to acquire and software engineers command a higher premium (but there may be less software engineers in aggregate)
I've found the same, the rate of bugs has dropped pretty dramatically after switching to ai generated code. I think it's partly because ai will write 1000s of lines of unit tests without complaining. I also have a github workflow where claude runs the /code-review command on every PR.
In the world of web apps, I find the agent's ability to write good e2e tests to be a real game changer. Turns out with enough rigor you can write pretty stable mostly not flaky e2e tests. And even flaky ones are fixed quickly due to a fuck ton of assertions at every step.
Test code looks like a mess, even more than the usual LLM code. takes a while to let it go. Test report looks beautiful though.
When the test code "looks like a mess", how do you get assurance it is testing the right properties?
Like you, I've found that LLMs can improve test coverage by decreasing the amount of developer time spent writing tests. But generally, it takes a lot of manual work to set up the initial testing framework, and even then, a lot of vigilance to ensure that what is actually tested corresponds to the description of the test.
I run claude code with 'dangerously skip permissions' flag enabled, and just tell it what I want. I hardly even interact with the OS anymore. I literally just tell it "install X, fix problem Y".
Someone should develop, or vibecode I guess, a Linux tool that does exactly this. A support agent so I can just install it for my mom and she can vaguely write her issues and needs and the agent does it.
I still use chat copy/paste for this. Can't argue too much when the results work. The tried and tested alternative for niche Linux issues is browsing the internet and checking different options until something works anyway.
I do recommend checking methods against another provider. Occasionally Claude will suggest X, and Sol is like WTF are you insane? Clear often and update the prompt with your latest findings, because there are so many opportunities for the agent to find red herrings that they'll fixate on.
As with all LLM work, if you know some sysadmin, the process goes a lot smoother because you can say specifically "Write me a systemd unit file that does X" instead of a vague "I want to automate this, how do I do it" and not have a gut feel for which approaches are jank.
I’ve unbanned you. I was expecting an email reply from you, since your own message stated:
“Please respond to the formal cease and desist at frontwarsio@gmail.com
. All further communication must be through that email with my legal counsel CC’d.”
“Please only communicate via email from now on thank you.”
Because of that, I thought it was wise to keep Discord communication paused until the legal side was sorted. I haven’t had any replies from you via email so far.
Can you confirm whether your legal counsel received my response?
Hey everyone, I'm the creator of https://openfront.io, an open source io game licensed under AGPL/GPL with 120+ contributors. I've spent the last 15 months working on this game, even quit my job to work on it full time.
Recently a game studio called 3am Experiences, owned by "Mistik" (he purchased diep.io a while back) has ripped my game and called it "frontwars". The copy is blatant - he literally just find/replaced "openfront" with "frontwars" throughout the codebase. There is no clear attribution to OpenFront, and he's even claiming copyright on work he doesn't own.
Thanks a bunch of clarifying all the details! Maybe worth putting the info in some FAQ or somewhere on the website as well, always good to have somewhere for when people go looking :)
Thanks a bunch for OpenFront as well, it's a really fun game I've spent lots of hours with already, although it's really hard :P Excited to see how the trains will be worked in, but it's also really enjoyable as it is so again, thanks for working on it!
reply