公开征求不信春哥也不信曾哥考试也能不挂科的方法

Twitter上有人说信谷歌——8过目前为止没听到过“信谷歌，不挂科”的说法，也没有实例能够证明这个原则，所以求证

嘛，今天最惨烈的1/4考完了，明天还有3/4。。。。。。两个微积分，还有一个振动·热力学。。。。。。

于是，目前的打算——早点睡觉，明天一早起床到教室复习去=w=

Author: 星野恵瑠

Mac user, Niji-Ota, Chinese, Now working in Japan at MAGES. Inc., Future's aim is that one day my name can be listed in Wikipedia

22 thoughts on “公开征求不信春哥也不信曾哥考试也能不挂科的方法”

  9. 看你上次在推上貌似对秀吉很有兴趣

    所以就找到一个秀吉77MB贴图下载：http://is.gd/7JmK4

    呃，于是就在我的新Blog里贴出来了。。。

    是RF盘跟纳米盘下载。。。

    Reply

  10. @A.L.:
    同意……上次俺们寝室长的哥哥专业英语就是QQ拍照传过来，然后我码字，最后谷歌童鞋翻译……oh~yeah~
    信谷歌，英语不挂科～

    Reply

  12. This school computer can not show and type Chinese, so i can only translate your post to the English words, but Google sucks, frankly i do not understand what google translate said…sian na…

    Reply

  16. @iBoluo:
    求证实 (……)

    @Never summer:
    I said, i’m looking for something that when you believe in it, you’ll pass the exam safely, except brother-chun and brother-zeng (;;)

    @Firm:
    拜访？老师？偶们工学伦理才讲了作为工学者不能行贿受贿 (……)

    @怡红公子:
    问题是英语和日语是偶唯一不可能挂的两科 (……)

    Reply

  19. @Lovee:
    啊哈……咱只是这样讲讲么……
    说道受贿，我上次有个网友跟我说他都是直接向老师要答案然后带进考场抄的，囧……
    事实上，最安全的方法还是好好复习……

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks: 

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax

(;;) (:D) (!!!!) (……) (^o^;) (==) (OoO) (=v=o) more »Note: Commenter is allowed to use '@User+blank' to automatically notify your reply to other commenter. e.g, if ABC is one of commenter of this post, then write '@ABC '(exclude ') will automatically send your comment to ABC. Using '@all ' to notify all previous commenters. Be sure that the value of User should exactly match with commenter's name (case sensitive).