|
I had a job interview for a job I didn't get but very much wanted. I was asked the dreaded question "Where do you see yourself in 5 years time?"
I'm debating whether I should phone them up and give them an update?
|
|
|
|
|
 
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
What stop you?
In Word you can only store 2 bytes. That is why I use Writer.
|
|
|
|
|
Well...the worse that can happen is they slam down the phone on you.
The best is the position is still open... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Pom Pey wrote: "Where do you see yourself in 5 years time?"
A terrible interview question usually indicating lack of experience on the part of the interviewer. 
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Pom Pey wrote: Where do you see yourself in 5 years time?
Don't say "doing your wife"[^]. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
"In a mirror, same as I did this morning" probably doesn't work either... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Where do you see yourself in 5 years time?
Celebrating the 5 year anniversary of you asking me that question.
- Mitch Hedberg
|
|
|
|
|
Send them a card, they will love it
|
|
|
|
|
Brilliant.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
That's a good one! 
Did you told them about the caiman islands?! 
|
|
|
|
|
I just finished MVVM for beginners!
Article is pending: MVVM for beginners[^]
If anyone want to give feedback or authorise it!
Too tired for tonight.. serializer will come tomorrow now...
|
|
|
|
|
For next time you may post such things here: Article Writing Discussion Boards[^]
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Ha! yes! good point! 
|
|
|
|
|
I just reported it 'cus you're begging... 
veni bibi saltavi
|
|
|
|
|
|
Thank you for this.
A first Trial from my side; I suggest you to download the source and try to build the Project. For me it ends in 13 Errors. Several times "PropertyChanged?.Invoke ..." and others (VS 2012 Express).
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Oh no! 
checking that now...
|
|
|
|
|
Got it!
I am using some C#... err.., 5? 6? 4? (kind of confused) functionality.
The nullable invocation parameter
a?.b
I am also using CallerMemberNameAttribute which came with .NET 4.5 I think, and reduce many errors....
(hence I want to show that I use it as a good tip for people to follow!)
All of that to say it work for me, but I am using VS2015 and the latest version of C#....
mm... not to sure how to go about that... VS2015 is free after all!
|
|
|
|
|
There is nothing wrong using a specific version for your sample of VS and/or .NET - you should however state it, so those have not would now...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
OK, just updated the Introduction by stating that VS2015 is needed, and why.
It will get published when it is approved...
Thanks for feedback!
|
|
|
|
|
Thank you for your Feedback. I'm just on installing VS Community 2015 and take an exercise on these new features
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Excellent!
|
|
|
|
|
IMHO, you should use compiler directives and include code for the various versions of DotNet when calling NotifyPropertyChanged is concerned, or at least put a note in the article that describes the changes that are required if you use something older than .Net 5...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
That's a doozy!
I am trying to write the most simplistic MVVM sample that can be written and explained.
It just so happen that C# 6 + .NET4.5 added some feature which do help write simpler code.
Getting bog down into perfecting the implementation or explaining the fine difference between C# 1,2,3,4,5,6, WinForm, WPF, XAML, .NET3, .NET4, .NET4.5, .NET4.6 is completely out of scope for my article!
Now I can understand that if you don't know the null coalesce article from C# 6 (a?.b) you could be paralysed by fear or doubt!
After all complaints I decided to add an introductory warning about the requirements, as well as a link to this C# 6 syntax feature: Null-conditional Operators (C# and Visual Basic)[^] (pending moderator approval)
This is as far as I will go into being diverted from my goal of simplistic sample.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
