blocks|key|1481013|text|我们没有全天候的工作人员，但我们有通宵运行的关键流程。我们创建了一个内部警报系统，用于通知我们严重的系统问题、失败的关键任务流程等。它使用文本到语音转换来创建描述性消息，然后连接到我们的自动拨号器，以呼叫适当的人员发送消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1481014|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|$]]

We aren't staffed 24x7 but we have critical processes that run throughout the night. We created an in-house alerts system to notify us of serious system issues, failed mission-critical processes, etc. It uses text-to-speech to create a descriptive message and then connects to our automated dialer to call the appropriate people with the message.

blocks|key|1696215|text|这算不上是黑客，但在当时，在我们速度很快的VAX11/730上，如果出了什么问题，我们的通宵进程就会在打印机上打印出文件"BLAMMO.TXT“。每天早上进门的第一站就是打印机。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1696216|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|$]]

Hardly a hack, but back in the day, on our speedy VAX 11/730, our overnight process would print the file "BLAMMO.TXT" on the printer if something went amiss. Every morning, the first stop was the printer when coming in.

blocks|key|1696248|text|我们有一个红绿灯，可以显示我们的日常构建是否成功，是否测试失败，或者根本没有构建。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1696249|此外，我们有一个灯条，当我们收到客户的上传时，它会亮起几秒钟。|1696250|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|$]]

We have a traffic-light that shows whether our daily build succeeds, has failed tests or simply doesn't build. 

Also, we have a light bar that lights up for a few seconds whenever we receive an upload from a customer.

blocks|key|1696325|text|我们团队中有一位开发人员不熟悉subversion冲突的概念。他推断，如果他只是删除了代码中所有奇怪的东西，然后单击resolve，那么一切都是正常的(即删除文件中的所有其他更改……)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1696326|不管怎么说，在第五次发生这种情况之后，也就是第五次我必须解释为什么我刚刚关闭的缺陷会重现时，我写了一个脚本。|1696327|对文件的更改将有所不同，以查看连续的签入是否删除了之前的所有更改，以及这些更改是否由匿名开发人员完成。|1696328|然后，它会向老板发送一封电子邮件，说明发生了什么，以及在签入过程中丢失了多少工作。|1696329|没有第7次发生。|1696330|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

We had one developer in our team who wasn't familiar with the concept of a subversion conflict. He deduced that if he simply deleted all that weird stuff in his code and clicked resolve that everything was ok (i.e. knocking out all the other changes in the file....)

Regardless to say, after the 5th time this occurred, and the 5th time that I had to explain why that defect that I just closed was reoccuring, I wrote a script.

It would diff for the changes to a file to see whether the consecutive checkin deleted all the previous changes and that they were done by the nameless developer.

It would then send an email to the boss with a description of what happened, and how much work was lost during the checkin.

There was no 7th occurrence.

blocks|key|1481244|text|回到我之前的工作，我们不得不审计许多表的数据更改(插入、更新和删除)。我们的支持人员必须能够搜索这些数据，以找到用户所做的更改。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1481245|已经变成半永久性的临时解决方案是存储每个非select查询。然而，这是一个大系统，表会以每天1.5+by的速度增长。|1481246|我想出的解决方案是创建一个脚本，该脚本为外部列表中的所有表创建适当的触发器，用于审计每个表、行、列、之前和之后、何时和谁，并将其存储在我们的新审计表中。这个表的大小大约是旧版本的10%25，并且存储了更多可用的数据。它使我们能够创建一个UI来搜索和查看对数据所做的每个更改，而不需要我们的支持团队或业务用户具备任何SQL知识。|1481247|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Back at my previous job, we had to audit many tables for data changes (inserts, updates and deletes). Our support crew had to be able to search through this data to find changes that users made.

The temporary solution that had become semi-permanent was to store each non-select query. However this was a large system, that the table would grow by about 1.5GB a day.

