What did they mean by this

>"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""engineer"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

>>56581041
All cut n paste hipster shit.

File: ec0.png (356KB, 680x353px) Image search: [Google]

356KB, 680x353px

>>56581041
>Michael J. Coren
>Coren
lol

>future

>>56581041
not really
https://blog.codinghorror.com/separating-programming-sheep-from-non-programming-goats/

even if you can just write in pseudocode, designing software is still harder than coding. anyone SHOULD be able to make a simple sort algorithm, even small children in middle school. but even then, they can't. you expect them to be able to design a non-trivial piece of actual software?

They mean software engineers solve qute puzzles children could do and uses that as an argument that we should write code that will write code for us. (Not a puzzle children would do)

>>56581041
essentially, as "visual" coding tools become more advanced and user-friendly, anyone will be able to create programs a-la wysiwyg-ish editing. Imagine being able to create a simple GUI program by dragging a button into a position, telling the editor what it should do, and it'll generate all the code for you.

Anyone will be able to create software but none of them will know the code behind doing so.

http://qz.com/778380/the-future-is-software-engineers-who-cant-code/

>.. visual interfaces that enable people to essentially snap together blocks of software, and bypass the actual lines of code underlying those blocks ..

>Most people still cannot code without engineers assisting. QuickBase surveyed its customers and found about 75% of them rely on IT specialists to start their projects, do about two-thirds of the work, then hand them off for the “last mile.”

So dick around with some GUI, once you've gotten bored with that you hand it off the actual programmers so they can unfuck the entire thing and do all of the hard work, then take it back and claim credit for it.

>>56581208
Which means, none of them are actually software engineers, but barely monkeys dragging shit around and doing menial tasks.

Skilled coders will always be a necessity and a highly sought after commodity. Companies might be able to push shit software for the masses for cheap with shit coders, but whenever they need something well done, they'll have to get actual skilled labor. If you're good enough, there will always be a skilled job for you.

>>56581041
>4L_87iDTxU0.jpg

Implying a nigger could do anything like this

> barley

>>56581241
>>56581208
to be honest, _over time_ those visual coding platforms will become very fucking efficient and you will probably be able to "visually" code a whole fucking mega-project and not notice a difference to hand-written software

web development engineer
design engineer
frontend engineer
backend engineer
ux engineer
test engineer

>>56581041
In the future jews will still demand niggers get affirmative action jobs.

>>56581770
>what is ue4 blueprint
C level programming style with the power of C

File: image.png (698KB, 960x1280px) Image search: [Google]

698KB, 960x1280px

>>56581693

>>56581770
Yeah, that visual basic gig sure turned out well.

>>56581041
The stuff that is outsourced to poo people right now will be done by AI in future. So you need to specialize in either design or more advanced programming if you want to stay employed.

>>56581208

Old street fag here and you're a bit behind the Times

Wysiwyg coders actually only know how to out together a UX with the barest minimum of actual functionality chiefly libraried in. Chrck it out: no loops, no branches

Exactly none of them know how to design proper and none of them should be allowed a title that excludes the word "babby"