4 ms·
I've been thinking that for a while. What I also thought interesting is the limited vocabulary we use for writing code. There are obvious huge benefits if other
by 6510 3y ago
I've been thinking that for a while. What I also thought interesting is the limited vocabulary we use for writing code. There are obvious huge benefits if others are suppose to be able to read your code but there are also different approaches to accomplish the same thing which are not very readable if you are used to the other approach. (implementations but also different languages) If we appreciate how hard it is to explain some technical goals (in human languages) it doesn't seem a stretch of the imagination to have an almost human programming language that is supper easy to access for untrained "programmers".
Then there are a good number of occupations that require so much memory that even the best of humans are a poor fit. I cant wait for a help desk "employee" who answers the phone immediately, knows who I am, is familiar with all my previous interactions with the company, is able to guess why I would be calling and is allowed to make decisions. It seems much better than having 100 employees who know very little trying very hard to deal with 300 calls with poor results while it costs $1500 per hour * 90 hours per week (135 000)
- 1oooqooq 3y agonot sure what you are smoking :) but you started with the divide between system programmer and business logic programmer... and ended up with some thoughts about access to information. Most call center already knows everything just by the phone number you call in. they just dont' tell you or want/can act on what they need.
- 6510 3y agoI'm pretty sure there is more to it than just search. The topic reminds me of early computers. People could imagine games and some niche company archives. The idea that it would touch everything didn't sound very likely to most.