The solution I came up with was to create a script that for all tables in an external list, created the appropriate triggers that audit each table, row, column, before and after, when and by whom and store it in our new audit table. This table grew by about 10% the size of the older version and stored much more usable data. It enabled us to create a UI to search and view every change made to our data, without requiring any knowledge of SQL for our support team or business users.

blocks|key|1481304|text|在一家网页设计公司工作时，我配置了我们的开发服务器，这样我们就可以按子域名实时查看项目的工作副本。因此，如果你的名字是joe，并且你正在从事jetfuel项目，那么你可以转到joe.jetfuel.test-example.com，你可以在不提交的情况下立即看到你的更改。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1481305|这是一个使用子域名作为部分目录结构的简单黑客攻击。我们的htdocs路径看起来像这样的htdocs/tag/project。我们有一个脚本(你可以通过setup.test-example.com访问的php应用程序)，它会为你创建一个新的标记名，签出你想要的任何版本，并调用该项目的部署脚本。如果它成功了，它会把你转到新的子域。然后，您可以通过一个samba共享来处理这个新副本。|1481306|这对我们来说工作得很好，因为我们总是部署到相同的linux版本，并且我们的项目有简单的数据库要求。|1481307|我们这样做的最初原因是因为我们的开发人员在各种不同的平台上工作。除了修复这个平台问题之外，这对于查看更改和测试来说也是非常棒的。我们有各种各样的标签，从人名，主干版本，测试标签，一直到像jquery-menu-hack.jetfuel.test-example.com这样的原型|1481308|现在回过头来看，我想知道运行虚拟机会容易得多。|1481309|entityMap^0|2F|S|0|17|I|23|M|0|0|2L|15|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|X|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|11|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|O|$]]

Working at a web design company I configured our dev server so we could see a working copy of a project in real time by a sub domain name. So if your name was joe and you were working on project jetfuel you would go to <code>joe.jetfuel.test-example.com</code> and you could see your changes instantly without committing. 

This was a simple hack that used sub domain names as a partial directory structure. Our htdocs path looked like this <code>htdocs/tag/project</code>. We had a script (a php app that you would access by <code>setup.test-example.com</code>) that would create a new tag name for you and checkout whatever version you wanted and call the deploy script for that project. If it succeeded it would forward you to the new sub domain. You could then work on this new copy by a samba share.

This worked really well for us since we always deployed to the same linux build and our projects had simple database requirements.

Our original reason for doing this was because our developers worked on all kinds of different platforms. Besides fixing this platform problem this was awesome for viewing changes and testing. We had all kinds of tags ranging from peoples names, trunk versions, test tags, all the way to prototypes like <code>jquery-menu-hack.jetfuel.test-example.com</code>

Now that I look back I wonder how much easier it would have been to run virtual machines.

blocks|key|1481318|text|我们有一个开发人员在一个典型的ASP网站上工作，他不相信源代码控制。代码直接从他的机器传到了生产箱。这会导致更改丢失或无法恢复到稳定版本的问题。由于CruiseControl.Net具有监视目录的能力，因此我添加了一个项目，当文件被复制到生产环境中时，该项目会实际签入这些文件。完全背离了CC.Net的初衷，但我们没有丢失更多的代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1481319|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|$]]

We had a dev working on a classic ASP site that didn't believe in source control. The code went from his machine straight to the production box. This lead to issues with lost changes or the inability to revert back to a stable version. Since CruiseControl.Net has the ability to monitor a directory, I added a project that actually checked in files whenever they were copied to production. Completely backward from CC.Net's original intent, but we didn't lose any more code.

