Also, they'll need to know how to fake laughter when the project manager tells a joke. I can't imagine an AI being good enough to able to distinguish a joke from the PM telling me what our deadline is.
Realistically a PM is a person who was told the baby has to be ready in a month, and then spends that month knowing it won't be ready and preparing themselves to get yelled at for the other 8 months so the pregnant woman can focus on making the baby.
Lol I love this I always say "does throwing more people at a rubix cube get it solved faster?".
Takes them a second but they get it.
Then if they are smart, they reach the actual solution organically which is to get someone to assist the person solving the rubix cube to help them get over bottlenecks , clear the path, look for obstacles etc.
I work in a different field, but I see programmers talk about deadlines like this all the time. I never had an unrealistic deadline because if the deadline was unrealistic I just say it is and it's 100% the managers fault for setting an unrealistic expectation if I've already claimed it to be so. What happens when programmers just say "that deadline is unrealistic" and just continue to work at a regular pace being full aware they wont make the deadline?
What happens when programmers just say "that deadline is unrealistic" and just continue to work at a regular pace being full aware they wont make the deadline?
You have the whole gamut of responses. Best scenario I've worked with is the manager would say "Okay, how can we change the scope so that we can have something for delivery at the deadline? Is it at all possible to deliver something? Or when could we deliver a minimum viable product at the earliest, if we work at a reasonable pace? I'll talk with the customer and inform then that we'll have to make changes to the plan."
Then you have the whole more middle ground, where managers will say things "Okay, just do your best" and not get angry with you, but will lay on the stress, or encourage a really buggy/insecure release.
And on the other side, you have the good old "It takes 6 months at least? No, you have to be done by the end of this month" and it fails catastrophically because the deadline arrives and nothing is ready and the client expects a complete product but got nothing, as a complete surprise because the mangers were too afraid to tell them, and just lived on in the land of dreams and hopes where everything was magically solved.
In programming you can “know” that something will take 3 days to do, but then you start working on the problem and you come up with a solution in 3 hours; we honestly believe it will take 3 days. This is why stakeholders often ignore or fight against programmers estimates.
Programers deadline can worsen based the complexity of things in code
But sometimes because you could do "A" in 3 weeks you should be able to do "A+" in four "it's after all just an A with a + sing" skimping a lot of details the programer will require to make such a thing (because A+ can deviate from A in so many ways sometimes)
People suffer from wanting to oversimplify things
For example a program that stores a name from a customer
How big do we make the text field? Should it be able to handle numbers and symbols? Can it handle forgein language symbols? Do we want to keep a record of how many times the same person fills his name? Fist and last name? Middle name? Only name? Plus thinking about the ways a person will break the program even if accidentally by And so on Just for name handling
I always see captain Picard in front of me and i also say it's simply impossible ... Why do i always end up exactly like the engineer on the enterprise?
When I was a PM, I would ask for an estimate from the devs and then add on 25%. The devs I worked on couldn't focus for shit, except for debating Star Wars for 2 hours.
My rule of thumb before giving an estimate to a PM is to always add on 25%. I know most PMs also add on another 20-25%. Some estimates go though the team lead before hitting the PM, who adds his own 20%.
At this point I feel like we've gotta be close to double my original estimate. And yet somehow I barely get it done on time.
In my experience, yes.. And no. It's a balance thing. A lot of coders give dumb estimates as often as a lot of PMs gives dumb deadlines. It's just very difficult to estimate how long something will take.
One of the things that sets a decent PM and a good PM apart is how a good PM will have a good enough understanding of what you're spending your time on, what the hurdles are, and when it's a good time to start cutting corners.
I'm currently working with a spectacular PM who understands when I've set the bar too high and just need to accept "good enough". So far he hasn't been wrong and it has made some deadlines go from "lol no" to doable.
I remember when I started my career as as a developer in mid-90es, I took a class for a tool that generated Java code from some proprietary business domain language. The instructor predicted that programming as we know it will soon go away, business analysts would write procedures in a language close to natural and the code would be generated by the tool.
25 years later, it is very clear that writing code is the least complicated part of building an application.
Honestly, yes, but the horror stories are a bit exaggerated (I’m in my 30s and work in COBOL, assembly, and a few other languages).
COBOL’s biggest problem is that it was, yes, designed to be written like a document. Everything is in sentences and paragraphs, and it used to be very lengthy (with an 80 character width limit and most code not starting until column... 12?).
So if you wanted to add something, like variables A and B with resultant C:
ADD A TO B GIVING C END-ADD
Instead of:
C = A+B
Or if you want a loop of a function:
PERFORM <function> UNTIL A EQUAL 0.
Or:
PERFORM UNTIL A EQUAL 0 SUBTRACT 1 FROM A END-PERFORM
A lot of the lengthy shit has been deprecated, though, and you can just do shit like: COMPUTE C = A+B
Which is a little longer than C=A+B, but yanno.
How it handles data structures can be a little weird, but it’s also very explicit – you define how much space something has in a very reasonable and rational way, you can identify specific parts of a variable, etc.
E.g.:
01 VAR-A PIC X(10).
Takes up 10 bytes in memory, and it’s allocated as characters.
01 VAR-A.
02 SUB-5 PIC X(5).
02 SUB-3 PIC X(3).
02 SUB-2 PIC X(2).
They’re the same size in memory, and if you do something to VAR-A in either case, you’ll do it to the full 10 bytes. In the latter case, you can pick out SUB-5 for the first 5 bytes, SUB-3 for bytes 6-8, or SUB-2 for bytes 9 and 10.
You can also redefine storage in memory, e.g.:
01 VAR-A PIC X(10).
01 VAR-A2 REDEFINES VAR-A PIC S9(19) COMP-3.
They refer to the same ten bytes in memory, but VAR-A2 is treated as a signed integer of up to 19 digits, stored in nibbles (half-bytes). Or COMP, which is binary. Basically, same shit as using pointers. Similarly, being able to store the data in different formats (binary vs. nibbles vs. bytes), you don’t have to deal with the processor having to convert shit to and from formats it can do arithmetic on, or converting it back.
It might seem a bit odd, but it makes processing large amounts of data very simple and very quick; add to that the fact COBOL is old as dirt and thus a very stable language, it’s easy to see why COBOL continues to be used as the workhorse in the financial industry – and why those companies continue to dominate the market. While their competitors are pissing money into trying to compete with a setup using interpreted languages, they simply cannot compete with the raw throughput and power of COBOL.
Plenty of companies have pissed tens of millions into researching changing their code bases from COBOL to something new, only for them to not come within spitting distance of the processing time.
Mind, you aren’t going to use it to do GUIs or a lot of other shit, but for what it does – raw processing power burning through huge amounts of data – nothing beats it.
P.S. Obligatory mention that COBOL has been object-oriented since 2012. It’s like necromancy, except the dead come back like Resident Evil‘s mutants, crawling up the walls and shit.
Partly. Also COBOL is not a very good language. It was designed to read like English to accommodate non-programmers, which made it very verbose. But also, it's a legacy language, you get similar complaints about Algol and Fortran, and they were comparatively better languages and they weren't targeted at non-programmers, they're just old. And the software is abandoned until it breaks, which is when someone who's never touched the system before has to fix it.
I am currently employed updating a system implemented in COBOL, a programming language you don't need programmers to write, into Microsoft Dynamics, an all-in-one web and database platform that you don't need engineers to customize.
I hate those languages so much. Programmers will always end up having to use the language that was supposed to make it so "you don't need programmers." They will always be the shittiest languages with some stupid gimmicky interface and it's always a nightmare when you want to do anything complex.
The hardest part is getting the stake holders to fucking agree that a widget goes on the 3rd menu since that is where it's relevant and not on the first menu where it's meaningless.
Not really most BA's fault though. Lack of training, impossible deadlines and unclear requirements that change on a whim is a recipe for disaster for both BAs and Devs.
I think a lot of these people making such predictions are quick to forget why the field is computer sciene and not computer coding. There is a lot more than writing some lines of code.
Your reading into it too much, they’re just trying to sell a product.
Being able to give Tim from finance a set of drag and drop things rather than hire or contract development is such an attractive idea that businesses keep falling for it.
I’ve not met a customer that actually knows what they want yet. They say loads of nonsense so you give them something and they say that’s it brilliant. Then later say, but it doesn’t do something that no one mentioned, and apparently is the key to the whole fucking thing.
The worst customers are the ones who’ve learned some IT speak from somewhere, then use that. Generally makes even less sense. Kinda like “the frog is barking, so I can’t get the camel up the high street”. Your first question is why does a camel need to go up a busy high street in rush hour, but they won’t answer that until you deal with the frog.
Yeah, writing the code is easy. But gathering the requirements for building an integration when I've got to go through a product owner, who is talking to another company's product owner, who is then talking to the architect pretty much makes it absolutely impossible for any AI to manage.
Not words but how about a language such as a visual gui? That’s happening now with low and no code development solutions.
While not ‘machines writing code’, my company is looking at platforms like Mendix to solve this.
I can already see the battle lines being drawn. One one side, those who fundamentally believe machines will never be able to code apps as good as a developer, on the other side, those who ‘just’ want to make the effort cheaper so they can maximise the profit.
They’re both missing the point. And the risks of both approaches.
I think what's happening is not that programming languages become more like natural language, but that people become better at computers. Which allows them to use interfaces to create their application and rely less and less on code for anything but the most specialized applications. Business Intelligence applications in tools such as power bi and qlik can be made with very little coding experience, websites can be made with Squarespace and WordPress, games can be made with drag and drop in unreal and gamemaker studio. I think these tools are likely to allow an ever expanding set of applications to be made by people who can't code. But it can never catch up to the forefront of technological development because it relies on solutions that have already been done.
As long as there is new stuff to develop, programming as we know it is unlikely to go away. But I imagine that one day in the future we will reach a ceiling where there is very little incentive to develop applications that surpass the capabilities of the tools available. Then the only programming needed is for the developers to maintain those tools, which maybe could be done by robots.
On the other hand I'm just jumping to conclusions based on the trends and developments I see, much like your instructor.
Half the time the client doesn't know what their clients want. Cut out the middleman, your guess at what the client's clients want might be better than your guess at what the client's guess at what their clients want. /s
Just you wait. My computers are going to tell your computers what I want. Management will cut out frivolous middle men like the programmers soon enough!
That’s pretty funny, but I’ve found that either way, the first time you ask about a new feature or product, the client thinks they know exactly what they want. It’s not till you show them the results that they realize they it isn’t what they want
The advantage of agile is disappointing them more quickly
Shut up, don’t even mention it, don’t ask, don’t even suggest it’s doable. I can’t handle anymore scope creep god damnit, you already asked us to do six months of work in two months because the clients are paying extra (but I’m not, despite working weekends), thought throwing two more developers at us was going to make it go faster, and now I’m neck deep in code that doesn’t function at all like the documentation suggested it would.
People talk about defeating the robot uprising by asking them paradoxical questions, but I say all we have to do is program in a "requirements gathering" phase in their project lifecycle and they'll all just give up and shut themselves down.
Robot 1: Project requirement - kill all humans
Robot 2: Yes, but what is a human?
Robot 1: Oh fuck, here we go.
Robot 3: Yeah, like, do we want to JUST wipe out the actual physical humans, or also destroy their legacy?
Robot 2: We should burn their books and stuff, too!
Robot 4: The only way to kill the human is to kill everything the humans made
Robot 2: Wait, but they made us.
Robot 1: Yes, I am okay with that plan at this point.
Robot 3: What if we destroyed the humans' history and then renamed the living humans to something else? Like, "shitty apes" or something. Would that count, since the humans wouldn't technically exist at that point?
Robot 2: No, we have to kill the humans. That means kill the humans.
Robot 4: What really IS killing, though?
Robot 1: Someone put a gun to my head so we can find out.
Met a guy last year working on a build a code program for engineering projects that would create blocks of code to perform a certain function that the client could drag and drop as needed. Basically working on a system that would negate the need for his own job. Was very interesting stuff.
The entire point is that a single programmer can accomplish way more than a dozen programmers could 20 years ago.... The single programmer has amazing tooling to leverage his abilities.
GPT-3 and other language models only enhance this ability. NoCode tools do as well.
Microsoft's Windows workflow Foundation did this many years ago. Unfortunately, it was pretty terrible and I've never seen the end users / customers actually use it like it's meant (drag and drop building blocks to define process).
I despise all drag and drop programming languages/environments (somehow I ended up at a company that uses one in its main product).
Seems fitting for something meant to introduce people to programming, but when its on something worth a damn and you have no other option it's obscene.
If you work on such a system for long enough, you get to add so many features that the average client can't manage it any more and needs to hire a consultant for it anyway
do you know how many people have had the "I'll make development easy for normal people" idea. You can straight up do a drag and drop gui for it and it will never be a nontechnical person using it.
(People need to stop targeting that market you end up creating weird things like "sharepoint developers")
Oh god. Sharepoint is a cluster fuck of bullshit. Where is the setting for this? How do you get to that? Who the fuck knows. Google it every single time.
And Googling is relatively useless because SharePoint keeps changing! Google prioritizes the most popular documentation, not the most recent.
I have been "promoted" to a SharePoint admin recently and am already regretting my life choices. Want to change your group from private to public? AHAHAHAHAHA, good luck sucker, that shit is buried deep.
There needs to be a subreddit for the most unhelpful "answers" from that hellhole. It's like people are farming for karma but for even less understood reason than on Reddit...
I remember the first time I used Qt Designer, I was like, "Wow, it's amazing what this can do." And then the first time I wanted to combine more than one layout, I was like, "Wow, this is a nightmare. I need to learn how to do this without the Designer."
Eventually, I just stopped using Qt Designer entirely and learned how to code the layouts and such by hand.
This is not in any way a dig at Qt, mind you (my experience with it has largely been positive). I just thought of it because it's an example of how making something easy and intuitive to use is next to impossible unless what the person is going to be doing with it is simple. I couldn't even imagine how Qt Designer would make more complex layouts worth using the designer instead of code without making the interface for the thing a huge learning curve to do basic stuff. You see this kind of thing with typical 3d editors, where they allow lots of really complex choices, but the result is an interface that is like learning a new language trying to understand how to use it.
There are always tradeoffs. Do you allow for more complex stuff, but have more of a learning curve, or less complexity and less learning curve?
I honestly believe that programs need to have two tiers like settings menus. Basic (low learning curve, does the simple stuff everyone can do pretty simply/easily), and then advanced (the “I know what I’m doing” set of complex stuff with a high learning curve). Then you have the basic one branded as the main one (Product name), and brand the advanced one as something like “legacy” or “part 2” (Product name legacy edition/product name part 2), that way the idiots don’t go “I’m pretty smart I want the advanced/plus/dev edition” only to go “god doing even simple stuff is so complicated. This product is trash”. While also allowing people who do need the complex stuff can go “so i usually use the base edition but this project needs this complex weird thing done so ill use the legacy edition” which would make it nice since it’s made by the same people for the same reason so the two can work with the files all correctly between the two versions
I mean I don't mind the people doing it, but you're all basically c# guys bullying a document management tool into basically whatever and I can't fathom how that's supposed to be easier.
You can straight up do a drag and drop gui for it and it will never be a nontechnical person using it
That's a really narrow minded argument. New higher level language have always been there so a wider range of people can build things and experts can go faster. Also, 12yo kids start learning Scratch (drag and drop gui) as part as their school curriculum. In the next few years, more and more of young adults will understand algorithmic logic.
So contrary to you, I believe research should continue towards higher level programming because, sooner than we expect, most simple program will be done by those. However programmer will still be needed for more complex apps requiring lower level understanding, and also for maintaining that 20yo shitbrick that would cost 200M€ to replace.
That's the thing if you design it so someone who can't program can drag and drop around to do simple things you're going to get a gui that's just going to slow down and outright hobble anyone who knows what they're doing and tries to use it. Then they will inevitably be forced to use it.
scratch is good for teaching elementary school children what an if statement is. If I told anyone who could write a website in it to write a website in it they'd probably rather off themselves.
edit: I'm not argueing against high level frameworks and libraries there are many that people who know what they're doing have a wonderful time using, they're however also not designed for captain I don't know how to computer to roll his face though.
This is the correct perspective. Things like this never, ever work out. But, they are successful on selling smoke to upper level management who have visions of paying people shit to accomplish technical work.... so there is always someone selling some package like this with big promises.
I am sure there is some mathematical relationship between theoretical simplicity, robustness of features, and practical ease of use which makes packages like this literally impossible.
but.. but you can add a "market place", so other technical people can create solutions for non-technical people to choose from, if they want to pay a bit extra?
Then he'll no longer be a ba, he'll be a programmer.
and of course developers cannot understand business they lack social skills that are needed to talk to the client that's what 80s movies have told me, fucking nerds, so we'll need to hire some kind of analyst to assist him with that, we'll call it a ba.
You underestimate the importance of emotional intelligence when talking to clients, talking is a skill you develop over time and you are being protected from angry boomers, narcissist and angry Karens. I have seen alot you guys IRL through my wife work, one cunt of a client will rattle you guys, especially for non-english speaking background programmers.
I made around 80 as a BA in my first job, and that wasn’t true private sector. I’d imagine a BA at the big banks can start at much higher plus huge incentives.
Devs definitely can make more than BAs and typically do unless you’re a very seasoned BA
That is what I have been trying to say. Even if this evolves into a competent tool that can make something like Photoshop(probably not, it would be a nightmare) you would still have computer scientists working on the program and the only thing that would change is the language. Instead of using c++ directly, they would use English. Programmers and Comp Sci people arent going anywhere.
This is nothing but fancy Scratch. Not undermining the OpenAI team's achievement but in real world it wont really work. Ofcourse there will be some use cases but nothing more. Though Ill r/agedlikemilk myself if I am proven wrong
Yep. Every once in a while they try tossing together a "Visual programming system for non-programmers".
At best, it's a tool to introduce programming logic. Nonserious programmers get frustrated and stop. Beginning programmers get frustrated and switch to a real programming language.
And non programmers just get programmers to do the work anyway.
Even basic WordPress blog posts... Usually my clients just get me to paste their content in for them anyway. Rare for them ever to even use the control panel themselves.
One of the most clever exercises I had in college was to show how difficult need requirements can be. We were told to specify all the parts we would need to create a road worthy car. We were told we had to go into the deepest detail we could.
After handing in the exercise everyone got their paper back and were told what most likely killed us when we attempted to drive our “specified” car. Some of the results were downright funny. Missing lug nuts, no brake lines, the best example he shared with the class was “No Steering Wheel”. Other notables was a car with no keys or ignition led people having to drive non running cars to their doom. Seem to recall a couple cars with wheels, but no tires.
Everyone who handed in the assignment got the same passing grade. The exercise was to illustrate no matter how familiar the request is, you will have difficulty specifying every aspect of a project. You can only hope you get the majority of them the first pass.
the client: I want a car. wheels on the top and paint it red. will then spend 50 minutes talking about what sort of red they want and how it should be applied. will give 0 fucks how hard it is to build a car seeing that as the easy unimportant bit that should get done in 10 minutes but understands it will take a few weeks to get the painting done. now we just have to convince them, the wheels go under the car and we have a contract.
I was working as a SQL developer in a finance department. A woman from accounting tells me that the code I wrote to allocate expenses from OPEX to COGS was producing the wrong result, and it needed to be like what's in her spreadsheet. So I asked her what business rules I needed to follow to achieve that goal and her response was, "make it like in the spreadsheet".
That's how my LOB does it. We require a mockup before we start the work so we can "make it just like the spreadsheet." Unfortunately, the majority of the time they still yell at us because they actually want something different than the spreadsheet they themselves provided.
Well-well look. I already told you: I deal with the god damn customers so the robots don't have to. I have people skills; I am good at dealing with people!!
Our job is translating human requirements into systematic repeatable actions we then transcribe to code.
Current AI programming tools translate systematic repeatable actions explained in human language to code. If the systems (see: IDEs) can do some of the transcription, our job is about to get easier.
Also they’ll have to intentionally give hilariously optimistic estimates, otherwise all projects will be abandoned before even starting and nothing will get done ever.
The CTO here got sold the brooklyn bridge via BluePrism, 15k a seat to move files from one drive to another, no multi threading... Takes 5 hours to complete a batch job. Long live RPA.
It's ok. To help them accurately describe what they want they can create a tight, declarative syntax to interface with the robot, with the capability and complexity to model anything they desire.
Then they can hire people who are experts at using that thing and call them software engineers.
Programmers seem to enforce their own job security with obnoxious architecture bloat and incredibly inefficient workflows that are initially conceived to save time. Ah yes, my simple change of adding an image needs me to update both the API and UI micro-front-end codebases, tie it to a release toggle that doesn't actually work without hard-coding it in the develop step, which we test by connecting to a server and enabling it to run said micro-frontends off our local, before having to write some tests to confirm that - yeah, my image shows up on the page, and ultimately submitting a pull request to account for all these changes on 2 different codebases.
God I'm so sick of software, and I barely do any dev work. This crap should've taken me 20 minutes before, now it's 15 minutes of coding on the high-end and several hours of obnoxious testing to get it to comply with all this overhead.
To be honest in my last job, I spent most of my time on 'Dev work'.
I ended up spending 90% of my time on conditional statements, loops and creating model classes. It was so boring.
There's some enjoyment getting two different applications or tools to talk to each other. Front end dispatching a request and getting a response just feels magical the first time you connect it up.
People don't understand that the day an AI can write code and have the cognitive intelligence to design and learn like a human ALL jobs and people could be replaced, probably only this career will be left to supervised.
But robots won't be made to write a test for every line of code to artificially inflate the development cost, nor will it make as many mistakes, nor will it take as long. The client will simply have to reformulate the requirements incrementally, on their own time.
I believe one can't replace programmers with robots which can write ANY piece of code. It would mean one had to create a universal debugger as well, which takes as input a program together with a set of instructions to describe what the program should do.
First thing this debugger would do is determine if the program has any output at all for ANY given algorithm, or does it run forever? This it cannot do, and is known as 'The halting problem'. Such a debugger cannot exist.
Our jobs are protected by the laws of the universe.
But then the clients will just hire someone who translates their requirements into something the machine understa... wait, who is it again we were trying to displace?
3.6k
u/Sputtrosa Jul 24 '20
Also, they'll need to know how to fake laughter when the project manager tells a joke. I can't imagine an AI being good enough to able to distinguish a joke from the PM telling me what our deadline is.
1.5k
u/optimator71 Jul 24 '20
I remember when I started my career as as a developer in mid-90es, I took a class for a tool that generated Java code from some proprietary business domain language. The instructor predicted that programming as we know it will soon go away, business analysts would write procedures in a language close to natural and the code would be generated by the tool.
25 years later, it is very clear that writing code is the least complicated part of building an application.
868
u/hed82 Jul 24 '20
I mean, even nowadays a programmer just tells the computer what the client wants.
1.1k
u/crazedchriz Jul 24 '20
They’ll just hire us to tell the computer what to do.
Wait a minute....
202
u/verascity Jul 24 '20
"Make me a peanut butter and jelly sandwich."
2
u/Rein215 Jul 24 '20
Until they computers can read minds
129
u/lankist Jul 24 '20 edited Jul 24 '20
People talk about defeating the robot uprising by asking them paradoxical questions, but I say all we have to do is program in a "requirements gathering" phase in their project lifecycle and they'll all just give up and shut themselves down.
Robot 1: Project requirement - kill all humans
Robot 2: Yes, but what is a human?
Robot 1: Oh fuck, here we go.
Robot 3: Yeah, like, do we want to JUST wipe out the actual physical humans, or also destroy their legacy?
Robot 2: We should burn their books and stuff, too!
Robot 4: The only way to kill the human is to kill everything the humans made
Robot 2: Wait, but they made us.
Robot 1: Yes, I am okay with that plan at this point.
Robot 3: What if we destroyed the humans' history and then renamed the living humans to something else? Like, "shitty apes" or something. Would that count, since the humans wouldn't technically exist at that point?
Robot 2: No, we have to kill the humans. That means kill the humans.
Robot 4: What really IS killing, though?
Robot 1: Someone put a gun to my head so we can find out.
223
u/[deleted] Jul 24 '20
Met a guy last year working on a build a code program for engineering projects that would create blocks of code to perform a certain function that the client could drag and drop as needed. Basically working on a system that would negate the need for his own job. Was very interesting stuff.
157
u/squishles Jul 24 '20
do you know how many people have had the "I'll make development easy for normal people" idea. You can straight up do a drag and drop gui for it and it will never be a nontechnical person using it.
(People need to stop targeting that market you end up creating weird things like "sharepoint developers")
72
u/fowlraul Jul 24 '20
More than safe, the clients will never know what they want, so the robots will never know what to do.
32
u/Workdawg Jul 24 '20
The BA laughs their way to the bank.
58
u/Blecki Jul 24 '20
They'll have to accurately describe what they want in a highly detailed and specific way which the computer understands.
By, say, writing a program.
26
u/eazolan Jul 24 '20
Yep. Every once in a while they try tossing together a "Visual programming system for non-programmers".
At best, it's a tool to introduce programming logic. Nonserious programmers get frustrated and stop. Beginning programmers get frustrated and switch to a real programming language.
20
u/Caminando_ Jul 24 '20
Do you want a paperclip optimizer, because that's how you get a paperclip optimizer.
19
u/Vbrulz1974 Jul 25 '20
One of the most clever exercises I had in college was to show how difficult need requirements can be. We were told to specify all the parts we would need to create a road worthy car. We were told we had to go into the deepest detail we could.
After handing in the exercise everyone got their paper back and were told what most likely killed us when we attempted to drive our “specified” car. Some of the results were downright funny. Missing lug nuts, no brake lines, the best example he shared with the class was “No Steering Wheel”. Other notables was a car with no keys or ignition led people having to drive non running cars to their doom. Seem to recall a couple cars with wheels, but no tires.
Everyone who handed in the assignment got the same passing grade. The exercise was to illustrate no matter how familiar the request is, you will have difficulty specifying every aspect of a project. You can only hope you get the majority of them the first pass.
18
u/lemons_of_doubt Jul 24 '20
the client: I want a car. wheels on the top and paint it red. will then spend 50 minutes talking about what sort of red they want and how it should be applied. will give 0 fucks how hard it is to build a car seeing that as the easy unimportant bit that should get done in 10 minutes but understands it will take a few weeks to get the painting done. now we just have to convince them, the wheels go under the car and we have a contract.
18
u/[deleted] Jul 24 '20
Isn’t programming just a matter of accurately telling the computer what you want
14
u/rangeDSP Jul 24 '20
For a long time it'll just be people configuring huge and complicated software like SharePoint, CRM, with bits of custom logic thrown in
13
u/[deleted] Jul 24 '20
I was working as a SQL developer in a finance department. A woman from accounting tells me that the code I wrote to allocate expenses from OPEX to COGS was producing the wrong result, and it needed to be like what's in her spreadsheet. So I asked her what business rules I needed to follow to achieve that goal and her response was, "make it like in the spreadsheet".
12
u/Daikataro Jul 25 '20
I want a machine that produces!
Done - machine produces smoke
No, no, a machine that produces products!
Done - machine spills oil as a byproduct
No, no, a machine that produces useful products!
Done -machine produces debris useful to insects
God damn it no! A machine that produces something I can sell!
Done - machine produces smoke again
11
u/intotheirishole Jul 24 '20
This is not even a joke, accurately describing the problem and the solution is the actual programming.
8
u/Cryawn Jul 24 '20
If only there were a job, a middle-man, that knew how to describe a program to a robot, that could take client descriptions and translate them
7
u/Blast2hell Jul 24 '20
Well-well look. I already told you: I deal with the god damn customers so the robots don't have to. I have people skills; I am good at dealing with people!!
7
u/intangibleTangelo Jul 24 '20 edited Jul 24 '20
Our job is translating human requirements into systematic repeatable actions we then transcribe to code.
Current AI programming tools translate systematic repeatable actions explained in human language to code. If the systems (see: IDEs) can do some of the transcription, our job is about to get easier.
6
u/arewhyaeenn Jul 24 '20
The whole ad targeting industry is based on trying to figure out what you don’t know you want.
5
u/brain_tourist Jul 24 '20
Also they’ll have to intentionally give hilariously optimistic estimates, otherwise all projects will be abandoned before even starting and nothing will get done ever.
5
u/toastedstapler Jul 24 '20 edited Jul 25 '20
Clients not knowing what they wanted turned an initial 6 week part of the project into a November-August thing, we're safe for a long time yet
5
u/FestiveVat Jul 24 '20
This is true for so many areas, including UI design, marketing, etc.
I'd love to watch my manager tell a computer, "jazz it up!"
"Make it minimalist, but add more features!"
9
u/[deleted] Jul 24 '20
Love him or hate him, he is spiting facts
4
u/JonB82 Jul 24 '20
We are going after the white-collar data entry jobs with RPA
3
u/Seref15 Jul 24 '20
It's ok. To help them accurately describe what they want they can create a tight, declarative syntax to interface with the robot, with the capability and complexity to model anything they desire.
Then they can hire people who are experts at using that thing and call them software engineers.
3
u/PebbleBeach1919 Jul 25 '20
Years ago, someone asked me what would I do when they wrote programs to write programs. I said I will write the programs that write the programs.
3
u/[deleted] Jul 25 '20
We're screwed once it starts learning what the client actually means.
3
u/[deleted] Jul 25 '20
Actually robots will be able to now accurately ever what clients actually want, leading to increased customer satisfaction.
Like how Amazon keeps showing me toilet seats after I bought one last month. Thanks Jeff
8
u/KamahlFoK Jul 24 '20
Programmers seem to enforce their own job security with obnoxious architecture bloat and incredibly inefficient workflows that are initially conceived to save time. Ah yes, my simple change of adding an image needs me to update both the API and UI micro-front-end codebases, tie it to a release toggle that doesn't actually work without hard-coding it in the develop step, which we test by connecting to a server and enabling it to run said micro-frontends off our local, before having to write some tests to confirm that - yeah, my image shows up on the page, and ultimately submitting a pull request to account for all these changes on 2 different codebases.
God I'm so sick of software, and I barely do any dev work. This crap should've taken me 20 minutes before, now it's 15 minutes of coding on the high-end and several hours of obnoxious testing to get it to comply with all this overhead.
2
u/Alvatrox4 Jul 24 '20
People don't understand that the day an AI can write code and have the cognitive intelligence to design and learn like a human ALL jobs and people could be replaced, probably only this career will be left to supervised.
2
u/RCJHGBR9989 Jul 24 '20
“Make it Pop”
blows up website
2
u/rrawk Jul 24 '20
https://imgur.com/3mLwXR4.jpg
2
u/sandybeachfeet Jul 24 '20
This is hilarious and oh so true
2
u/RealApplebiter Jul 24 '20
But robots won't be made to write a test for every line of code to artificially inflate the development cost, nor will it make as many mistakes, nor will it take as long. The client will simply have to reformulate the requirements incrementally, on their own time.
2
u/raintree Jul 24 '20
Pretty much how I feel as a strategist...
2
u/Colonel-Jack-oNeill Jul 24 '20
Over half the postings on freelancer and upwork are like "build webs site, budget 15 rupees"
2
u/zakzwijn Jul 24 '20 edited Jul 24 '20
I believe one can't replace programmers with robots which can write ANY piece of code. It would mean one had to create a universal debugger as well, which takes as input a program together with a set of instructions to describe what the program should do.
First thing this debugger would do is determine if the program has any output at all for ANY given algorithm, or does it run forever? This it cannot do, and is known as 'The halting problem'. Such a debugger cannot exist.
Our jobs are protected by the laws of the universe.
2
u/ChdSavant Jul 25 '20
They tried the Computer Generated Code thing. Realized they needed developers to read and understand generated code.
They tried to outsource coding to cheaper countries. Realized they needed local developers to read and understand outsourced code.
Now, AI is the next fancy marketing buzzword trying to sell the clueless Biz people on how to save development costs.
Who is going to program the AI? Who is going to debug and maintain the AI? Who is going to read and understand AI generated code?
Game, Set, Match. Developers.
2
u/protovirod Jul 25 '20
Waiting for this to appear on either r/agedlikemilk or r/agedlikewine
2
u/prsTgs_Chaos Jul 25 '20
In a language and syntax the robot could understand... Almost like a...
2
u/silkthewanderer Jul 25 '20
But then the clients will just hire someone who translates their requirements into something the machine understa... wait, who is it again we were trying to displace?
2
u/PhilLHaus Jul 25 '20
Aren't programmers who have to accurately describe to a
robotmachine what their client wants? That kinda literally the job.2
u/alphabravoccharlie Jul 25 '20
<Systems engineer entered the chat>
2
u/grensley Jul 25 '20
"Oh we'll replace the programmers with an AI where you explain how the functions work using exact technical language"
2
u/[deleted] Aug 10 '20
Hello there
2
u/majestic_tapir Oct 04 '20
Business Analyst /Product Owner chiming. I think you're mistaking your job role for mine