帝国视频网站模板,广州美霖室内设计学校,深圳电商公司排行榜,xampp wordpress安装wp博客写文章500错误Ive written a lot of blog posts. Somewhere north of 500 to be exact. All of them are technical. 我写了很多博客文章。 确切地说是在500以北的某个地方。 所有这些都是技术性的。 About two dozen of them are actually good. 实际上大约有两打是不错…wp博客写文章500错误Ive written a lot of blog posts. Somewhere north of 500 to be exact. All of them are technical. 我写了很多博客文章。 确切地说是在500以北的某个地方。 所有这些都是技术性的。 About two dozen of them are actually good. 实际上大约有两打是不错的。 The rest are just a meandering hot mess of grammatical errors, code snippets that dont work and a never-ending misuse of its vs its. Why cant I get that right?! Its not that complicated. 剩下的只是一堆乱七八糟的语法错误不起作用的代码段以及对“它是”与“它”的无休止的滥用。 我为什么不能正确呢 它没有那么复杂。 BUT. Im not here to talk about my failures. Thats what therapy is for. Im here to talk about the dozen or so roses that bloomed in a literary field of feces. These are the tips that you need to write the best technical articles. 但。 我不是在这里谈论我的失败。 那就是治疗的目的。 我在这里谈论的是在文学领域里盛开的十几朵玫瑰。 这些是编写最佳技术文章所需的技巧。 为初学者写 (Write for the beginner ) To date, my most popular article on Medium (by views) is, Heres how you can actually use Node environment variables. 迄今为止我最流行的有关Medium(按视图)的文章是“这是您实际使用Node环境变量的方式”。 When I was writing the post, I wondered if I was the last person alive who didnt fully understand environment variables. Clearly Im not. The takeaway from this is that if you think something is too simple to write about, you should probably write about it. 当我写这篇文章时我想知道我是否是最后一个没有完全理解环境变量的人。 显然我不是。 由此得出的结论是 如果您认为某些事情太简单而无法写则可能应该写它 。 Over-estimating the audience is the most common mistake you can make when writing technical articles. You dont need to dissect a compiler or invent a framework to have something to talk about. Lea Verou did an entire talk on 1 CSS property. ONE. And its one of the best presentations I have ever seen. 高估受众是您撰写技术文章时可能犯的最常见错误。 您无需剖析编译器或发明框架就可以谈论一些事情。 Lea Verou对1个CSS属性进行了整个讨论。 之一。 这是我见过的最好的演示之一。 Pick simple topics and then dive into them. There are far more people interested in learning how to trim strings than there are people who are interested in having a structured argument on how to solve the Dining Philosophers problem. 选择简单的主题然后深入其中。 对学习如何修剪弦乐感兴趣的人比对如何解决就餐哲学家的问题有结构性争论的人要多得多。 Note that Im judging the popularity of articles based on views. Theres some conjecture about whether or not this is a good measure of success. After all, good clickbait will get you views. There are sites with an entire business model based on this, and we dont hold them in particularly high esteem. 请注意我根据观点来判断文章的受欢迎程度。 关于这是否是成功的良好衡量标准存在一些猜测。 毕竟良好的点击诱饵将使您获得观看次数。 有一些网站基于此建立了完整的业务模型我们并不特别重视它们。 Another measurement we could look at is Read Ratio. The above article has a Read Ratio of 25%. One quarter of the people who visited the article actually read it. The higher the percentage, the better. It turns out that the easiest way to increase that percentage is to just write shorter posts. Take a look... 我们可以查看的另一种度量是“读取比率”。 上面的文章的“读取率”为25。 实际访问过这篇文章的人中有四分之一读过这篇文章。 百分比越高效果越好。 事实证明增加该百分比的最简单方法是撰写较短的帖子。 看一看... These are throw-away posts that are only 2 or 3 paragraphs long. Lazy writing. Me just throwing turds in the air so that I can say I wrote something that week. 这些是只有2或3个段落长的一次性文章。 懒惰的写作。 我只是把杂物扔在空中这样我可以说我那一周写了一些东西。 We seem to be in a culture that is obsessed with this target. Make shorter content! People will read it! Yeah, theyll read it, but kind of the same way they read road signs; flying down the 1 billion lane highway of the internet, stuffing their face with Combos and retaining virtually none of what they see. 我们似乎处在迷恋这个目标的文化中。 缩短内容 人们会读它 是的他们会读的但是他们读路标的方式差不多 沿着10亿车道的互联网高速公路飞来飞去用Combos塞满了他们的脸几乎什么也看不见。 Read % is not a good target. It encourages everyone to just throw turds, and what goes up, must come down. 读取不是一个好的目标。 它鼓励每个人都乱扔垃圾上涨的东西必须倒下。 A better measurement, I think, is the Reads metric. How many people actually read the article? Now we dont know how Medium calculates this, but they attest that its how many viewers have read the entire story. By that metric, a new post emerges as the top dog. 我认为更好的衡量标准是“读取次数”指标。 实际上有多少人阅读了这篇文章 现在我们不知道Medium是如何计算出来的但是他们证明这是“有多少观众阅读了整个故事”。 按照这个指标一个新职位成为头号狗。 You should never ever run directly against Node in production. Maybe. “永远不要在生产中直接与Node对抗。也许。” Which brings me to the second insight for writing successful technical articles... 这使我对撰写成功的技术文章有了第二见解... 质疑现状 (Question the status quo) While working on a demo with a friend, he mentioned to me in an off-handed way that you should never run directly against Node in production. Well I didnt know that. I had never heard that before. So I decided to research it to see if he was right. As it turns out, he was right. But he was also wrong. The answer, like everything in life, is, it depends. 在与朋友一起进行演示时他以一种过分的方式向我提及您绝对不应在生产中直接与Node对抗。 好吧我不知道。 我以前从未听说过。 因此我决定对其进行研究以了解他是否正确。 事实证明他是对的。 但是他也错了。 就像生活中的一切一样答案是“取决于情况”。 Programming ideology is littered with absolutes. Never use ternary statements. Never open a hyperlink in the same window. Never push to production on a Friday at 5 PM. Never build a website that doesnt work on mobile. Never do Select * from a database. Never force push into a Github repo. And never ever should you take any of those things at face value. 编程思想充满了绝对性。 切勿使用三元语句。 切勿在同一窗口中打开超链接。 切勿在星期五下午5点推入生产。 切勿建立无法在手机上运行的网站。 请勿从数据库中执行“选择*”。 切勿强行推入Github存储库。 而且您永远都不应以任何面值看待这些东西。 Programming is black and white. Reality is not. The second that you hear someone make an absolute statement, thats a good time for a blog post. You may find that absolute is absolutely wrong. I once heard that you should never put JavaScript in HTML. Then some guy named Jordan said, yeah, but you can put HTML in JavaScript, and today we have React. 编程是黑白的。 现实不是。 您听到的第二个声音是绝对的这是写博客的好时机。 您可能会发现绝对是绝对错误的。 我曾经听说您不应该将JavaScript放入HTML。 然后一个叫约旦的家伙说“是的但是您可以将HTML放入JavaScript中”今天我们有了React 。 Shake it up. Readers want an original opinion and everyone likes a renegade. 摇一摇。 读者想要有独到见解每个人都喜欢叛徒。 The paradox of absolutes is that as much as people like you to question existing ones, they also like it when you make your own. 绝对的悖论是就像您这样的人质疑现有的一样当您自己创建时他们也会喜欢它。 绝对发言 (Speak in absolutes) If we continue down the list of the most popular posts, we get to The greatest Visual Studio Code setup in the world. 如果我们继续在最受欢迎的帖子列表中进行下去我们将获得“世界上最棒的Visual Studio Code设置”。 This one has a far lower view count because its posted in my personal publication. As a side note, dont try and create your own blog or publication. Thats like trying to create your own magazine or TV channel. You can do it, but its way easier to just go where the readers already are. 由于它已发布在我的个人出版物中因此它的视图数量要少得多。 附带说明请勿尝试创建自己的博客或出版物。 这就像尝试创建自己的杂志或电视频道一样。 您可以做到但是走到已经是读者的地方会更容易。 Also note that even though this article has far less views than the next highest one (41K vs 113K), it only has 4K less reads (24K vs 28K). 还要注意即使这篇文章的浏览量远少于第二高的浏览量(41K vs 113K)但读取量却少了4K(24K vs 28K)。 This article makes an outlandish allegation - that my personal VS Code setup is the best in the world. This is an extremely subjective claim, and likely not even close to being accurate. But its great for a blog post because it makes the reader think, Oh yeah!? Ill be the judge of that, buddy!. 本文提出了一个怪异的指控-我的个人VS Code设置是世界上最好的。 这是一个非常主观的主张并且可能甚至不十分准确。 但是这对博客文章很有用因为它使读者认为“哦是的我将成为法官老兄”。 Anytime you make an absolute statement, you are inviting people to come and see if it can stand up under scrutiny. Developers really cant help themselves. Seeing if things stand up under scrutiny is kind of what we do. 每当您发表绝对声明时您都在邀请人们来看它是否可以接受严格审查。 开发人员真的无法自救。 看看事情是否经过严格审查是我们的工作。 Many of these people are going to disagree with you. Thats OK. In fact, its healthy. Let people like things, but also let them not like things. There are going to be people who dont like that I said to use absolutes. They are going to say that you should never use absolutes, which is itself an absolute statement. See? You cant win, so dont be afraid when at least half of your readers leave comments like this... 其中许多人会不同意您的看法。 没关系。 实际上它是健康的。 让人们喜欢事物也让他们不喜欢事物。 会有人不喜欢我说的使用绝对值。 他们会说您绝对不要使用绝对值这本身就是绝对值声明。 看到 您赢不了所以当至少有一半的读者发表这样的评论时请不要害怕... Feel the burn. And its got 432 claps - by far the most of any comment on that article. Thats fine. Let those people disagree or not like your writing style. You can please some of the people some of the time. 感到灼伤。 它获得了432拍手-到目前为止对该文章的评论最多。 没关系。 让那些人不同意或不喜欢您的写作风格。 您有时可能会请一些人。 The only article that Ive ever had go to #1 on Hacker News uses a similar strategy... 我曾经在Hacker News上排名第一的唯一文章使用类似的策略... Everything? Its ruined everything?! Of course not. Every0ne knows that DC actually ruined everything when they made, Aquaman. Now, see, you want to take issue with that statement. See how that works? 一切 一切都毁了 当然不是。 Every0ne知道DC制作“ Aquaman”时实际上毁了一切。 现在看一下您想对该语句发表意见。 看看如何运作 The other thing that we can glean for the top three posts, is that they all cover pretty popular technologies - Node and VS Code. Thats a trend that continues in the stats. 我们可以收集到的前三篇文章的另一件事是它们都涵盖了非常流行的技术-Node和VS Code。 统计数据将继续保持这种趋势。 撰写流行技术 (Write about popular technologies) If I keep looking through the list, the next several posts are about either React, or VS Code. 如果我继续浏览列表接下来的几篇文章都是关于React或VS Code的。 Writing about popular technologies is gonna get you readers. This one is kind of a no-brainer, but it bears repeating: writing about popular technologies is going to get you readers. Writing about an obscure product or technology that nobody has heard of is gonna feel like you threw a party and nobody showed up. Not that thats ever happened to me. Twice. 撰写流行技术将吸引您的读者。 这有点儿不费吹灰之力但需要重复 撰写有关流行技术的文章将吸引您的读者 。 撰写一篇没人听说过的晦涩产品或技术的感觉就像是您参加一个聚会却没人露面。 并不是那件事发生在我身上。 两次。 For me, writing about whatever is hot always feels like dunking on a six foot goal. Its too easy and nobody is impressed when you topple your four year olds Fisher- Price Grow-To-Basketball toy. But the fact remains that talking about subjects that people are interested in is simply better than talking about ones they arent. That shouldnt be an earth shattering revelation. 对我来说写些“热门”的东西总是感觉像是在踩着6英尺高的球门灌篮。 这太简单了当您推倒四岁的费舍尔价格成长型篮球玩具时没人会留下深刻的印象。 但是事实仍然是谈论人们感兴趣的主题比谈论他们不感兴趣的主题更好。 那不应该是破天荒的启示。 The trick is to figure out how to use those things to leverage what you actually want to say in an article. 诀窍是弄清楚如何使用这些东西来充分利用您在文章中实际要说的内容。 For instance, I work on Azure at Microsoft. If I want to write an article about best practices for running Node apps on Azure, I could do it and then call it Best practices for running Node on Azure. There is a name for an article like that. Its called, documentation. 例如我在Microsoft的Azure上工作。 如果我想写一篇有关在Azure上运行Node应用程序的最佳实践的文章则可以这样做然后将其称为“在Azure上运行Node的最佳实践”。 这样的文章有一个名字。 它称为“文档”。 Instead, I wrote an article titled, You should never ever run Node apps in production. Maybe. This article benefits all Node developers while still conveying the ideas for how to best run Node apps on Azure. Since Im no longer scoped to just Azure, I get to write to all Node devs and you dont have to be using Azure to benefit from the content. 取而代之的是我写了一篇文章标题为“永远不要在生产环境中运行Node应用程序。也许吧。” 本文使所有 Node开发人员受益同时仍然传达了有关如何在Azure上最佳运行Node应用程序的想法。 由于我不再局限于“ Azure”因此我可以写信给所有Node开发人员而您不必使用Azure即可从内容中受益。 所有点击诱饵的创建方式均不相同 (All click bait is not created equal) Good titles draw people in. They have to. The sheer volume of information that we consume daily requires you to say something to get peoples attention. 好的头衔吸引着人们。他们必须这么做。 我们每天消耗的大量信息需要您说些什么来引起人们的注意。 Unfortunately, people have abused this concept by optimizing for the Views or Read Percentage metric; putting turds behind a title designed just to get your click. 不幸的是人们通过优化“观看次数”或“阅读百分比”指标来滥用这一概念。 将草皮放在仅旨在获得点击的标题后面。 We call this, Clickbait. 我们称其为“ Clickbait”。 Clickbait is bad. Its bad because the title is salacious, but the content is weak. This is pure deception, and we hate it. Nobody likes being lied to. Thanks to people abusing titles for clicks, weve gotten to the point where any title which grabs your interest is considered clickbait. Except it isnt. Clickbait不好。 不好是因为标题很淫荡但内容很薄弱。 这纯粹是欺骗我们讨厌它。 没有人喜欢被骗。 由于人们滥用标题来获得点击因此到现在为止任何引起您兴趣的标题都被视为“点击诱饵”。 除非不是。 Your content is only as good as the title that it sits behind. If the title doesnt get people to stop and take notice, it really doesnt matter how good your content is, does it? As long as you are putting substance in your content, dont be afraid to bravely draw people in with strong titles. Of all the titles Ive come up with, here are some of my favorites... 您的内容仅取决于其标题。 如果标题没有引起人们的注意那么您的内容到底有多好不是吗 只要您在内容中添加实质内容就不要害怕勇敢地吸引具有强标题的人。 在我想出的所有标题中有一些我的最爱... Oauth has ruined everything Oauth毁了一切 Save 15% or more on car insurance by switching to plain JavaScript 改用纯JavaScript可以节省15或更多的汽车保险费用 How to increase your page size by 1500% with Vue and Webpack 如何使用Vue和Webpack将页面大小增加1500 You should never ever run Node.js in production. Maybe. 您永远不要在生产中运行Node.js。 也许。 The best CLI is the one you dont have to install 最好的CLI是无需安装的CLI So how do you write better headlines? In the first iteration of the freeCodeCamp style guide, Quincy recommended the CoSchedule Headline Analyzer tool. Ive used this site many many times. It helps you to write better titles by giving your headline a score. 那么您如何撰写更好的标题 在freeCodeCamp样式指南的第一版中Quincy建议使用CoSchedule标题分析器工具。 我已经多次使用该网站。 通过为标题提供一个“得分”可以帮助您编写更好的标题。 This tool can be a little frustrating to use. It will tell you that you need more common words or emotional phrases, but it doesnt tell you what those things are. Its a bit of an exercise, but Ive found the tool to be useful in so much as it forces me to create dozens of iterations of a title and I always end up with a better one than the one I started with. 使用该工具可能有点令人沮丧。 它会告诉您您需要更多的“常用”字词或“情感”短语但并不能告诉您这些东西是什么。 这是一个练习但是我发现该工具很有用因为它迫使我创建一个标题的几十个迭代而且我总是得到比开始时更好的标题。 For my last tip, I have no data. I have no charts to show you or stats to back me up. My last tip is just hard-learned from the trenches of life. 关于我的最后一条提示我没有数据。 我没有图表可以显示您也没有统计数据来支持我。 我的最后一个提示只是从生活的战hard中吸取的。 脆弱 (Be vulnerable) The psychologist Robert Glover once said, Human beings are attracted to each others rough edges. 心理学家罗伯特·格洛弗(Robert Glover)曾经说过“人类被彼此粗糙的边缘所吸引”。 One of the most engaging things you can do for your reader is to simply be you. If you dont understand something, say so. If a concept is confusing, point that out. If you are afraid to write about something because you think you might be doing it wrong, write it. Your honesty is what ultimately makes a terrific blog post. 您可以为读者做的最吸引人的事情之一就是成为您自己。 如果您听不懂请这样说。 如果一个概念令人困惑请指出。 如果您害怕写某事是因为您认为自己做错了请写下来。 您的诚实是最终使您撰写精彩博客文章的原因。 Put yourself out there. Show people how you solved a problem and ask them how they would do it. You are going to be wrong. All the time. Thats life. And the thing is, people love that. 把自己放在那里。 向人们展示您如何解决问题并询问他们如何解决。 你会错的。 每时每刻。 那就是生活。 事实是人们喜欢这一点。 One of the first articles that I wrote for CSS Tricks was covering a pretty simple issue in React where I needed some content to be dynamically rendered. I was new to React, so I wasnt sure how everyone else was doing it. 我为CSS Tricks撰写的第一篇文章之一涉及React中一个非常简单的问题其中我需要动态呈现一些内容。 我是React的新手所以我不确定其他人的表现如何。 So I asked people. 所以我问人 。 This article has more comments than any article I have ever written. It is not a long article. It does not provide any sort of revelation. It also exposes my naivety as a React developer. But more importantly, it connects with people. Why? Because everyone has things that they dont know that they think everyone else already knows. They are just waiting for someone to step out and say so. Once you do, they will too. 与我以前写过的任何文章相比本文的评论更多。 文章不长。 它不提供任何形式的启示。 这也暴露了我作为React开发人员的天真。 但更重要的是 它与人联系在一起 。 为什么 因为每个人都有他们不知道的东西他们认为其他人已经知道了。 他们只是在等待某人说出来。 一旦您这样做他们也会。 Yes, you are going to get the everyone knows this comments. But thats false. Everyone doesnt know it. After all, you didnt know. And that voice in your head that tells you that youre the only one? Thats your ego. In short, pride keeps you from being authentic, and that ultimately keeps you from connecting with your readers. 是的您将获得“每个人都知道这一点”的注释。 但这是错误的。 每个人都不知道。 毕竟您不知道。 而脑海里那种声音告诉你你是唯一的一个 那是你的自我。 简而言之骄傲会使您失去真实性最终使您无法与读者建立联系。 有趣和进攻之间的细线 (The fine line between being interesting and being offensive) A word of caution: there is a fine line between writing interesting content and just being a jerk. Its quite easy to swing from being insightful into just being mean. I should know. Ive done it. 请注意在编写有趣的内容与成为混蛋之间有一条很好的界限。 从有洞察力转变为卑鄙是很容易的。 我应该知道。 我做完了 If I say OAuth has ruined everything, I am taking shots at the people who created that spec. There is a thinking, feeling human on the other end of every technology you use. In the case of OAuth, the creator himself had already made worse statements it, so I felt comfortable that I wasnt simply smearing his work in public. 如果我说“ OAuth破坏了一切”那我就是对创建该规范的人开枪。 在您使用的每种技术的另一端都有一种思考感觉像人。 就OAuth而言创建者本人已经做出了更糟糕的陈述因此我感到安慰的是我并不仅仅是在公开场合涂抹他的作品。 Even still, I took a big risk doing that. Thats expected. You are going to have to assume some amount of risk to write great content, either because you are being vulnerable, because you are questioning the status quo, or because you are simply being honest. But you dont have to be a jerk. That part is optional and the internet is not exactly lacking in negative content. 即使如此我还是冒着很大的风险。 那是意料之中的。 您可能要冒一定的风险才能编写出色的内容要么是因为您处于脆弱状态要么是因为质疑现状要么是因为您只是诚实。 但是您不必是一个混蛋。 这部分是可选的互联网也不是完全缺少负面内容。 写在 (Write On) The most important thing of all is to just write. None of these tips are any good if you dont write anything. For a lot of people, thats the hardest part. Just know that the more you do it, the easier it gets. Its kind of like playing the guitar. 最重要的是写。 如果您什么都不写这些技巧都不是一件好事。 对于很多人来说这是最难的部分。 只要知道您做得越多它就越容易获得。 有点像弹吉他。 Ill leave you with this inspiration. This is Alexandr Misko. My guess is he didnt just pick up a guitar one day and play like this. It took a lot of practice. Writing is no different. If you do it enough, you might just become the Alexandr Misko of blogging. 我会给你这个灵感。 这是亚历山大·米斯科。 我的猜测是他不仅有一天会拾起吉他并像这样弹奏。 花了很多时间练习。 写作没有什么不同。 如果做得足够您可能会成为博客的Alexandr Misko。 翻译自: https://www.freecodecamp.org/news/what-500-blog-posts-taught-me-about-writing-great-articles/wp博客写文章500错误