blocks|key|1481376|text|不完全是黑客，但有几个IT开发工作的必备条件：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1481377|如果您使用的是subversion，则必须使用CommitMonitor。(http://tools.tortoisesvn.net/CommitMonitor)它允许您监视svn存储库中的新提交&然后检查新提交。如果你想了解你的团队正在做的事情，那就太好了。特别是如果你有几个后辈需要注意的话。;)|offset|length|1481378|Rsnapshot+(http://www.rsnapshot.org/)也是无价的--在两年前，我们每四个小时就有一个完整的文件系统备份快照，而且每天都是如此。它就像文件系统的数据立方体！这带来的心灵的平静是纯粹的极乐。:)|1481379|entityMap|0|LINK|mutability|MUTABLE|url|http://tools.tortoisesvn.net/CommitMonitor|1|http://www.rsnapshot.org/^0|0|12|16|0|0|B|P|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

Not exactly hacks, but a couple of must-haves for IT dev work:

If you're using subversion, you've got to use CommitMonitor. (<a href="http://tools.tortoisesvn.net/CommitMonitor" rel="nofollow noreferrer">http://tools.tortoisesvn.net/CommitMonitor</a>) It lets you monitor svn repositories for new commits &amp; then review the new commits. Great if you're wanting to stay on top of what your team is doing. Particularly if you have a couple of juniors that need to be watched. ;) 

Rsnapshot (<a href="http://www.rsnapshot.org/" rel="nofollow noreferrer">http://www.rsnapshot.org/</a>) is also invaluable - we have complete backup snapshots of our entire filesystem every four hours going back 2 years, and every day beyond that. It's like a data cube for your filesystem! The peace of mind this gives is pure bliss. :)

blocks|key|1481452|text|放在一个检查bug注释的pre-commit钩子中，引用一个打开的bug，分配给执行签入的用户。(SCMBug可以做到这一点)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1481453|然后，为了让生活真正有趣，请检查评论的拼写！！提交注释和代码中的注释。(拼写是我的伙伴)|1481454|通过设置为compayn标准的代码格式化程序运行代码；并将其与原始代码进行比较:如果它不是公司官方格式:拒绝提交。|1481455|使用单元测试构建进行覆盖率测试。|1481456|将导致的所有错误/错误通过电子邮件发送给开发团队。|1481457|我漏掉了开发人员的名字。他们知道是他们干的。|1481458|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

Put in a pre-commit hook that checks the bug comment refers to an open bug, assigned to the user doing the checkin. (SCMBug can do this).

Then to make life REALLY interesting, spell check the comments!!
The commit comment, and the one in the code. (spell is my buddy)

Run the code through a code formatter set to compayn standard; and diff it to the original: if it's not in company offical format: reject the commit. 

Do a coverage test with the unit test build.

Email all mistakes/errors caused to the development team.

I left OUT the name of the developer. They know they did it.

blocks|key|1481526|text|回到大约9年前的dotCom时代，我不得不在两个不同的位置之间破解故障转移系统。我们有一个时髦的设置，有一个powerbuilder前端网站和powerbuilder管理工具。数据存储在MSSQL7.0中。ask服务器使用IPX与SQL服务器通信(不要问)。无论如何，我有责任提出一个故障转移计划。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1481527|我最终破解了一些linux机器，并让它们运行我们的外部DNS。每个位置一个。我们有一个带webserver的远程站点，sql+server让SQL事务复制通过128k+ISDN+IPX连接工作。然后在我们的生产站点构建了一个监控工具，将数据包发送到各种上游网络切换。如果我们在主站点上遇到超过20%25的宕机，监控工具就会在Debian机器上运行perl脚本来更改DNS并指向我们的第二个站点。我们的次要DNS和监控站有一个心跳。它将复制记录，除非它丢失了两个连接，然后它将转到将DNS指向备份位置。|1481528|主站点将在主位置关闭SQL+server以中断复制。使用128k+ISDN+IPX连接实现自动站点到站点故障切换:)|1481529|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Back in the dotCom days about 9 years ago, I had to hack a failover system between two different locations. We had a funky setup with a powerbuilder front end website, and powerbuilder managment tool. Data was stored in MSSQL 7.0. The webservers used IPX to communicate to the SQL Servers (don't ask). Anyway, I was responsbile for coming up with a failover plan. 

I ended up hacking together some linux boxes, and had them run our external DNS. One at each location. We had a remote site w/ webserver, and sql server I got SQL transaction replication working over a 128k ISDN IPX connection (of all things). Then built a monitoring tool at our production site to send packets out to various upstream network handoffs. If we experienced more than 20% outage the primary site, the monitoring tool ran a perl script on the Debian box to change DNS and point to our 2ndary. Our secondary had a heartbeat w/ our primary DNS, and monitoring station. It would duplicate records unless it lost both connections then it would roll over to pointing DNS to backup location.

The primary site would shut down the SQL server at the primary location to break replication. Automated site to site failover using 128k ISDN IPX connection :)

blocks|key|1696775|text|这是在较低的级别，但我相当自豪的是，我编写了一个make文件，用于为我的研究编译代码。它只需要提供源文件名和头文件名，这样就可以自己处理其余的事情(尽管它确实做了一个假设，即您不会将任何头文件编译成对象，只有源文件会被编译)。其他缺点是它依赖于GNU+make程序的第二个扩展特性，所以我不知道它是否适用于其他make程序。此外，所使用的编译器需要支持类似于gcc的-MM特性。在这里，我希望没有人嘲笑它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1696776|-include+prereqs.mk
HEADERS=$(SRC_DIR)/gs_lib.h+$(SRC_DIR)/gs_structs.h
SOURCES=$(SRC_DIR)/main.cpp+$(SRC_DIR)/gs_lib.cpp
OBJECTS=$(patsubst+$(SRC_DIR)/%25.cpp,$(OBJ_DIR)/%25.o,$(SOURCES))

release:+FLAGS=$(GEN_FLAGS)$(OPT_FLAGS)
release:+$(OBJECTS)+prereqs.mk
++++$(CXX)+$(FLAGS)+$(LINKER_FLAGS)+$(OUTPUT_FLAG)+$(EXECUTABLE)+$(OBJECTS)

prereqs.mk:+$(SOURCES)+$(HEADERS)
++++$(CXX)+$(DIR_FLAGS)+$(MAKE_FLAG)+$(SOURCES)+%7C+sed+'s,$[abcdefghijklmnopqrstuvwxyz_]*$.o:,\1=+\\\n,'+>+$@

.SECONDEXPANSION:
$(OBJECTS):+$$($$(patsubst+$(OBJ_DIR)/%25.o,%25,$$@))
++++$(CXX)+$(FLAGS)+$(NO_LINK_FLAG)+$(OUTPUT_FLAG)+$@+$(patsubst+$(OBJ_DIR)/%25.o,$(SRC_DIR)/%25.cpp,$@)|code-block|syntax|javascript|1696777|显然，我省略了许多变量的定义，但我认为它让人明白了。|1696778|由于我的编码工具和风格与此脚本的要求兼容，因此我喜欢使用它。我要做的就是添加(a)一段新的源代码，把它的名字添加到适当的变量中，剩下的就可以处理了。|1696779|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

This is at a lesser level, but I am fairly proud of a make file I wrote for compiling code for my research. It only needs to be given your source and header file names that can take care of the rest all by itself (though it does make the one assumption that you will not be compiling any header files into objects, only source files get compiled). The other downsides are the fact that it relies on the GNU make program's second expansion feature, so I don't know if it works on other make programs. Additionally the compiler used needs to support something similar to gcc's -MM feature. Here is hoping that no one laughs at it.

<pre><code>-include prereqs.mk
HEADERS=$(SRC_DIR)/gs_lib.h $(SRC_DIR)/gs_structs.h
SOURCES=$(SRC_DIR)/main.cpp $(SRC_DIR)/gs_lib.cpp
OBJECTS=$(patsubst $(SRC_DIR)/%.cpp,$(OBJ_DIR)/%.o,$(SOURCES))

release: FLAGS=$(GEN_FLAGS)$(OPT_FLAGS)
release: $(OBJECTS) prereqs.mk
 $(CXX) $(FLAGS) $(LINKER_FLAGS) $(OUTPUT_FLAG) $(EXECUTABLE) $(OBJECTS)

prereqs.mk: $(SOURCES) $(HEADERS)
 $(CXX) $(DIR_FLAGS) $(MAKE_FLAG) $(SOURCES) | sed 's,$[abcdefghijklmnopqrstuvwxyz_]*$.o:,\1= \\\n,' &gt; $@

.SECONDEXPANSION:
$(OBJECTS): $$($$(patsubst $(OBJ_DIR)/%.o,%,$$@))
 $(CXX) $(FLAGS) $(NO_LINK_FLAG) $(OUTPUT_FLAG) $@ $(patsubst $(OBJ_DIR)/%.o,$(SRC_DIR)/%.cpp,$@)
</code></pre>

Obviously I dropped the definition of a number of variables, but I think it gets the idea across. 
Since my coding tools and style are compatible with the requirements of this script I like to use it. All I need to do to add (a) new piece(s) of source code is add its name(s) to the appropriate variable and the rest is taken care of.

blocks|key|1696847|text|我们有许多项目的Twitter账户，这些项目在Twitter上发布提交消息、构建通知、失败的单元测试、部署、bug跟踪活动-任何与项目相关的事件。运行像Twitter+Gwibber这样的客户端(它为每个新状态显示一个弹出窗口)是与您感兴趣的项目的活动保持联系的一种很好的方式。使用Twitter是很好的，因为你可以利用所有的第三方应用程序--比如iPhone客户端。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1696848|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|$]]

