Pseudocode: A secret weapon to improve code efficiency
Recently, Yonatan Doron published an article on Medium titled "The Art of Code - Why You Should Write More Pseudocode". As a fan of pseudo-code, I really like this title. Pseudocode refers to "code" that describes what you want to do or what you want to communicate with, but it does not belong to any particular language and does not use any correct API or other content.
Writing annotated pseudo-code helps organize ideas, boost motivation, and plan expected code results in advance. That way, when we start writing code, we always have this mind map or framework to help us focus and improve efficiency.
Jeremy Keith once compared it to writing a script:
"When a user submits a form, a modal dialog box with confirmation information is displayed." Then he encourages everyone to write a script...but I am not referring to scripts in the JavaScript sense; Write down each step you want to complete. Once done, translate every line of script you wrote in English (or Portuguese) into JavaScript.
I see educators using this technology time and time again. But it’s not just for teachers to use and students to learn – it goes a long way toward anyone. I find myself writing pseudo-code before writing real code, and of course, sometimes I keep it in code comments. Most commonly, I use it in Notion documentation or Slack conversations to express my point of view.
Even simple ideas:
<code>如果env.dev停止郵件投遞</code>
Anything that has logic and branching or step-by-step operations will benefit greatly from it. Please note that this code is not a valid code. It doesn't work in any language I can think of. Sometimes, I will add some brackets or semicolons casually out of muscle memory. Who cares? It's just about communicating ideas with yourself or others.
<code>如果(支持網(wǎng)格)使用網(wǎng)格否則使用flexbox將內(nèi)容布局在基本行中</code>
This is very natural. They probably won't care about grammar, they will only understand what it means.
<code>在表單提交時(shí)驗(yàn)證如果存在錯(cuò)誤顯示錯(cuò)誤;否則提交到api;如果api成功顯示ui成功;否則顯示ui失?。?lt;/code>
(After writing this, it reminds me of uilang. See how the plain text code blocks work there.)
Yonatan's article lacks real pseudo-code examples, so I asked around. Check out these great examples!
My entire notebook is pseudo-code...
These are converted to comments before starting to encode so that I can know what I'm doing and what pictures I've made afterwards. twitter.com/9vfJYfweDh
— Ruth John (@Rumyra) May 28, 2019
Whiteboards are great for writing pseudo-code as well as adding graphics. picture. twitter.com/56FUu4rhmU
— norom (@_norom_) May 28, 2019
Oh, I used to do this...pictures. twitter.com/lQi4Y8RhwP
— Ben Koppenens (@bkoppenens) May 28, 2019
Always use it! picture. twitter.com/YFVVNwls5M
— Bryan (@iamBryanSanders) May 28, 2019
Trying to use both JavaScript and php can sometimes be a bit tricky picture. twitter.com/Xp0bQyV86D
— frankie | webdev (@azoicx) May 29, 2019
Belated join. Quick script mapping. picture. twitter.com/n1kYDxKgya
— Adam Styles (@thelibstyles) May 31, 2019
I was surprised how much pseudo-code is written on paper! This is really cool. It's a little weird for me because I rarely do anything with paper. I probably should.
The above is the detailed content of Pseudo Code. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

There are three ways to create a CSS loading rotator: 1. Use the basic rotator of borders to achieve simple animation through HTML and CSS; 2. Use a custom rotator of multiple points to achieve the jump effect through different delay times; 3. Add a rotator in the button and switch classes through JavaScript to display the loading status. Each approach emphasizes the importance of design details such as color, size, accessibility and performance optimization to enhance the user experience.

To deal with CSS browser compatibility and prefix issues, you need to understand the differences in browser support and use vendor prefixes reasonably. 1. Understand common problems such as Flexbox and Grid support, position:sticky invalid, and animation performance is different; 2. Check CanIuse confirmation feature support status; 3. Correctly use -webkit-, -moz-, -ms-, -o- and other manufacturer prefixes; 4. It is recommended to use Autoprefixer to automatically add prefixes; 5. Install PostCSS and configure browserslist to specify the target browser; 6. Automatically handle compatibility during construction; 7. Modernizr detection features can be used for old projects; 8. No need to pursue consistency of all browsers,

Use the clip-path attribute of CSS to crop elements into custom shapes, such as triangles, circular notches, polygons, etc., without relying on pictures or SVGs. Its advantages include: 1. Supports a variety of basic shapes such as circle, ellipse, polygon, etc.; 2. Responsive adjustment and adaptable to mobile terminals; 3. Easy to animation, and can be combined with hover or JavaScript to achieve dynamic effects; 4. It does not affect the layout flow, and only crops the display area. Common usages are such as circular clip-path:circle (50pxatcenter) and triangle clip-path:polygon (50%0%, 100 0%, 0 0%). Notice

Themaindifferencesbetweendisplay:inline,block,andinline-blockinHTML/CSSarelayoutbehavior,spaceusage,andstylingcontrol.1.Inlineelementsflowwithtext,don’tstartonnewlines,ignorewidth/height,andonlyapplyhorizontalpadding/margins—idealforinlinetextstyling

Setting the style of links you have visited can improve the user experience, especially in content-intensive websites to help users navigate better. 1. Use CSS's: visited pseudo-class to define the style of the visited link, such as color changes; 2. Note that the browser only allows modification of some attributes due to privacy restrictions; 3. The color selection should be coordinated with the overall style to avoid abruptness; 4. The mobile terminal may not display this effect, and it is recommended to combine it with other visual prompts such as icon auxiliary logos.

To create responsive images using CSS, it can be mainly achieved through the following methods: 1. Use max-width:100% and height:auto to allow the image to adapt to the container width while maintaining the proportion; 2. Use HTML's srcset and sizes attributes to intelligently load the image sources adapted to different screens; 3. Use object-fit and object-position to control image cropping and focus display. Together, these methods ensure that the images are presented clearly and beautifully on different devices.

The choice of CSS units depends on design requirements and responsive requirements. 1.px is used for fixed size, suitable for precise control but lack of elasticity; 2.em is a relative unit, which is easily caused by the influence of the parent element, while rem is more stable based on the root element and is suitable for global scaling; 3.vw/vh is based on the viewport size, suitable for responsive design, but attention should be paid to the performance under extreme screens; 4. When choosing, it should be determined based on whether responsive adjustments, element hierarchy relationships and viewport dependence. Reasonable use can improve layout flexibility and maintenance.

Different browsers have differences in CSS parsing, resulting in inconsistent display effects, mainly including the default style difference, box model calculation method, Flexbox and Grid layout support level, and inconsistent behavior of certain CSS attributes. 1. The default style processing is inconsistent. The solution is to use CSSReset or Normalize.css to unify the initial style; 2. The box model calculation method of the old version of IE is different. It is recommended to use box-sizing:border-box in a unified manner; 3. Flexbox and Grid perform differently in edge cases or in old versions. More tests and use Autoprefixer; 4. Some CSS attribute behaviors are inconsistent. CanIuse must be consulted and downgraded.
