> I can fix anyone's code, even when I've never used the language before [..]

You can jump into any codebase and solve core architectural problems like precise garbage collection, eventual consistency, or miscellaneous dead locks? I'm not making up contrived examples, these are some of the problems my friends and I are currently dealing with at work for different companies.

> I would only have a vague idea of how to do a integer => string conversion with base N without googling it. So am I shit? Am I suddenly a useless programmer because lazyjones only likes people who studied CS?

I've never had to do integer => string conversion until asked in an interview either and I still did it. It's not a difficult problem. Anyone with a basic understanding of division and string manipulation should be able to reason out a solution.

> You have picked an arbitrary, and extremely rare in the programming world, standard. No-one needs to write their own string handling routines any more.

I wrote my own C++ string library before std::string was introduced. I contribute to Rust which has its own string, big number, vector libraries and much more. The web site I work on gets >130M monthly uniques and we have extended Python's string, dictionary, iteration, and datetime modules because the standard library isn't enough.

> [Programming languages are] all pretty much the same after you've used 3 or 4.

Then you haven't used enough languages. Try functional programming via Haskell, or dependent typing via Coq, or concurrency via Erlang, or memory safety via Rust.

The world is a really big place. I know people infinitely smarter than me doing incredible things, and there are many more like them. Stop being limited by your own experiences.

>>I would only have a vague idea of how to do a integer => string conversion with base N without googling it. So am I shit?

If you receive a programming task like the above (with a relatively clear specification, very little state to manage, defined domain of the desired function, and the input and output of the function are most likely primitives in your language, your standart library probably have lots of utility functions to work with these primitives), I will expect, that you should be able to do it without googling.

Your solution may not be the most effective/short/clean, but it should work. If you can not do it without googling, well ... yes, I do think you are a shitty (or just out of shape for the moment) programmer.

You will need more programming exercise, in order to know more algorithms and aproaches to solving problems, and/or learn better your language and its standart library.

I'd tend to agree with lazyjones. I doubt that his expectation is that you would know all the tricks for making the most efficient integer => string conversion routine ever, but I certainly would expect any competent programmer to be able to write an integer => string conversion routine without really thinking about it, not because anyone needs to write such code much anymore, but simply because a competent programmer should have sufficient mathematical understanding to see the obvious solution to the problem. This isn't about writing string handling code, but about demonstrating understanding of very basic mathematics using a trivial problem that should need a line or two of code in most programming languages to solve.

> would only have a vague idea of how to do a integer => string conversion with base N without googling it. So am I shit?

I would probably not hire you unless you could actually back up your dubious claims ("I can fix anyone's code ..."). The funny thing is, while I am judging people by their ability to solve a particular problem (which admittedly may have an age bias), you are judging people who studied CS based on the fact that you didn't but are still full of yourself.

> I would only have a vague idea of how to do a integer => string conversion with base N without googling it. So am I shit?

It sounds very much like it I'm afraid. This is trivial problem solving. Your overconfidence + lack of problem solving ability are big red flags. If you're as good as you claim you are then you should know foundational principles. It gives you a far greater insight into programming than just grinding away with other programmers 'snippets'.

I feel like it's a pretty common phenomenon for people to have their pet somewhat-arcane "gotcha" problem that they feel is the ultimate decider of who's shit and who isn't. And you're on HN, so the responses are going to be way more pedantic than just about anywhere else.

Personally I think this example is way more reasonable than most other technical "gotcha" problems. (I say that because I could solve it despite not having studied CS and being still relatively inexperienced.) But at least they're not asking how many pickles you could eat before exploding if you were shrunk down to the size of a kitten's tongue and placed on a miniature rocking horse that may or may not be alive inside its sad plastic shell.