We have Twitter accounts for many projects which tweet things like commit messages, notices from builds, failed unit tests, deployments, bug tracking activity - any kind of event associated with the project. Running a client like Twitter Gwibber (which displays a pop-up for each new status) is a great way to stay in touch with the activity on the projects you are interested. Using Twitter is good as you can take advantage of all the 3rd party apps - such as the iPhone clients.

blocks|key|1481684|text|早在1993年，当源代码控制系统非常昂贵和笨拙的时候，我工作过的公司有一个内部的源代码控制，是用4DOS脚本构建的。它不像大多数当前的源码控制系统那样软化，例如，它没有分支或集成，但它完成了支持修订历史、签出/签入和基本冲突解决的基本工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1481685|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 in the 1993, when source control systems were really expensive and unwieldy, the company I worked about had an in-house source control built as 4DOS scripts. It wasn't as sofisticated as most current source control systems, for example it didn't have branching or integrates, but it did the basic job of supporting revisions history, checkout/checkin and rudimentary conflict resolution.

blocks|key|1696925|text|为具有纹理/图像绝对路径的VRML/3D模型文件添加提交钩子检查。f:/maya/my-textures/newproject/xxxx.png不属于服务器。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1696926|entityMap^0|X|13|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Add commit-hook check for VRML/3d-model files with absolute path to textures/images. <code>f:/maya/my-textures/newproject/xxxx.png</code> just doesn't belong on the server.

Lots of people have things that their systems do for them or for their teams. Source control post-commit hooks are a standard example: have an automated build system that checks out the latest source, compiles, tests, and packages it is a back-office hack that most of us probably use.

What other cool things have you done?

Best IT/back-office system hacks?

数据存储

单元测试

文件系统

数据库

服务器

虚拟机

编译器

Debian

许多人都有他们的系统为他们或他们的团队做的事情。源代码控制提交后挂钩就是一个标准的例子:拥有一个自动化的构建系统来检查最新的源代码、编译、测试和打包，这是我们大多数人可能会使用的后台技巧。你还做过其他很酷的事情吗？

问最好的IT/后台系统黑客？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问最好的IT/后台系统黑客？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问最好的IT/后台系统黑客？
EN