SitePoint的一年

Today marks the one year anniversary of my editing job at SitePoint.

今天是我在SitePoint编辑工作一周年。

SitePoint的一年

It sure went by fast – in fact, I was genuinely surprised when LinkedIn “likes” started popping up. In this short post, I’d like to take a moment to reflect on the past 365 days, and share with you what I’ve learned and how things changed.

它肯定飞速发展-实际上,当LinkedIn“点赞”开始出现时,我真的感到非常惊讶。 在这篇简短的文章中,我想花点时间回顾一下过去365天,并与您分享我学到的东西以及情况如何变化。

旧世界的混乱 (Chaos in the Old World)

When I first took the job and stepped into Tim’s shoes, I’m not going to lie – I was overwhelmed. With a big and chaotic author roster, I had very little time to get familiar with the writers, the approach to accepting drafts, the editing process and the aspect of communication with both HQ and the author pool.

当我刚开始工作并踏上蒂姆的鞋子时 ,我不会撒谎–我不知所措。 有了庞大而混乱的作者花名册,我几乎没有时间熟悉作家,接受草稿的方法,编辑过程以及与总部和作者库的交流方面。

Vagrant still not having been a tool as popular as it is and Docker basically not existing yet made things more difficult to test – every code sample came with its own prerequisites, and it was more work than my home Linux playbox could handle, sometimes reinstalling the PHP development environment several times per day. My machine looked messier every day.

Vagrant仍然没有像现在这样流行,并且Docker基本上不存在,但使测试变得更加困难–每个代码示例都具有自己的先决条件,而且工作量超过了我的家庭Linux播放器所能处理的工作,有时会重新安装PHP开发环境每天几次。 我的机器每天看起来都比较混乱。

SitePoint的一年

To top it all off, a huge transition happened at SitePoint at the time. The site Timothy had been editing for was called PhpMaster, and was a separate entity. Some time around my arrival, PhpMaster was welcomed back into the SitePoint fold as a sub-channel of the main site and underwent a serious rebranding, de-naming, and restructuring, along with a structural shift in HQ. Amid all this chaos, the channel was expected to do well and to continue operating seamlessly.

最重要的是,当时SitePoint发生了巨大的转变。 蒂莫西(Timothy)一直在为其编辑的站点称为PhpMaster,它是一个单独的实体。 在我到达的某个时候,PhpMaster作为主要站点的子渠道重新回到SitePoint折叠中,并进行了认真的品牌重命名,取消命名和重组,以及总部的结构性转变。 在所有这些混乱之中,该渠道有望表现良好,并继续无缝运行。

新订单 (Order in the New)

One year later, all traces of PhpMaster are gone, but not forgotten.

一年后,PhpMaster的所有痕迹消失了,但没有被遗忘。

Vagrant and Docker have allowed us to not only test all the demo code in articles efficiently, safely and easily – these technologies also helped us make a common environment approachable to everyone via Homestead Improved. With this Vagrant setup, every reader can have a setup ready for following along with a tutorial in minutes, without harming their current PHP development environment with additional library and extension installations.

Vagrant和Docker不仅使我们能够高效,安全和轻松地测试文章中的所有演示代码,而且这些技术还帮助我们通过Homestead Improvementd使每个人都可以使用的通用环境。 使用此Vagrant设置,每个读者都可以在几分钟之内准备好要跟随教程的设置,而又不会因安装其他库和扩展而损害其当前PHP开发环境。

We’ve transitioned to Trello for project management, and while still somewhat chaotic due to the sheer size of the author roster, it’s infinitely better than keeping everything in inboxes and spreadsheets. Communication now mostly happens in Slack instead of email, and everything is that much smoother.

我们已经过渡到Trello进行项目管理,尽管由于作者名册庞大而有些混乱,但它比将所有内容都保留在收件箱和电子表格中要好得多。 现在,沟通大多在Slack而不是电子邮件中进行,一切都变得更加顺畅。

On the author layer, almost all editors transitioned to MarkDown drafts exclusively, which now allows us all to stay in sync and easily edit each other’s articles, while at the same time getting standardized input from our writers, allowing for faster edits and a smoother workflow, along with automatic exports into HTML for publication.

在作者层,几乎所有编辑者都只转换为MarkDown草稿,这使我们所有人都可以保持同步并轻松编辑彼此的文章,同时从我们的作家那里获得标准化的输入,从而实现更快的编辑和更流畅的工作流程,以及自动导出为HTML进行发布。

SitePoint的一年

The new channel is far from a futuristic efficiency machine, but with the growth it’s seen over the past year, things absolutely must flow as smoothly as possible. Seeing the competition try to copy our approaches more and more was flattering and assured us of the course we were on.

新的渠道远非未来的效率机器,但随着过去一年的增长,绝对必须尽可能顺利地进行。 看到比赛试图越来越多地模仿我们的方法,这很受宠若惊,并向我们保证了前进的道路。

我学到了什么 (What I’ve Learned)

