As much as I enjoy that cartoon, watch out with being snarky when giving feedback. Intent is often hard to convey in text. In a similar way, your PS might be more effective if it were stated in a more constructive way.
I do agree, though, with you that adding code snippets as images has many drawbacks. Apart from preventing the user from copying the text, and making the article longer, they also prevent users with screen readers from accessing the code (Yes, some people use screen readers to read code, as weird as that might sound :)), unless you add the code in the alt attribute.
Thanks for that thought! I'm trying to be more cognizant of accessibility and did not think about that at all. I'll be looking into this more and trying to figure out which is better moving forward then I'll update the post.
You must type each of these exercises in, manually. If you copy and paste, you might as well not even do them. The point of these exercises is to train your hands, your brain, and your mind in how to read, write, and see code. If you copy-paste, you are cheating yourself out of the effectiveness of the lessons.
I just took it a step further and made it impossible to copy and paste.
Striving to become a master Go/Cloud developer; Father ๐จโ๐งโ๐ฆ; ๐ค/((Full Stack Web|Unity3D) + Developer)/g; Science supporter ๐ฉโ๐ฌ; https://coder.today
I just took it a step further and made it impossible to copy and paste.
That make sense but the article seems way too long and heavy, and the borders only adds to the pain.
To learn how webpack works I built a boilerplate too, but I never considered to follow a tutorial. The purpose was to read the official documentation and learn how and why they are build and figure out how should I connect them.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
As much as I enjoy that cartoon, watch out with being snarky when giving feedback. Intent is often hard to convey in text. In a similar way, your PS might be more effective if it were stated in a more constructive way.
I do agree, though, with you that adding code snippets as images has many drawbacks. Apart from preventing the user from copying the text, and making the article longer, they also prevent users with screen readers from accessing the code (Yes, some people use screen readers to read code, as weird as that might sound :)), unless you add the code in the
alt
attribute.Thanks for that thought! I'm trying to be more cognizant of accessibility and did not think about that at all. I'll be looking into this more and trying to figure out which is better moving forward then I'll update the post.
I actually got the idea for images from Learn Ruby The Hard Way where the author states:
I just took it a step further and made it impossible to copy and paste.
That make sense but the article seems way too long and heavy, and the borders only adds to the pain.
To learn how webpack works I built a boilerplate too, but I never considered to follow a tutorial. The purpose was to read the official documentation and learn how and why they are build and figure out how should I connect them.