Programming with eclipse

-
Quick! Anyone who's ever used eclipse for more than 5 years tell me how you would find a file in your project(or workspace) with a name that starts with the test "BuildString".

If you answered:
Hit CTRL+SHIFT+R
Then type BuildString

I'd believe you used eclipse more than a few hours.

If you answered:

Hit CTRL+SHIFT+T
Then type BuildString

I'd ask "what if you where looking for a property file, not a class?"... Even if you got it wrong, I'd believe you use eclipse, but perhaps just misinterpreted my question.

If you answered:
I'd click on then to menu and select 'find', then switch to the file view then...
or any of 100 other possible combinations like:
I'd drop to a shell prompt and use the 'grep'
or
I'd use windows search
or
I'd open a browser to google
I'd say "that's interesting, I hadn't thought of that" and give you some credit for understanding the problem and having some sort of plausible solution.

If you said "I've never had to do that" I'd silently intake a slow breath to prevent myself from jumping across the table and beating you over the head with a copy of "programming interviews for dummies".

Listen, at an interview I KNOW folks are lying and overstating their capabilities... I kinda expect it. You're trying to show us you're superman + wonderwomen + aquaman all rolled into one.

But if you show up saying you can leap over tall buildings and I ask you to jump over a 10" rock... You better clear it or I'm just not going to waste any more of my time. I don't care if you can leap tall buildings because of superpowers, a yellow sun, jetpack, trampoline, or any other "cheater"... I just want an illustration that you can actually do something similar to what you originally claimed.

Comments

Post a Comment

Popular posts from this blog

Please use ANSI-92 SQL Join Syntax

-
Image
Way back in 1992, a standard was published for SQL. In it, the syntax for specifying joins in SQL Database was finally standardized. This was a good thing because (for folks who've been doing this a while), trying to decode the vagaries of how various Databases handled outer joins could drive you bonkers yielding different results depending on the parse order of things in the from and where clauses. Unfortunately, some DBMS vendors took a while to adopt this standard (Oracle didn't support it until 2001), but at this point if you're using a major RDBMS and NOT using it, you're probably mired in a tradition or habit that bears changing. As an example of what I'm describing, here are some examples of what I mean. Old School (no standard syntax + implementation and evaluation of predicates varied by vendor [and query]): select * from customer, order where customer.customer = order.customerid ANSI way (agreed to standard, predicate evaluation has some rules
Read more

the myth of asynchronous JDBC

-
Image
I keep seeing people (especially in the scala/typesafe world) posting about async jdbc libraries. STOP IT! Under the current APIs, async JDBC belongs in a realm with Unicorns, Tiger Squirrels, and 8' spiders. While you might be able to move the blocking operations and queue requests and keep your "main" worker threads from blocking, jdbc is synchronous. At some point, somewhere, there's going to be a thread blocking waiting for a response. It's frustrating to see so many folks hyping this and muddying the waters. Unless you write your own client for a dbms and have a dbms that can multiplex calls over a single connection (or using some other strategy to enable this capability) db access is going to block. It's not impossible to make the calls completely async, but nobody's built it yet. Yes, I know ajdbc is taking a stab at this capability, but even IT uses a thread pool for the blocking calls (be default). Someday we'll have async databa
Read more

The difference between Scalability, Performance, Efficiency, and Concurrency explained

-
I thought I'd give some explanation of the difference between scalability, performance, Efficiency, and concurrency. To make things more accessible (and because I'm watching a cooking show on TV) I'm going to use a baking metaphor to help explain the differences. In our case, the system in question is baking cookies for consumers. Scalability, is how well something responds to adding more resources. If we can double our capacity by doubling the number of resources, we've got linear scalability. In our baking example, if we add more ingredients, we can scale to a larger number of cookies. To contrast with our other metrics, this doesn't actually increase the performance of creating a single cookie (they still take 10 minutes to bake), and the efficiency is the same (we just have more capacity). We also cannot bake more cookies in a fixed time period, but over a larger time period we can produce more cookies. Performance is how fast something can get done, u
Read more