{"id":17035858,"url":"https://github.com/dabeng/technical-terms","last_synced_at":"2026-02-12T10:03:04.388Z","repository":{"id":76025370,"uuid":"185890748","full_name":"dabeng/technical-terms","owner":"dabeng","description":null,"archived":false,"fork":false,"pushed_at":"2025-05-27T22:54:44.000Z","size":160,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":2,"default_branch":"master","last_synced_at":"2025-05-27T23:26:46.872Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/dabeng.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2019-05-10T00:29:39.000Z","updated_at":"2025-05-27T22:54:47.000Z","dependencies_parsed_at":"2024-03-11T03:28:35.778Z","dependency_job_id":"68387e51-73b2-4cfa-a4c5-1b1ec990cbc8","html_url":"https://github.com/dabeng/technical-terms","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/dabeng/technical-terms","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dabeng%2Ftechnical-terms","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dabeng%2Ftechnical-terms/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dabeng%2Ftechnical-terms/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dabeng%2Ftechnical-terms/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/dabeng","download_url":"https://codeload.github.com/dabeng/technical-terms/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dabeng%2Ftechnical-terms/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":270856575,"owners_count":24657691,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-08-17T02:00:09.016Z","response_time":129,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-10-14T08:48:22.856Z","updated_at":"2026-02-12T10:03:04.370Z","avatar_url":"https://github.com/dabeng.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# technical-terms\n\nAs a qulified frontend developer, it's not big deal to switch between different frameworks to develop different web applications  作为一个合格前端开发者，在不同框架间切换来开发不用web应用，不是什么大不了的事\n\nGive me half a month to get familiar with the latest framework, and I can deliever the code like a charm afterwards  给我半月时间熟悉最新框架，之后我就能顺利提交代码\n\nI deeply understand how to create the robust web apllications with the front-end best practices  我深知如何基于前端最佳时间去创建强健的web应用\n\nAs long as it can solove users' pactical problems, I'm willing to use it  只要能解决用户实际问题，我就愿意使用它\n\nI was in charge of the architecture design, technology stack selection and the implementation of core modules for a long time  我长期负责技术栈选型，架构设计和核心模块实现\n\nAll my work falls within the scope of front-end field  我所有的工作都是前端领域\n\nI have been working as a full-time frontend developer since 2011  从2011年开始，我就一直做专职的前端\n\nI once worked in RedHat for nearly six years  我曾在红帽工作了近6年\n\nDuring that period, I developed various internal systems  在那期间，我开发过各种各样的内部系统\n\nThe biggest challenge in my career I have ever faced is to promote opensoure project  我职业生涯中面临的最大挑战是推广开源项目\n\nConvincing as many community members as possible to use your opensource project is the most defficult thing  说服尽可能多的社区网友去使用你的开源项目是最难办的事\n\nYour can imagine that there are lots of options on the internet to do same things  你可以想象出互联网上有很多选择来做相同的事情\n\nYour library should be powerful and esay to use  你的库必须简单好用并且功能强大\n\nProviding users with the maximum customization space(flexibility) is the killer feature of the OrgChart libraray  给予用户最大的定制空间是OrgChart组件库的杀手级特性\n\nI have to spend extra effort dealing with non-modern browser compatibility issues  我必须花额外的力气去处理非现代浏览器的兼容性问题\n\nNot all browsers can handle the \"Ghost Node\" well  并不是所有的浏览器都能处理好ghost node\n\nIt's worthwhile to do this  这么做是值得的\n\nLeave the troubles to myself and the comfort to the customers. This is the mission of a qualified library or framework  把麻烦留给自己，把安逸留给用户，这才是一个库或框架的使命\n\nTry your best to anwser the questions reaised by the opensource comunity members  \n\nI have always firmly believed that the key to solve problems lies in changing the way of thinking, ranther than applying fashionable technologies  我始终认为解决问题的关键在于改变思考的方式，而非应用新潮的技术\n\nThere is only the most suitable solution, not the best one  只有最合适的方案，没有最好的方案\n\nVBCS allows users to develop the web applications in a what-you-see-is-what-you-get way  visual building cloud service允许用户用所见即所得的方式开发web应用\n\nI have to think from the VBCS creators' perspectives, how to allow users to develop modern web application by drag and drop UI elements\n\nAll the variants of the organization chart originate from the ingenious ideas of community netizens  所有的组织结构图变种都源于社区网友的奇思妙想\n\nAs the new feature requests become more and more, this jquery plugin is also growing larger and larger. It has transformed into a coarse-grained component, not fine-grained component anymore \n\nI borrowed from the mongoose api design style\n\ncontributing code to the opensource community benefits me a lot  向开源社区贡献代码让我受益匪浅\n\nA man can get married and divorced multiple times. A women can get married and divorced multiple times. A couple can have multiple children. \n\nThe one-to-many relationship turns into many-to-many relationship  一对多的关系变成了多对多的关系\n\nAt the next milestone, I'll expose the method to draw the line between the two random nodes\n\nAs a best practice, we should use more shapes and fewer colors to reduce negative user experience for people with color deficiency  作为一条最佳实践，我们要多用图形少用颜色，以减少对有颜色障碍的人士的负面的用户体验\n\nOnce you create an original version, you don't have to worry about other derivative ones. Cmmunity members wil naturally develop them on their own.\n\nI can't figure out why it doesn't work as expected  我想不出为什么它没有按预期的那样工作\n\nIt's entirely a matter of preference.  这完全是个人偏好的问题\n\nValid folder name is composed of alphanumeric characters, underscores and dashes  有效的文件夹名由字母、数字、下划线、破折号组成\n\nA man can marry and get divorced multiple times. A woman can also marry and get divorced multiple times too. A couple can have multiple children\n\nwe use vertical lines to connect parent and child nodes, and horizontal lines to connect spouse nodes  我们用垂直线连接父子节点，用水平线连接配偶节点\n\nIts child nodes will be arranged vertically  它的子节点会被垂直布置\n\nAs long as the business logic is self-consistent and the requirement boundaries are clear, I'm confident in delievering the frontend code with guarnteed quality and quantity\n\nLightweight and powerful are the criteria for evaluating a good frontend framework\n\nI really enjoy the process of turning ides into reality\n\nThe more layers of encapsulatin, the more difficult it is to fix bugs\n\nSuperficially, you are enjoying the nice views, but you are rethinking the optimal solution over and over again in an undisturbed environment\n\nit will take me a lot of time to fix the compatatibility issues\n\nWhat is the main job content of this position ?  该岗位的主要工作内容是什么\n\nWhat is the main development process ?  主要的开发流程是什么\n\nwhich project will I join ? 我会加入到哪个项目\n\nhow log is the development and maintenance cycle of this project ? 该项目的开发和维护周期是多长时间\n\nwhat is the career progression path for this front-end developer position ?  这个前端岗的职业发展路径是什么\n\na spinoff company of IBM -- 拆分出来的公司\n\n3.2.1 -- the major version 3. the minor version is 2. the patch version is 1\n\nTS交叉类型A \u0026 B -- 读作：A intersection B\n\nTS联合类型A | B -- 读作：A union B\n\ninteract, intercept, interpret -- 交互；拦截；解读\n\nbe like, be similar to -- 与...相似\n\nexclamation mark, question mark -- 叹号，问号\n\nsingle quotes, double quotes, backtick -- 单引号，双引号, 反引号（`）\n\nweakly typed/ weak typing -- 弱类型\n\nstrongly typed/ strong typing -- 强类型\n\naccording to the covention  --  按照惯例\n\nadopted child -- 抱养的孩子\n\nbiological child  --  亲生的孩子\n\nbig and comprehensive -- 大而全的\n\nsmall and specialized -- 小而专的\n\nExplicitly -- 显式地\n\nimplicitly -- 隐式地\n\nallocation / deallocation -- 分配/回收\n\na.k.a(also known as) -- 亦称，又名\n\nas the name implies -- 顾名思义\n\nbeforehand -- 预先；事先；提前\n\nbehind the scenes -- 在底层\n\nbe basically a -- 基本上算是一个. . .\n\nbe best used when -- 最适合用在...的时候\n\nbe comfortable doing ... -- 很轻松地做...\n\nbe good to use when -- ...适用于...时候\n\nbe intended to ... -- 用来干...的\n\nbe desinged to ... -- 设计用来干什么的\n\ncamelCase -- 驼峰命名法\n\ngreen check mark -- 绿对勾\n\nred cross -- 红叉\n\nround brackets, square brackets, curly brackets -- 小，中，大括号\n\ncost-effective -- 高性价比的\n\nemoji -- 表情符号\n\nedge case -- 边界案例\n\nerror-prone -- 易出错的\n\nfar-fetched -- 牵强的；不切实际的\n\nfeasible,  workable  -- 可行的\n\ninfeasible, unworkable -- 不可行的\n\nfigure out -- 想出；弄明白\n\nFIFO -- First In First Out\n\nflatten -- 打平\n\nfor simplicity -- 为简便起见\n\nfor that to happen, ... -- 为了做到这一点；为了实现这个目标\n\nplatform-agnostic -- 平台无关的\n\ngo deep into -- 深入到\n\nThe issue here is that -- 这里的问题是...\n\nA interfere with B -- A干扰B\n\nintuitive -- 凭直觉的；易懂的\n\nkeep ... and ... in sync -- 使...和...保持一致\n\nkeep ... out of ... -- 使 … 置身于…之外\n\nhere is where ... comes into play -- 这就是...发挥作用的地方\n\nhere is where ... step in --这就是...可以介入（干预）的地方\n\nLIFO -- Last In First Out\n\nliken sth/sb to sth/sb -- 把...比作...(同compare sth/sb to sth/sb)\n\nlowercase -- 小写字母命名法\n\nthis node is moved down two levels -- 这个节点被下移两个层级\n\nman-hour -- 工时\n\nmarital relationship  -- 婚姻关系\n\nMethodology -- 方法论\n\nmiscellaneous -- 各种各样的，五花八门的，大杂烩的\n\nnow that -- 既然\n\nomit -- 忽略掉\n\n\"one size fits all\" solution -- 万能的解决方案\n\nsolve the problem once and for all -- 彻底地，一劳永逸地解决问题\n\nover time -- 随着时间的推移\n\nplug-and-play - 即插即用的\n\npressing -- 紧急的，迫切的\n\npseudo code -- 伪代码\n\nRealistically -- 实事求是地说\n\nbe referred to as ... -- 被称为...\n\nreducer -- 归纳函数\n\nrefer to it as -- 把...称为...\n\nroundabout -- 迂回的;间接的;兜圈子的\n\nself-explanatory -- 自解释的\n\nsolid line -- 实线\n\ndashed line -- 虚线\n\nsyntactic -- 语法的\n\nA rectangle stands for a male node -- 矩形代表男性节点\n\nA willow leaf stands for a female node -- 柳叶代表女性节点\n\nthe most space-saving solution -- 最節省空間的解決方案\n\nsemantic -- 语义的\n\nsynthetic -- 人造的，人工合成的\n\ntake into account -- 考虑到;把…计算在内\n\ntedious -- 冗长乏味的\n\nin theory -- 理论上，按道理（同Logically）\n\nThat said， -- 也就是说，\n\nThere is nothing to dive into -- 没啥值得深入研究的东西\n\nTechnical debt (expensive work that must be done later) -- 技术债\n\ntweak -- 微调\n\nunder heavy load -- 在高负荷，高负载情况下\n\nunder the hood -- 在后台，在底层\n\nwhen it comes to -- 当谈到...\n\nWYSIWYG(what you see is what you get) -- 所见即所得的\n\n(fix the bug/work on IOS) like a charm -- ...立竿见影，效果超好，超顺畅\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdabeng%2Ftechnical-terms","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fdabeng%2Ftechnical-terms","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdabeng%2Ftechnical-terms/lists"}