With an excellent starting point set into place by Tim and the absolutely awesome guidance of Ophelie Lechat, my boss and mentor who came into her position a bit before I started at SitePoint, my progress was further accelerated with the added help of some ridiculously qualified people. People like Ricky Onsman, who left us to pursue other endeavors a couple months in, Louis Lazaris, Adam Roberts and others I frequently communicate with have all made becoming fluent with the process that much easier.

蒂姆(Tim)设定了一个很好的起点,而我的上司和导师Ophelie Lechat在我加入SitePoint之前就担任了她的职位,他的指导非常出色 ,在一些荒谬的合格人员的帮助下,我的进步得到了进一步的加速。 像Ricky Onsman这样的人离开了我们几个月来从事其他工作, Louis LazarisAdam Roberts以及我经常与之交流的其他人都使流利地简化了这一过程。

I’ve learned to treat authors as peers, not employees. I’ve learned what it’s like to be on the editing side, and finally realized what took Tim so long with some of the edits back when I was a writer :) I’ve learned how to properly test all the code that’s sent my way, and I’ve learned I hate WordPress more than any other software in the world.

我学会了将作者视为同行,而不是员工。 我已经了解了在编辑方面的感觉,最后意识到当我还是一名作家时,Tim花了这么长时间进行了一些编辑:)我已经学会了如何正确测试发送给我的所有代码,而且我了解到我比世界上任何其他软件更讨厌WordPress。

I’ve learned the tech industry is still ridiculously male-oriented, but I’ve also learned stereotypically feminist approaches to solve this problem do more harm than good.

我了解到科技行业仍然是荒谬的面向男性 ,但我也了解到刻板的女权主义方法解决这个问题弊大于利。

Most importantly, I’ve learned that I still have a lot to learn. In communication, community management, efficiency, work ethics, planning and structuring my time – all crucial to a job well done.

最重要的是,我了解到我还有很多东西要学。 在沟通,社区管理,效率,职业道德,计划和安排我的时间方面,所有这些对于做好工作都是至关重要的。

While the editing job has reduced my coding time significantly, I can honestly say I enjoy it wholeheartedly. I do miss coding, but what little coding I do for personal projects and pleasure is thoroughly enjoyable and relaxing, unlike the traditional coding we’re used to – with looming deadlines and screaming bosses overhead.

虽然编辑工作大大减少了我的编码时间,但老实说我可以全心全意地享受它。 我确实很想念编码,但是我为个人项目和娱乐所做的很少编码是完全令人愉悦和轻松的,这与我们习惯的传统编码不同-迫在眉睫的截止日期和尖叫的老板开销。

Finally, I’ve learned that exposure matters a lot. I always made sure my online persona exposed only the aspects of my life I’m comfortable with being exposed, and that my online presence stay professional and cordial (if somewhat ranty). What I didn’t know, however, was how much of an impact working for a high profile online magazine would have – particularly in terms of being recognized (either as friend or foe) in certain groups, and in being invited to speak at conferences purely due to writing and open source work – which brings me to the next section.

最后,我了解到曝光非常重要。 我始终确保自己的在线角色只暴露自己对生活感到满意的各个方面,并且我的在线形象保持专业和诚恳(如果有些担保)。 但是,我不知道为一本高知名度的在线杂志工作会产生多大的影响,尤其是在某些团体中被(朋友或仇敌)认可以及被邀请在会议上发言纯粹是由于编写和开放源代码的工作–这使我进入下一部分。

加入我们? (Join us?)

The author roster has grown several times its size, and still continues to do so. If you’re interested in growing the online aspect of your life and career, and if you’d like to get more in tune with the PHP community at large, please consider joining us. We’ve got topics for all levels of experience and comfort, and there’s no better way to grow your personal brand and show various parties where your expertise lies.

作者花名册的规模增长了数倍,并且仍在继续增长。 如果您对发展自己的职业和生活中的在线方面感兴趣,并且希望与整个PHP社区取得更多联系,请考虑加入我们。 我们提供了有关所有级别的体验和舒适度的主题,没有更好的方法来发展您的个人品牌并向各方展示您的专业知识所在。

The channel has grown significantly in the past year, and having experienced both the awe inspiring power of social media, and both the horrible burns and great successes of content sharing on Reddit-like sites, we’re stepping into year two with new, interesting findings and more fertile ground to grow on. The publication schedule has expanded and we’re in need of authors more than ever.

在过去的一年中,该频道取得了巨大的发展,并经历了社交媒体的震撼人心的力量,以及在Reddit之类的网站上分享内容的恐怖燃烧和巨大成功,我们正以崭新的,有趣的方式迈入第二年调查结果和更广阔的沃土。 出版时间表已经扩大,我们比以往任何时候都更需要作者。

Get in touch if you’d like to know more, or come to my ZgPHP and ForumPHP talks.

如果您想了解更多信息,请与我们联系 ,或者参加我的ZgPHPForumPHP讲座。

Here’s to a successful first year and to, hopefully, many more! Cheers!

这是成功的第一年,希望还有更多! 干杯!

翻译自: https://www.sitepoint.com/year-sitepoint/