Looks like he had a very bad appraisal this year.. Fun fact : the coming year would be too :)
On Thu, 16 Apr 2020 at 12:07, Qi Kang <miraisen...@126.com> wrote: > Well man, check your attitude, you’re way over the line > > > On Apr 16, 2020, at 13:26, jane thorpe <janethor...@aol.com.INVALID> > wrote: > > F*U*C*K O*F*F > C*U*N*T*S > > > ------------------------------ > On Thursday, 16 April 2020 Kelvin Qin <qykx2...@126.com> wrote: > > No wonder I said why I can't understand what the mail expresses, it feels > like a joke…… > > > > > > 在 2020-04-16 02:28:49，seemanto.ba...@nomura.com.INVALID 写道： > > Have we been tricked by a bot ? > > > *From:* Matt Smith <matt.smith...@gmail.com> > *Sent:* Wednesday, April 15, 2020 2:23 PM > *To:* jane thorpe > *Cc:* dh.lo...@gmail.com; user@spark.apache.org; janethor...@aol.com; > em...@yeikel.com > *Subject:* Re: Going it alone. > > > *CAUTION EXTERNAL EMAIL:* DO NOT CLICK ON LINKS OR OPEN ATTACHMENTS THAT > ARE UNEXPECTED OR SENT FROM UNKNOWN SENDERS. IF IN DOUBT REPORT TO SPAM > SUBMISSIONS. > > This is so entertaining. > > > 1. Ask for help > > 2. Compare those you need help from to a lower order primate. > > 3. Claim you provided information you did not > > 4. Explain that providing any information would be "too revealing" > > 5. ??? > > > Can't wait to hear what comes next, but please keep it up. This is a > bright spot in my day. > > > > On Tue, Apr 14, 2020 at 4:47 PM jane thorpe <janethor...@aol.com.invalid> > wrote: > > I did write a long email in response to you. > But then I deleted it because I felt it would be too revealing. > > > > > ------------------------------ > > On Tuesday, 14 April 2020 David Hesson <dh.lo...@gmail.com> wrote: > > I want to know if Spark is headed in my direction. > > You are implying Spark could be. > > > > What direction are you headed in, exactly? I don't feel as if anything > were implied when you were asked for use cases or what problem you are > solving. You were asked to identify some use cases, of which you don't > appear to have any. > > > On Tue, Apr 14, 2020 at 4:49 PM jane thorpe <janethor...@aol.com.invalid> > wrote: > > That's what I want to know, Use Cases. > I am looking for direction as I described and I want to know if Spark is > headed in my direction. > > You are implying Spark could be. > > So tell me about the USE CASES and I'll do the rest. > ------------------------------ > > On Tuesday, 14 April 2020 yeikel valdes <em...@yeikel.com> wrote: > > It depends on your use case. What are you trying to solve? > > > > ---- On Tue, 14 Apr 2020 15:36:50 -0400 *janethor...@aol.com.INVALID > <janethor...@aol.com.INVALID> *wrote ---- > > Hi, > > I consider myself to be quite good in Software Development especially > using frameworks. > > I like to get my hands dirty. I have spent the last few months > understanding modern frameworks and architectures. > > I am looking to invest my energy in a product where I don't have to > relying on the monkeys which occupy this space we call software > development. > > I have found one that meets my requirements. > > Would Apache Spark be a good Tool for me or do I need to be a member of a > team to develop products using Apache Spark ? > > > > > > PLEASE READ: This message is for the named person's use only. It may > contain confidential, proprietary or legally privileged information. No > confidentiality or privilege is waived or lost by any mistransmission. If > you receive this message in error, please delete it and all copies from > your system, destroy any hard copies and notify the sender. You must not, > directly or indirectly, use, disclose, distribute, print, or copy any part > of this message if you are not the intended recipient. Nomura Holding > America Inc., Nomura Securities International, Inc, and their respective > subsidiaries each reserve the right to monitor all e-mail communications > through its networks. Any views expressed in this message are those of the > individual sender, except where the message states otherwise and the sender > is authorized to state the views of such entity. Unless otherwise stated, > any pricing information in this message is indicative only, is subject to > change and does not constitute an offer to deal at any price quoted. Any > reference to the terms of executed transactions should be treated as > preliminary only and subject to our formal written confirmation. > > >
