957 reputation
814
bio website
location Zug, Switzerland
age
visits member for 3 years, 6 months
seen Feb 23 at 20:29

I no longer participate in this site. You may still find me haunting SO.


Sep
17
comment Is over-engineering a warning sign?
@moderators, the question has been put on hold as it is deemed opinion based - and I can't argue with this; the purpose was to solicit other's opinions rather than get a yes/no answer - which frankly is impossible in this case. What's more useful from something like this is the thought process others go through when determining an answer to a problem like this, and this can only be opinion. I cannot think of a way of re-wording this to get a yes/no answer - but I will accept an answer which I think makes most sense and helps me with my thought process...
Sep
16
comment Is over-engineering a warning sign?
@jwenting, let me assure you, we do no such thing, that's just underhanded. If we do proceed however, we will in the f2f interviews, talk through how they could expand to add corner cases, but only if the candidates bring it up.
Sep
16
comment Is over-engineering a warning sign?
For a coding exercise, it's a bit much to expect candidates to stick to coding standards and style - but consistency is a fair expectation. We expect that candidates will use the language idiomatically, but we're not after test cases - the time frame is only two hours (I think it's unrealistic.) I don't believe in tricks in interviews, there's no point - I've been in those situations before, and frankly I find that they are an ego trip for the interviewer and so best avoided. We do explicitly mention OOD (and yet it's amazing to see solutions that use no OO..)
Sep
16
comment Is over-engineering a warning sign?
@ptyx, I would have thought the point of a coding exercise is to show how you would tackle a problem you're not familiar with under a time pressure. Can you grasp the problem, and can you provide a solution; your "answer" really isn't an answer. Unfortunately given our domain, the problem cannot be simplified any further than it is...
Sep
13
comment Is over-engineering a warning sign?
+1, this is my current thought process, I guess it's good to see it's not naive or plain dumb... Thanks for the two Joel links...
Sep
13
comment Is over-engineering a warning sign?
With all due respect, I disagree, the exercise even goes as far as saying that pseudo code demonstrating your approach would be acceptable. Frankly I would say that a simple solutions which solves the problem is a better demonstration of your capability that stuffing every design pattern in the book just to impress?
Sep
13
comment Is over-engineering a warning sign?
@MathewFoscarini, that would give the game away.. :) Basically the problem is to scan a file and calculate a latency between two types of updates - this is explicitly listed and drawn out with examples; I had to do the same exercise way back when I joined... :)
Apr
1
comment Functional document from code
You are stuck between a rock and a hard place. You could try something like a UML modelling tool and see if it can reverse engineer the models from the java code (AFAIK, NetBeans for example used to have a tool capable of this pre version 7.) That could be a starting point, else, it's navigating the code manually and documenting as you go - eitherways, a shit job to do!
Jul
2
comment Do your managers prefer to create proof of concept (POC) before working prototype?
should also add that there should be a clear understanding of the scope of the POC - i.e. there is a clear line between it and a fully fledged implementation...
Mar
8
comment Are time restrictions on technical tests a good thing?
@kevincline, I totally agree, I just wanted to canvass some opinions to see what the general thinking is. The 2 hour time limit is more than generous for anyone of any experience to come up with some sort of design. If they cannot, that in itself is a no-no for me (implies they cannot really think on their feet/adapt/react quickly...)
Mar
8
comment Are time restrictions on technical tests a good thing?
I like "analysis paralysis"... :)
Mar
8
comment Are time restrictions on technical tests a good thing?
That's the counter argument to the time limit, by placing this artificial limit, are we also rejecting good but slow candidates.. I guess there is no real win...
Mar
8
comment Are time restrictions on technical tests a good thing?
@blunders, as I mentioned in a comment below, we state that in the spec, "we don't expect a fully working solution", just your thoughts...
Mar
8
comment Are time restrictions on technical tests a good thing?
Funnily enough, all of the folks here have passed that test (aside from one or two founders!) ;)
Mar
8
comment Are time restrictions on technical tests a good thing?
We do communicate exactly that (i.e. we don't expect a fully working solution, pseudocode with some descriptions is sufficient), we just want to see their thinking, hence why I am in favour of the time limit.
Mar
8
comment Are time restrictions on technical tests a good thing?
@Oded, updated the question...
Aug
18
comment Advantages of a left to right language syntax
I rarely downvote (and in this case it's pointless), but this deserves a -1. The majority of this answer has nothing to do with the question!
Aug
18
comment Advantages of a left to right language syntax
I did not vote to close, but, the comment by @Devjosh is pertinent, it's more appropriate for Programmers, hopefully someone will migrate it....
Aug
9
comment Is micro-optimisation important when coding?
I generally agree - except for one line, I contend that "every idiot thinks they can micro-optimize"... ;)
Jul
23
comment Finding a new job when my skillset isn't matching the job ads
@tryurbest, not convinced of the bloomberg argument, went for a "c++" interview there, every question was c. I agree with sbi here.