21–24 of 24 posts
Earlier quoted context omitted.
Are you interested in tackling this challenge? If so, let me know.
In principle absolutely, full disclosure realistically I honestly don't see myself being able to spend time on it between everything else. Love to chat further about it if you are interested or had something specific in mind that you would like to discuss. In that case let me know the best way to contact you.
It will probably be much the same as it is today. Styles will go in-and-out of fashion(today: OOP is not cool; FP is hip), but in 25 years I for one will probably be typing ASCII characters into a text editor, debugging with logs & debuggers & print statements, and using a command line.
There seems to be a trend: As software increases in complexity, programming languages and frameworks become higher and higher level to combat these increases in complexity. For example, think about how much more complex it is to develop an Android app versus a web app. All you need to write a web app is a text editor to create three files: an html file, a css file, and a js file. Android development on the other hand…
Android is actually the perfect example of adding tools to simplify development that end up making development much harder than it needs to be.
It will probably be much the same as it is today. Styles will go in-and-out of fashion(today: OOP is not cool; FP is hip), but in 25 years I for one will probably be typing ASCII characters into a text editor, debugging with logs & debuggers & print statements, and using a command line.
25 years ago it was much the same as it is today. In 1992 people were typing ASCII characters into a text editor and debugging with logs and print statements. You can do so much more with a line of code now and there are so many more ways to make user interfaces, but the fundamental actions of the programmer are the same.