The past few days I've posted a lot about my passionate antipathy with the no code approach, the belief that HTML and CSS are not important to learn in favor of JavaScript, HTML5 /APIs, and my ongoing pain that we disregard accessibility. Some understand why but most do not.
1
1
17
One of the reasons that people do not understand my position is because they think I'm a web 10 developer and it doesn't make sense to me. Inaccurate. I'm not a developer designer or programmer. I come from a background of language, linguistics, semantics, meaning, Behavior.
1
2
When I started in Information Technology that's when the computation part became very important to me as did retaking mathematics from simple to Advanced and studying computational linguistics and now computational Neuroscience. I have long and deep experience in our field.
1
1
1
I want to passionately Proclaim that I feel the no code and you don't have to learn languages or have an education in a wide variety of influential topics as well as an understanding of internet and web protocols and languages as well as the history of our field is very harmful.
1
4
My influences when it comes to mentors and great thinkers in our industry remain an unexpected delight in my life. But it did not include the computer scientist, and Stanford professor emeritus Donald Knuth who met Tim Berners-Lee and others once at a pre w3c conference. Crazy!
1
Professor Knuth has some wonderful and easy to understand I'm going to post a compelling short video relevance to conversations this week in the next post. He has interviews with my personal favorite podcaster @lexfridman and others as well. I'm very interested in your responses.
1
1
This video from Dr. Donald Knuth "HTML IS a Programming Language" is provocative, witty, arguable and even he shows where and why! to have discovered his work now is an utter joy for me. I hope it will be for you as well. 😊 youtube.com/4A2mWqLUpzw#100Days… #HTML #webdevelopers #NoCode

May 2, 2022 · 3:29 AM UTC

14
4
2
17
Replying to @mholzschlag
Seen this way, CSS in the browser creates a particular dynamic rendition. CSS in a page formatting rendered creates a particular page description (usually PDF). And with appropriate other attribution, HTML in a screen reader creates a VoiceML or other audible rendition.
1
Theoretically. I would answer more but I'm too lazy and tired right now no. He's enjoyable isn't he?
Replying to @mholzschlag
Consider literate programming tools as interpreters, and you see how "design documentation" can be expressed as parser generators or even code fragments or full functions. Consider each <dt>/<dt> pair to be a dictionary entry, and you can validate terminology across the business.
2
Not entirely. I don't know why you're trying to tell me the history of the world wide web but okay I'll follow up tomorrow with more insight I saw a very good interview that would be interesting to talk about have a good night
Replying to @mholzschlag
Love this thread will take a look at the video 100% 💪
1
1
Replying to @mholzschlag
Thanks for sharing this!
1
1
It's my pleasure. As you work with no code approaches I hope you will listen carefully to all of his videos it may help inform an even greater approach to truly making your products you need for your customers and improving the web while doing so I wish you well!
Replying to @mholzschlag
So to me, HTML's importance flows mainly from Roy Fielding's emphasis that a URL points to a "resource" and not just a JCL program (and a poor one at that). Through semantic markup, a resource encodes knowledge, and THAT gives both humans and computers real power in future uses.
Replying to @mholzschlag
Granted, HTML is still hardly able to encode all the nuances of intent (that's for massive XML designs like TEI and DocBook and DITA to handle). A JCL simply drives an interpreter to convert raw input into intentional output (or better termed, "rendition").