|
|
You missed this:
Quote: If it is not considered as spam or whatever i would insert what i wrote so far
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
How about basic understanding of German language as "nice to have"
cheers,
Super
------------------------------------------
Too much of good is bad,mix some evil in it
|
|
|
|
|
Good point ! I totally forgot about that
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
OT. What is Qualification 1?
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
That is something i don't know, so it's a placeholder to remind me. What should be the qualifications for such a job?
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
How about advanced knowledge of Object Orientated Programming principles for starters.
if (Object.DividedByZero == true) { Universe.Implode(); }
|
|
|
|
|
i think i'll add that! I thought this would be included in c# but thanks for the hint
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
It's been my experience that you only need basic OOP knowledge to write C# code but if you're going to write WPF, you really need to know your stuff when it comes to polymorphism, abstraction and other more advanced principles such as lambda expressions, multi-threading, and how to properly use the Dispatcher.
if (Object.DividedByZero == true) { Universe.Implode(); }
|
|
|
|
|
I see you are right
Thanks for that
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
It is highly depends on your company...
1. CS from University or College
2. Lesser CS related degree from College
3. Some specific courses/certifications (like Microsoft certifications)
4. Proven knowledge via samples/recommendations...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Well we don't need a highly trained super guy, i guess a fullfilled apprenticeship might fit. Since i really don't know the pay for this person and i don't know what a good it guy studied or with education costs down in Bratislava i am not sure what would fit best.
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
You missed "Family ownership of brewery or distillery will be a distinct advantage"
veni bibi saltavi
|
|
|
|
|
But only if they produce Gin or Whisky
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Looks good to me
It's short and to the point - I take it you are also going to devise a practical exam for before or at the interview?
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
GuyThiebaut wrote: you are also going to devise a practical exam for before or at the interview?
We thought about something like that, a small task to programm something so we can see how this guy codes and solves problems
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
SERIOUS PART
You should write somewhere what the company will pay, the working hours, benefits...
If there will be the need to travel...
WPF / Win Forms ... there it is not clear if it is a requirement or a plus.
The clearer the better in terms of filtering initially.
But afterwards, prepare a good interview, when I interviewed candidates usually I read the resume with them and commented it, then I presented the company briefly and the kind of job and how it is to work with us, afterwards, asked for samples or previous works or, as I mostly took guys and girls without previous experience, I tried to see how they were answering the questions and how fluent the interview was...
Then the first 15 days I made a kind of exam that allowed me to be sure that they were not cheating. It was not important to solve all the issues, but at least I was able to see how they worked them.
JOKE PART
You should ask for 20 years of C# experience as minimum.
Not only English, you will want some extra languages: Catalan is a must!
Capability to travel around a 90% of the time.
Overnights not paid.
...
Good luck.
|
|
|
|
|
Joan Murt wrote: You should write somewhere what the company will pay, the working hours, benefits...
If there will be the need to travel...
As i am just doing the job my boss should do i actually don't know what he's getting paid, maybe 2400-3000€ a month? i can just guess. Same goes for the working hours, i expect 40 a week. Travelling is in the role description
Joan Murt wrote: WPF / Win Forms ... there it is not clear if it is a requirement or a plus.
I'll clarify that, thanks !
Thanks for the insights of your approach on interviews, i'll keep that in mind and prepare my self
Joan Murt wrote: JOKE PART
You should ask for 20 years of C# experience as minimum.
Something serious about that, is it wrong to ask for X Years of experience? I always see some ads ppl want 5 y o e but the guy should be like 18 years old. Should i just write experience without the years?
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
HobbyProggy wrote: Something serious about that, is it wrong to ask for X Years of experience? I always see some ads ppl want 5 y o e but the guy should be like 18 years old. Should i just write experience without the years?
No it isn't, you can do that, the joke was about asking for more years of experience than the amount of years the technology has been there...
Usually it is not legal to ask for some age or gender, but you can ask for some years of experience and therefore it won't be possible to receive people younger than X, and of course, if they have been working with that technology for a certain amount of time this is a plus as they will know more on that than what is learnt studying.
|
|
|
|
|
More than having a lot of requirements it is unavoidable that your new co-worker is trustworthy, flexible and is capable of aquiring new knowledge.
You wont find a perfect match (or only a at high salary), so it is better hire someone who will and can learnt it.
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
I wanna thank all of you for your answers and insights, i guess now i can hand it to my boss and let him finish the ad.
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Knowledge of Clean Code, design techniques and patterns such as MVC and Observer
Total b**sh**. How frequently you order to carpenter which shape of hammer to use? Never? So why you ask developer which tool/architecture/etc he should use? Your business is just make professional "technical requirement", everything else is the job of developer.
|
|
|
|
|
Knowledge is the keyword, i am not sure you understood correctly. I want him to know the principles of clean code, we have coding guidelines here and if someone doesn't know them i won't take him. I don't want to review a pile of junk you know?
For the patterns etc. "such as" is used to give an example.
The carpenter learned all the tools he has and when to use which, i don't ask for anything else, i want a carpenter that knows which hammer he should use for what.
Lastly, this guys does not need to be a dev, he should be a programmer, so if i tell him we use MVC for that he has to use MVC no matter what. Therefore he should know basics about different patterns and stuff.
Hope you got it now
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Nowadays every monkey from India who knows words "design pattern" position himself as a "senior developer". As well as words "MVC/MVVM". Are you sure you will find "just a programmer" who know these words??
You know in my experience I never ever used any word from "patterns theory" - I always think about solution, despite how it's named. And my opinion is that hype around "patters" just a sign of narrow mind - instead of finding proper solution (what is not necessary a pattern at all), people enumerate pattern names, trying to apply any of 'em. These are monkeys, not a developers. Again, just my IMHO.
|
|
|
|
|
That's an entry-level job description.
Excellent for someone who is bright and wants to gain a few years of corporate job experience. I would emphasize that. Attitude is what's most important here.
|
|
|
|