32,081 reputation
864123
bio website none
location United States
age
visits member for 4 years, 2 months
seen yesterday

profile for Caleb on Stack Exchange, a network of free, community-driven Q&A sites


You: Do you know Jon Skeet?

Expert: I once tried to convince the community, it worked remarkably well.

You: Do you know Joel Spolsky?

Expert: I know joel spolsky to a certain degree at least.

You: Does he treat you well?

Expert: :)

You: What is it like to work at Stack Exchange?

Expert: The answer is pretty complicated.

You: I'm listening.

Expert: I used to know someone who was listening.


Mar
25
comment Using advertising with free app is a commercial app?
It's not a coincidence that another word for advertisement is commercial.
Mar
13
awarded  Yearling
Jan
21
revised Should a scrum team estimate time for the user stories during Sprint Planning, or before it?
added 32 characters in body
Jan
21
answered Should a scrum team estimate time for the user stories during Sprint Planning, or before it?
Dec
20
comment What is a closure and how is it implemented in Ruby?
@raptortech97 It's actually "a little more" than a link only answer, where the "little more" is a concise explanation of what a closure is and how that relates to Ruby.
Dec
15
comment Should I give the answer to a failed interview coding exercise?
@user1172763 That's the point -- unlike FizzBuzz, the OP's interview question can be answered with a single calculation. It is therefore a poor choice if the point is to see whether the candidate can write a loop. You can't expect a candidate to choose a slower, far more verbose solution on the assumption that you're asking the question for a specific (and unstated) reason. Indeed, the interviewer could easily be a "trick" question to see if the candidate notices that looping is completely unnecessary. Reading your mind is not the candidate's responsibility.
Nov
6
comment offline application development for mobile devices
Googling for something like html5 offline forms will turn up a lot of useful information.
Nov
6
comment Why do we use non-descriptive internal codenames?
Names acquire meaning over time. If you'd all been using lon-web-lin-2 and the like for years and then some VP decreed that from now on all servers would be named after moons and/or body parts, things would have been equally confusing, maybe even more so because the "new" names would arbitrary instead of systematic.
Nov
6
comment Why do we use non-descriptive internal codenames?
What’s in a name? That which we call a rose by any other word would smell as sweet.
Oct
8
awarded  Good Answer
Oct
6
comment Are there any OO languages without inheritance?
Preferring composition doesn't mean completely abandoning inheritance is a good idea.
Oct
6
comment On GitHub, etiquette and pull requests
@Greg I can't tell whether you're really asking whether you should contact the author (last line of question, answered in the accepted answer in the dupe) or how to contact the author (seems to be answered by your observation that Github doesn't have a built-in messaging system). Perhaps you could clarify what you want to know.
Oct
3
answered How to predict a future simulation state
Oct
3
awarded  Nice Answer
Oct
3
awarded  design
Oct
2
revised When writing object-oriented code, should I always be following a design pattern?
added 365 characters in body
Oct
2
answered When writing object-oriented code, should I always be following a design pattern?
Sep
30
awarded  Explainer
Sep
26
comment Is there any language-agnostic specification for “String Natural Sorting Order”
Are you asking about sort algorithms or sort order? Algorithms for sorting are well understood and widely implemented in every language you're likely to use. The particular order that you want to sort things into depends heavily on your situation, but is usually tied to the character set you're using.
Sep
8
comment Is it correct to keep version numbers of all components always the same?
What's the point of giving each component its own version number if it doesn't indicate the version of that component? If the "version" really just indicates the version of the overall application that that component belongs to, that's fine, but you should make it clear that the number is the app version, not the component version. And as you say, any update to any component means that you have to release new versions of everything, which sort of defeats the point of a component architecture in the first place.