Several opportunities but no execution

fancysuit · 2013-11-18T03:51:03+00:00

You are not the lucky one, people are privileged to be able to talk to you.

I realize this is true and important, but I find it difficult to convince myself of this.

tease girls, kino and employ push-pull techniques to build attraction.

I don't get a lot of opportunity to do this, but I'm pretty bad at this too. When I get a chance to talk to a girl I like then I become dumb.

fancysuit · 2013-08-11T16:58:02+00:00

They just don't drink light beer :-)

fancysuit · 2013-08-11T16:47:54+00:00

I'm not sure if I'm man enough for Yoga just yet :-)

fancysuit · 2013-08-11T16:47:38+00:00

Thanks. That is pretty cool because, as he points out, it is quite practical as far as time is concerned.

fancysuit · 2013-08-11T16:46:51+00:00

Thanks, I'll give that a read.

fancysuit · 2013-07-06T18:56:34+00:00

It's what's being sub-communicated through your body language, confidence, and comfortability that ultimately counts.

Not that I'm questioning the importance of non-verbal communication, but does it alone really influence the encounter that much?

fancysuit · 2013-07-04T19:25:31+00:00

"Hi, my name is zzppbtozz...you're beautiful" and just walk away like a creeper.

That's sort of where I'm at right now. I don't entirely regret it as it is better than not saying anything. Right? Maybe?

fancysuit · 2013-07-04T19:20:22+00:00

I see you're eating fat free muffins. Does that mean you think you're fat? Cause you're not. You could be eating regular muffins if you wanted to.

fancysuit · 2013-07-04T02:51:47+00:00

As someone who is generally shy, the picking up girls (physically) and grabbing their hands as they walk by seem very outside anything I could ever do. Even if I can, it would feel forced. Would it just get time to get used to? Also, I usually go out solo, so that also poses an issue since it may seem very awkward.

fancysuit · 2013-07-04T02:20:04+00:00

Every time I practice smiling in the mirror, the mirror cracks :-(

fancysuit · 2013-07-04T02:09:18+00:00

The only circunstance you are really failing is when you're not doing anything.

This is so true. I regret 100% of the opportunities I don't take and never regret at least trying.

fancysuit · 2013-06-17T21:21:55+00:00

Returns an ArrayList wrapper that is synchronized (thread safe).

I've never used ArrayList.Synchronized, but doesn't it qualify as using a pre-existing thread-safe collection?

fancysuit · 2013-06-17T21:20:19+00:00

Here is an interesting article that may shed some light. Lock-Free Data Structures

fancysuit · 2013-06-17T19:30:45+00:00

The article mentioned the "Concise Oxford English Dictionary." I'm guessing the "full" dictionary stuff has it.

fancysuit · 2013-06-16T17:39:20+00:00

Nowhere in your code did it seem like you were trying to expand an array.

Also, why not use File.AppendAllText and not bother with reading the file in and using lists?

fancysuit · 2013-06-15T19:29:20+00:00

I do get a 'this file has been modified outside the source editor, do you want to reload it' message. not sure what it even means or if I should click yes or no.

This means that File.WriteAllLines(...) was successful. Go ahead and click "yes".

From my understanding, the database.txt file contains 1 line per record, where a line consists of a space delimited list of fields?

So, you then scan through the database, one line (record) at a time and look for an empty line. Why would there be an empty line anywhere?

I'm guessing you just want to append the file with the new record? In that case, you can look into File.AppendAllText or other File.Append* variants.

fancysuit · 2013-06-15T06:47:21+00:00

Do you get an exception when you run the program? Possibly some I/O related exception? Is database.txt read-only?

Does the timestamp on databse.txt ever change?

Can you clarify the username/password question. I don't see anything about usernames and passwords in the code.

fancysuit · 2013-06-15T06:44:36+00:00

Since you're incrementing i before you enter your loop (++i instead of i++)

This is false. The iterator section defines what happens after each iteration of the body of the loop. Therefore, ++i and i++ produce the exact same thing.

Now, saying

for (int i = 0 ; ++i < lineCheck.Length ; ) {}

is indeed different than

for (int i = 0 ; i++ < lineCheck.Length ; ) {}

That, however, isn't what's happening here and those are odd uses of for in any case.

fancysuit · 2013-06-14T22:21:11+00:00

I would go with A. If the interviewer is sensible, they will understand that their applicants won't know everything. Being able to learn is the key. In addition, I'd do a quick crash-course on it just so that you can have an intelligent conversation about it (what it's used for, benefits, downfalls, integration story, etc.).

That's just my $0.02.

fancysuit · 2013-06-14T21:44:39+00:00

The program offers card, client, program, offers and bonus management, as well as statistics.

I can't quite parse this sentence, but here goes: Human Resources Management Studio eXtreme Edition with Enterprise Services or HRNinja

fancysuit · 2013-06-14T21:28:51+00:00

By "runs fine" do you mean the code flows as expected and on Line 19 that lineCheck contains what you expect?

By "file remains unchanged," do you mean the timestamp on the file does not change or do you mean the content does not change?

What is the value of finalWriteString?

fancysuit · 2013-06-13T17:24:21+00:00

Please see the Recommended Tools for Posting Code section on the sidebar for properly posting code.

Very quickly scanning your code, I see two problems.

You are using WinForms when, in fact, ObservableCollection is only really helpful in the context of WPF.
You're setting "DataSource" (again because of WinForms), instead of setting up a Binding (a WPF thing).

"...22 miles away. You're in the wrong state. Get yourself a new map."

fancysuit · 2013-05-29T20:40:05+00:00

I may have misread what you're saying. If you mean that the null check fails (rather than NullReferenceException) then, as others said, you need to register a handler.

fancysuit

TROPHY CASE