perfectionist handicap

Original link:

I don’t know how many people looking at this site, or any site, have the habit of opening the developer tools and flipping through CSS. Given that there are quite a few articles on web production on this site, the percentage may be higher than average. Anyway, I like to do it myself. When looking at someone else’s website and encountering a beautiful or interesting effect, I have to go through it, satisfy my curiosity, and occasionally copy a few sentences. As for why I only look at CSS… Because I don’t know how to write JavaScript, when I see complex or very abstract scripts, my eyes are black (hey), and the developer tools that come with home browsers can inspect CSS very thinly. The support is far from being so good. Oh yes, and well, JAVASCRIPT is a registered trademark of Oracle USA , so calling him by his first name might get in the way !

The joke is comfortable. The reason for this is that when I wrote the copy code button two days ago, the CSS in the code box was not pleasing to the eye. I modified it, and I was even more dissatisfied. After I rolled it back, I remembered that I had made the exact same modification a long time ago and Also rolled back. It’s…a frustrating feeling. Perhaps this article should be retitled “Perfectionist Dementia.” I remembered when I was still at Blogger and summed up a series of custom CSS written at that time, but now it seems that I need to summarize not only some design choices I have made, but also summarize (and remind myself in the future) some designs I have made” don’t choose”.

for example. Suppose there is such a piece of code:

 import numpy as np def test_function (a, b): blah = a + b + 233 return blah test_function( 2 , 3 )

I want to change the style to this:

 import numpy as np def test_function (a, b): blah = a + b + 233 return blah test_function( 2 , 3 )

to match the current citation style: (text source: group see the authoring text for this use )

Foreign wine and い え ば, who で も first に 思 い Floating か べ る の が ウ イ ス キ ー.いわば Japanese wine のシンボル’s な の だ が, English notation が [general に [meter] で は Whiskey, 〔 English] ではWhisky.] であることはあまりknowledge られていない. The difference between Mi Yingboguo and このスペルのis the difference between domestic and imported products.わが和production ウイスキーの“Whisky”というBritish expression は, 手本にしたスコッチのフォルムに imitation ったものであり, それ and above の means はないようだ.て て て し も も も, ごくま れ に キ キ キ キ と と い う き を を を かける かける が とて とて を 図 し し し では では では カナ づか づか づか に な な な な

~ Ask わ ず が た り の foreign wine history (basic バージョン) Sato Akira

But the difference between code blocks and reference blocks is that reference blocks usually have very clear left and right borders, so canceling the left and right borders like this will not affect the display effect, but looks beautiful. However, the right border of the code is generally ragged, sometimes scrolling is required, and the left side usually has a variable amount of white space; so without a clear border, it is difficult to see which line is indented, or the entire paragraph. The code is indented or not, which increases the cost of understanding. Of course, if you really need this code, you can check it out by selecting it or copying it; but an article that could have been scanned and read needs one more step to get this (not dispensable) information after the change , I think such web design is not reader friendly enough.

Changed the code copy button to be always displayed (rather than displayed on mouseover) for similar reasons. Anyone, without redundant operations, can see at a glance that this code block is interactive. I like this design.

When making web pages, you are often faced with such a choice: should you choose beauty or convenience? As a person who has been making web pages as a hobby for many years, I understand the idea of ​​wishing my designs are pixel-perfect. In fact, when I change the CSS of this website, I will occasionally take out a ruler and draw 1 on the screen; but as a network As someone who has been surfing for more years, I have also experienced firsthand how uncomfortable it is to find information on a beautiful but unusable website. Of course, if the presentation form of the website itself is the key point and the information is secondary, then there is no such problem. However, for text-based bloggers, even if you don’t consider other readers, just consider myself in a year or two, and sacrifice a little beauty in exchange for a little convenience, it seems to be cost-effective enough.

A lot of little conveniences, together, become a relatively easy-to-use website. Hope.

  1. Recommend a browser plug-in to friends who have the same needs: jpedroribeiro/Baseliner . ↩︎

This article is reprinted from:
This site is for inclusion only, and the copyright belongs to the original author.

Leave a Comment