blocks|key|1109115|text|我不知道我可以写我自己的函数(php)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1109116|几年前，当我自学编程时，我写了一个完整的php+web应用程序，没有一个单独的函数。所有代码重用都是通过调用include(...)在其他.php脚本上。我学到的这本书从来没有介绍过用户定义函数的概念。(我学习函数的那一天是非常好的一天。)|offset|length|style|BOLD|1109117|entityMap^0|0|V|A|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

<h1>I didn't know I could write my own functions (php)</h1>

When I was teaching myself to program years ago I wrote an entire php web application without a single function. All code reuse was done by calling include(...) on other .php scripts. The book I was learning from never introduced the concept of user defined functions. (The day I learned about functions was a very good day.)

blocks|key|1014216|text|多态性。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1014217|一开始我并没有真正理解它的力量。导致臃肿，繁琐的程序。孩子，试着不去记起那些日子...|1014218|entityMap^0|0|3|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

Polymorphism. 

Didn't really understand it's power at first. Resulted into bloated, and over complicated routines. Boy, try not to remember those days...

blocks|key|3330906|text|我做过的最糟糕的事情就是将逗号分隔的i存储在数据库中。我没有完全理解连接，所以这是我能做的最简单的事情，但是查询太可怕了|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3330907|(WHERE+foo_ids+LIKE+"%25，$id，%25“或foo_ids+LIKE+"$id，%25”或foo_ids+LIKE+"%25，$id")。|3330908|我经常看到的最糟糕的事情是那些使用所有方法公共静态(PHP)的类就像名称空间一样工作。|3330909|编辑：|3330910|我只记得有一次，一个同学试图为数据库表创建一个XML文件|3330911|表：|3330912|teacher_id+%7C+name
+++++++++1+%7C+foo
+++++++++2+%7C+bar
++...++++++%7C+++...|code-block|syntax|javascript|3330913|他的XML：|3330914|<teachers>
++<id1>foo</id1>
++<id2>bar</id2>
+++....
</teachers>|3330915|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|12|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|T|5|N|7|14|8|@]|9|@]|A|$O|P]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

The worst i've ever done was storing comma seperated ids in a database. I did not fully understand joins so it was the easiest thing i could do but the queries where horrible 
(WHERE foo_ids LIKE "%,$id,%" OR foo_ids LIKE "$id,%" OR foo_ids LIKE "%,$id").

The worst thing i regularly see are classes that just work like namespaces with all methods public static (PHP).

EDIT: 
I just remembered the time when a school mate tried to create an XML file for a database table

Table:

<pre><code>teacher_id | name
 1 | foo
 2 | bar
 ... | ...
</code></pre>

His XML:

<pre><code>&lt;teachers&gt;
 &lt;id1&gt;foo&lt;/id1&gt;
 &lt;id2&gt;bar&lt;/id2&gt;
 ....
&lt;/teachers&gt;
</code></pre>

blocks|key|3330922|text|一些Java+-“开发人员”(lol)试图用C#编写一个软件，却不知道这是一种带有"foreach“语句的现代语言。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3330923|结果：|3330924|软件有迭代使用...迭代器。丑陋，90年代风格，典型的Java。|3330925|这让我更加讨厌Java。:-(|3330926|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Some Java - "developer" (lol) trying to write a piece of software in C#, not knowing that this is a modern language with a "foreach" - statement.

Result:

Software had iterations using... iterators. Ugly, 90s style, typical of Java.

Made me hate Java even more. :-(

blocks|key|3330955|text|我和一位同事在一个中型软件项目中担任顾问。他已经在类似的项目上工作了一年，所以他被客户称为平台上的“专家”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3330956|很快，我发现我的同事没有完全理解我们正在使用的语言中文件I/O的细微之处，因此留下了许多细微的bug。有趣的是，他之前的所有项目都有相同的细微缺陷，但客户学会了以不会触发它们的方式使用系统。|3330957|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

A colleage and I worked as consultants on a medium software project. He'd been working for a year on similar projects, so he was billed to the client as an "expert" on the platform.

Soon I discovered that my colleage didn't fully understood the fine points of file I/O on the language we were using, consequently leaving lots of subtle bugs. The funny thing is, all his previous projects had the same subtle bugs but the clients learned to use the system in ways that didn't trigger them.

blocks|key|1014346|text|当我还是个初学者的时候，我用PHP写了一些代码，不理解指针，对象，甚至元组/结构。我刚刚使用PHP极其灵活的动态类型数组构建了我所有的数据结构。实际上，你可以通过这种方式完成很多事情，这是相当令人惊讶的，但我对任何需要修改代码的人(包括几个月后的我自己)都感到很遗憾。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1014347|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Back when I was a beginner, I wrote some code in PHP without understanding pointers, objects, or even tuples/structs. I just built all my data structures using PHP's ridiculously flexible, dynamically typed arrays. It's actually pretty surprising how much you can accomplish that way, but I feel bad for anyone (including myself a few months later) that ever needed to modify that code.

blocks|key|3331047|text|在连接字符串时，我必须对每个变量调用ToString()，即使变量是字符串。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3331048|示例|BOLD|3331049|Enum.GetName(...).ToString()
myDate.ToShortDateString().ToString()|code-block|syntax|javascript|3331050|..。|3331051|entityMap^0|I|A|0|0|2|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|H]]|D|@]|E|$]]|$1|I|3|J|5|K|7|X|8|@]|D|@]|E|$L|M]]|$1|N|3|O|5|6|7|Y|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|Q|$]]

That I had to call <code>ToString()</code> on every variable when concatenating strings, even if the variables were strings. 

Examples:

<pre><code>Enum.GetName(...).ToString()
myDate.ToShortDateString().ToString()
</code></pre>

...

What's the worst technical misunderstanding you've ever seen? Worst abuse of a good system due to lack of knowledge?

Worst technical knowledge gap you've seen?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

你所见过的最严重的技术误解是什么？由于缺乏知识而导致的好系统的最严重的滥用？

问你见过的最严重的技术知识差距？
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问你见过的最严重的技术知识差距？EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问你见过的最严重的技术知识差距？
EN