"Uncle" Bob Martin - "The Future of Programming"

I've watched Uncle Bob's talk today and one of the key messages were that software hasn't advanced much since the 50s: this video Visual programming may or may not be the next big step, but I have to applaud anyone who attempts it in an OS manner. Unreal Studio for example executed it really good and the code it generates operates in god knows how many games.

The coaching gap: this video People early in their career thinking SQL is something UNIX greybeards did in ancient times, and which is not necessary anymore.

Robert ‘Uncle Bob’ Martin has a theory about what happened, starting around 1970, to change this to the present situation: this video

There’s a YouTube talk from Uncle Bob where he foretells a future in which software kills some people and then regulations are put into place governing software development. I think he was close in his vision. It will be Facebook and Google and millions of IOT devices that push us to that future. Big companies won’t be hurt, but your startup better be able to afford the certs or too bad. this video

At one point, you have to stop "looking for the next magical/better thing". You pick something mature enough, that works well, and you ignore new cool trends (anyway there will be cooler things soon enough). this video What I am trying to do with my framework, link , is to ignore new cool trends as much as possible and focus on real use cases. Comments welcome.

Here are a couple sides of the arguments: link -- According to the DOL there is a much smaller than typically quoted wage gap, and there are additional variables not accounted for. link Also WRT forcing women: "Uncle" Bob Martin observes that at one time programmers were 50% women. this video

I recently listened to a lecture about the future of programming, and there was a sentence that really stuck out to me. The speaker said something along the lines of "If you go to an agile conference, there aren't that many devs there and it's mostly management.* As an ops type usually only on the peripheral of sprints etc I feel I don't fully grasp the nuances of the different methods enough to really comment, but that just really got my attention for some reason. Found the video, linking at the timestamp that includes the manifesto for agile (which I think has some obvious flaws) this video

> when you spend 30 seconds making a Reddit submission to save you 3 seconds of googling, what exactly are you accomplishing? You might have seen someone say "welcome to learning Spanish, if you have any questions just ask!" and simply believed them instead of thinking it was a sperglord den where people were waiting to jump on you for not asking superior enough questions, for one thing. The sidebar of /r/learnspanish even says " If you have a question about anything Spanish-language related, ask and we'll help the best we can! ". For another, when learning something new you're pushing the edge of what you're capable of - what you want is a direct answer to just this sticking point, not a video of "5000 words every beginner MUST know!" or a page of "Twenty False cognates" which might have the answer, or a page of "Introductory Spanish" which is an advert for a training course in another country which isn't even running and hoping you can divert your already-strained attention to digging an answer out of a lot of unrelated stuff; asking a narrow, focused question on just the thing you need might be as much as you can manage. And as you say, you would ask a teacher, you would ask a friend, you would ask an IRC/Discord/etc chat, why would you assume you can't just ask Reddit? I get it, /r/powershell is full of "how do I get rid of {Name=bob} in my output" because they don't understand the object pipeline, and I answer the ones I want to answer and ignore the ones I don't want to

According to Robert Martin 50% of developers at any given time have less than 5 years of experience. [1] [1] this video