People still paint, despite photoshop. People still play instruments, despite Digital Audio Workstations.
There is art in the craft, and more importantly enjoyment in the craft.
I wouldn't AI generate a song because all of the fun for me and my friends is in the playing and watching. You will find that's true very often for creative people and those who enjoy their work.
If all you are doing is blasting out corporate assets, or persuing money, I don't think anyone cares what you are using, generate away.
For me this is one of the biggest features/nice-to-haves! Just a folder with text files to define your environment that you can easily sync to other devices, backup, move to the next client...
Key word there is had, while the comment you're replying to is speaking as to today minus ten years roughly.
And yeah, as a millennial I know lots of people who had a shared desktop at home, probably had a laptop in college, used a work laptop, and hasn't had a personal computing device outside an iPad and iPhone for a decade or more. Outside of those who play PC games or other niche hobbies it's getting more and more rare, at least for the people I know.
I think a lot of things stick around because they have a good bespoke manufactoring industry and maintenance practices. Old infrastructure and automations that were built during the bubble era still work and you can still get parts made for them.
If you are a technologist/generalist, aiming for small companies is a good strategy. If you're not in SV even better, you may end up in a real grass roots business and a really interesting problem domain that is ostensibly Not Software.
I personally, cannot stand the software for software industry. You, me, we have all built such arbitrary bullshit machines that link together in a web of unnecessary business. We lambast redundant jobs and useless management, but a moment of reflection for our industry and just how much software we have built for entirely self-serving purposes. So many man hours spent on the ephemeral whims of software. Sorry for the cynicism.
Less cynically, I feel the smaller the company, self-funded, the more likely a generalist will thrive and the business domain will be real-world and impactful. If it's venture funded and can pivot to advertising, it probably will. If you move away from tech hubs the wages are lower, but you might find a more fulfilling role.
It’s hard to break in to, but industrial automation can be incredibly satisfying. The code itself is quite simple compared to ‘real’ software engineering, but you’re solving actual real physical problems in the real world, with tangible (and often lucrative) physical results. It’s extremely cross-disciplinary so if you like getting on the tools that’s always an option, it’s like the ultimate ‘full stack’ development role.
It's an incredibly messy space and the particulars are going to vary wildly based on the company. A company in a more regulated space may have the finances to standardize on Siemens or something similarly fancy, but smaller manufacturers may not have any standard at all and you'll be looking at a mix of Rockwell, Allen-Bradley, Honeywell and even more niche brands and PLCs. Many vendors have "proprietary" languages, but they're all going to be very basic stuff that is essentially Visual Basic, C, or JavaScript-ish. It's not going to be a formal software development environment like you're used to. In less regulated environments, a lot of the time you'll find that the PLC/automation component is being handled by the MAINTENANCE or FACILITIES people.
So for an example of a problem I'm facing, we have some Vacuum Furnaces. Essentially before you can turn titanium into a useful implant, you have to bake titanium at a temperature above its ignition point so that the molecules can loosen up enough and release the stresses that accumulate in the forging process. As part of this process, there's eight thermocouples of different sensitivities and at least three pressure/vacuum sensors all physically wired into a "chart recorder". The thermocouple "data" is literally a voltage reading, and the chart recorder is interpreting that and converting it into an integer and storing that in RAM. These devices are about 20 years old, and it can only hold about 24 hours of data, so you have to network it with a server that can store those readings in case you ever need to prove to someone that this step of your process was done right. It's not technically complex, but these devices aren't easy to interact with and often require physically connecting to them to make changes.
There's all sorts of possibilities for really meaningful integrations with other manufacturing systems, ERP systems, data analysis and visualization, and basically a million "low hanging fruit" problems in the space that simply don't get done because don't have enough people with any technical skill at all. Most companies I've worked for literally don't care about what the solution is, so you get a ton of leeway on architecting the solution.
IMO, the best part is that it feels like you're accomplishing something. Making a real impact. You can walk the floor and see the code you wrote building things. Doing things. You know the engineer who came to you with a problem, and you delivered a solution that makes his life easier. Not to make some abstract number go up for a quarterly report, but to actually make things that are useful.
Everyone I’ve met in this role has taken a different path to get here. Some are software engineers (like me), IT or networking techs who got into automation and learned more about electronic, electrical and mechanical hardware in the process. Some are electricians or comms techs or hydraulic fitters or mechanical engineers who learned to program PLCs.
not OP but I once took an entry-level role at a small museum exhibit fabricator as their "tech guy", and many people i worked with there (vendors / external co-fabs) were showing me PLC / ladder logic stuff
Embedded software is definitely more “real” coding than industrial, but that’s partly because we don’t get as much excuse to dig into it at the industrial level.
I have been doing some embedded work and can agree, the challenges are very different. But the challenges tend to be real world, physical challenges and so feel more real and rewarding. Versus the self-made challenges of regular software.
It would seem Google account details have been compromised or otherwise correlated, with not a peep from Google, we are getting reports of scam calls to people's real phone numbers about the "business opportunity" available in their attached Youtube properties.
Another possibility is advertising shadow profiles are able to correlate logged in accounts across YouTube and other properties.
Why not have the engineers, or "implementors", known for systems thinking, build things with AI? A team of product managers building things is like saying I want my factory floor manager on the tools, running the machines. The evolution of that role just lands you at a team of implementors again, who still need a leader. You already have that.
In a sense, you're demoting your managers to implementors, and getting rid of their leadership role altogether. Simultaneously getting rid of your prior engineers and all the domain and tribal knowledge they had built up.
Its going to be wildly distributed and varied so hard to spot, but look for companies where the main output was commodity B2B assets and you can see a real impact. Marketing copy, images, graphic design in the low and mid tiers. Real businesses supplied that stuff and even adopting AI wouldn't help, since their customers could just do it in house now.
There's heaps of companies between small and conglomerate and the middle area is where the commodity asset companies lived. Generating low stakes copy, art, apps and websites for small companies.
That's fair. I would love for this to be studied one day, it would be good to know with some accuracy what proportion of creative/software is slop-factory versus novel, interesting work.
There is art in the craft, and more importantly enjoyment in the craft.
I wouldn't AI generate a song because all of the fun for me and my friends is in the playing and watching. You will find that's true very often for creative people and those who enjoy their work.
If all you are doing is blasting out corporate assets, or persuing money, I don't think anyone cares what you are using, generate away.
reply