How would all the pro-coders like to work directly with the Angular or even the lower JavaScript instead of Application Studio?
2 Likes
These things sell licenses to companies, but you know who ends up using them when they end up being too hard for the ānon-developersāā¦
Spoiler Alert
Itās developers.
1 Like
6 Likes
Well deciphering traces, understanding the difference between pre and post, understanding the difference between client side and server side, and various aspects of BOās and such are the parts that make it inaccessible that arenāt helped by what the visual system looks like. The less we need to know about the āhardware/implementationā of kinetic the easier to learn and be productive it will be.
1 Like
Iām going with Rockstarā¦ really just because itās funny.
And of course who wouldnāt want āRockstar Programmerā on your C.V.
5 Likes
One of our Sr Principal Architects said something similarā¦ they were at first very resistant to Snap, but after working with it, realized the power.
3 Likes
It remains to be seen, but Visual Tools might be the least of the worries for us developers. Declarative tools like SQL made us productive taking away all of the drugery of reading indexes, pulling in data and sorting like we did in the old days. In the next ten years, declarative code (human language) may be given to AI and it codes what they want because it knows what users want better than developer specs. 
2 Likes
Note that we are focusing on many areas of QOLā¦ but also note that we dont just have one programmer working on one area. we have multiple development teams working in many different areas in parallel. Multiple Apps teams, Tools Teams, UX/UI teams, etcā¦ not everyone can work on the same exact thing at the same timeā¦ so if we have one of those team working in one area, that doesnt mean that we have lost focus on another area.
2 Likes
4 Likes
I can see that. I think the code it generates is on a curve like the āUncanny Valleyā. When itās new, itās cute, then it gets more helpful, but you still watch it because itās wrong enough that you have to really understand it. Then it gets helpful enough that you start to ātrustā it and people use it to make things they donāt understand, but it letās you down enough where itās really frustrating! (and potentially dangerous) I think we are on the cusp of the down turn right now, and weāll get some pretty bad code written that the user doesnāt understand. But then weāll eventually pull out of that where the users still donāt understand it, but the AI is good enough to make good enough code to trust it.
2 Likes
hahaā¦ i remember the olden days when we had no built in selecting and sortingā¦ I had to write (in AlphaBASIC) my own selection code, and my own BUBBLE SORT routines to get the data correct in my Alpha Microsystems computer.
5 Likes
Was quite fun for me on my VIC-20 in interpreted BASIC my first programming language.
5 Likes
In my mainframe days, we used Job Control to select records in one step, sort in another step, and report in a third. The hard part was there was no file system. You had to specify the cylinder, blocks, or sectors for the sortās temp space. It was possible to pick the wrong location and clobber a database table. There was a file on each disc where people manually had to keep track of which files were where. Clobbering files happened far more often than I expected.
5 Likes
Aahā¦ I canāt pretend I know anything about the Alphaā¦ except that was what I had to deal with when transitioning to Epicor. I had to migrate our data out of our legacy Alpha system. Code in Fortran and data in octalā¦ wasā¦ fun?
4 Likes
What an incredibly enjoyable thread to catch up on!
I think we are all in violent agreement that Epicor needs tools for BOTH experienced professional developers AND the rest of us.
I think that the
is generous in my case, but even if it were true, it is not productive for me to learn that last bit because I have a LOT of other things I have to do in my day, and I wouldnāt use it often enough to make it stick.
4 Likes
My first programming experience was a BASIC class in 1977, on a DEC PDP-11, using paper teletype terminals. I thought it was great, because my friends at Purdue were learning Fortran, punched into stacks of Hollerith cards. 
2 Likes
Commodore64 starting point for me. College had just added the CompSci major so first-year students had to use punch cards while the upperclasses got to useā¦actual CRT terminals.
Dadgum it Iām old.
4 Likes
I took a summer course at MTU in FORTRAN 77 entered using punch cards as well the summer before starting high school. My high school programming instructors sometimes got a bit exasperated when I corrected them on properly generating random numbers in BASIC. I had more fun helping my classmates understand programming back then versus the actual course work.
2 Likes
Probably even old enough to know how many teeth Bobby Clarke didnāt haveā¦
Sounds like we need to start thinking about a big Epi Retirement Party at Insights I started out on DOS/Win 3.1
4 Likes