|
If you can create a bot that codes, It can improve infinitely. It can be revolutionary, but fictional.
|
|
|
|
|
And it will demand payment.
|
|
|
|
|
They'll function as middle men: talking with the cloud people about an issue a user is having but can't articulate themselves. The in-house Customer Rep.
As some point, users will simply be told "that is not a service" / option (instead of expecting a software fix).
At one point, no one built LOB apps; they all bought canned systems. Then the PC came out, and everyone started "programming".
We're now back to "packages" (cloud services and "the rep").
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
Allow me to take a different approach to an answer. (With the same outcome of course.)
As has been said before, there's a difference between a "handy man" and a "licensed contractor", and they have different duties.
Home owners who hire handy men to do licensed contractors' jobs to save money often wind up with a huge mess which costs even more to remedy.
I am not a Software Engineer, I have never met a Software Engineer.
Very little software is engineered. Airplane flight systems, missile guidance systems, Mars Rover systems, these are engineered.
Point-of-sale systems and Automatic Teller Machine systems, these are engineered.
Operating Systems used to be engineered, I suppose the kernels still are, but the UI less and less.
Web apps, mobile apps, business apps, these are not engineered.
I suppose that this is part of the reason why some people have such a low opinion of "Software Engineers" -- they just don't understand the situation.
There are many hacks who style themselves "Software Engineers" -- these developers should be eliminated from the work force, I wouldn't even buy a cup of coffee from them.
The tools still need to be developed and maintained by Software Engineers.
But the users of the tools are usually not software engineers, they can be software developers like me, people who know what the tool does and how best to use it, how best to apply it to a particular problem set.
So of course the particular details of what the developer does will continue to evolve.
From writing machine code, to assembly code, to C code, to fourth-generation code, etc.
If a business analyst has the ability to specify the details of a program to an nth-generation tool, then that analyst will be a developer.
And it will likely continue to be that the most experienced analyst (with the fewest bugs) will become the go-to developer for the organization (the guru).
Software Engineers will always be required.
"Computer Science" will always evolve.
Bob will continue to bless us with his benevolence.
|
|
|
|
|
|
>64
Some days the dragon wins. Suck it up.
|
|
|
|
|
Interesting, I've always used software engineer and developer interchangeably (and I've seen it used that way).
I prefer developer for myself too.
I get what you're saying though, and indeed, I'm not engineering anything.
PIEBALDconsult wrote: And it will likely continue to be that the most experienced analyst (with the fewest bugs)
Not necessarily the most experienced, but the one who just fixes the bug instead of pointing people to some ticketing system, needing approval from a manager, and then gets it into the sprint after the next (because that one's full already), so you'll have your fix in six weeks.
I've been in such an environment and I was the go-to guy.
It's often easier and faster to fix something now (mostly typo's or adding an if-statement or something like that) than to do things the "official" way.
Most of my coworkers weren't that flexible 
Sure, sometimes it's a bigger fix and I'll tell them to do it using the official channels, but then they'll say something like "Sander already knows about it" because they always came to me first.
I can tell you, when the software architect (and management) didn't extend my contract (because they thought I was too much of a cowboy), a lot of people were not happy because at least I actually got some work done 
And yeah, when things get done normally, the number of bugs is absolutely a key metric for becoming the go-to guy 
|
|
|
|
|
Sander Rossel wrote: the number of bugs is absolutely a key metric for becoming the go-to guy
The more expensive the bugs you write are, the more you'll try in the future not to repeat it, and thus you become much more valuable than someone who's yet to write such bugs. It's called experience, and it can't be bought.
|
|
|
|
|
The value of an engineer is directly proportional with the value of the equipment he/she has destroyed.
I know that because I'm a VERY valuable engineer.
Mircea
|
|
|
|
|
Not necessarily, some people are just sloppy or don't care 
I'm ehhh... very experienced
I stopped an entire factory with a SQL update once, most "experiencing" minute of my career 
|
|
|
|
|
On my first job after graduating college, one thing I was asked to develop was a script to stop and restart database...
Yes, I accidentally tested it in production. And it worked.
|
|
|
|
|
Well, that's...good, then? 
|
|
|
|
|
Me, too. 
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
Everybody has an overinflated sense of importance.
Most devs I've met throughout in my career at least are rather humble about their abilities. Which is the exact opposite of managers.
|
|
|
|
|
dandy72 wrote: Most devs I've met throughout in my career at least are rather humble
Not all though 
One of the most bloated ego's I've ever met and unfortunately worked with, and hope never to see again, was a (freelance) developer.
It puzzles me how people like him get jobs, friends, a wife and everything.
|
|
|
|
|
I think that the closer you get to any complex field, the more you know how much you don't know - how individual situations require unique solutions. I mean for those without a god complex, obv.
|
|
|
|
|
Cpichols wrote: the closer you get to any complex field, the more you know how much you don't know
I've had that belief for decades now.
At this rate, by the time I retire, I'll be convinced I know nothing.
|
|
|
|
|
|
Managers always think they are "masters of the universe" and everyone but them will go obsolete.
In the end it is they who will probably find themselves out of jobs as the future won't need them anymore...
Steve Naidamast
Sr. Software Engineer
Black Falcon Software, Inc.
blackfalconsoftware@outlook.com
|
|
|
|
|
I'm old enough to remember when COBOL was going to eliminate the need for programmers because managers would write the code themselves.
|
|
|
|
|
maker makes a shovel
100 workers get a shovel each.
101 people working.
shovel maker than makes a mechnical digger. Does the work of 100 shovel workers.
but digger opens a new job for the guy with flags and on-call repair guy
4 people have jobs.
Digger maker makes a machine that can make the digger for them, all on it's own.
The digger maker is out of a job now, and is so good, the repair guy is out of a job.
but a new job opens, the nut-job that has to figure out how to fix the automated digger maker.
3 people have jobs.
conclusion: automated code tools all great. More work with fewer people, but will likely open other jobs that we have not yet considered. Maybe only fewer people needed in total, but not 0 people.
The real threat, is the poor rubber duck that might be out of a job.
|
|
|
|
|
You know I kinda thought we Videogame developers shot ourselves in the foot with the commercialization (and then opensourcing) of powerful game engines...back in 2012.
10 years later I've only seen script kiddies think they're programmers and very lame games come to market. I'm not saying all future Shigeru Miyamoto's have to have intimate knowledge of the bare metal, but it does help to know what sinful fun you can get away with making.
I have to conclude that people who love getting their hands dirty and can fix what they created...will always be the gods the computer world pray to whilst they live.
A.I. replacing genius, in my lifetime, is little more than a funny joke.
|
|
|
|
|
Sander Rossel wrote: There are two schools of thought. Those with a background in business see developers as commodities and fully believe that programmers will program themselves out of a job field. The idea is that in some distant future, jobs like project manager, product manager, and marketing manager will still be critical but programmers themselves will be extinct as a result of the tools they created.
Which is a train of thought that has existed as long as computers existed in any real form.
Which went hand in hand for the same amount of time with the claim that in 'just a few years' everyone will have a robot that will do your housework and other day to day chores.
Myself I am still holding out for the faster than light space ship.
But I suspect that outside of movies none of those will ever exist.
|
|
|
|
|
Wordle 315 5/6
🟨🟨⬛⬛⬛
⬛🟩🟩⬛⬛
⬛🟩🟩⬛⬛
⬛⬛⬛🟨⬛
🟩🟩🟩🟩🟩
Whew! I made it!
|
|
|
|
|
Wordle 315 5/6*
⬜🟨⬜🟨⬜
🟩⬜⬜🟨🟨
🟩🟩🟩⬜⬜
🟩🟩🟩⬜⬜
🟩🟩🟩🟩🟩
Happiness will never come to those who fail to appreciate what they already have. -Anon
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
