non-programming

And in the non-programming job you learn a whole new field and then apply code to it.

So, for me the answer to this question has been: listen for opportunities in the communities around fun, non-programming fields.

You can perform programming activities in spreadsheets and you can perform non-programming activities in spreadsheets.

He was running his own company and offered me a (non-programming, IT) job.

HN certainly has a lot more startup and non-programming content than reddit.

Often when these things have bitten me it has been non-programming stuff.

Domain knowledge of the type relevant to programmers in many fields is gained through experience programming in that field, not non-programming experience in that field.

I do it both in programming, when it makes sense, and in everyday (non-programming) things.

The only numbers I've seen come from the Separating Programming Sheep From Non-Programming Goats papers by Saeed Dehnadi and Richard Bornat: > We have discovered a test which divides programming sheep from non-programming goats.

I looked through manually and found about a dozen companies each with non-programming technical openings, such as for biologists, physicists, or electrical engineers.

I have one hour lunch and spend two hours doing non-programming work (e.g.

I had a grad school classmate who paid someone to do his (non-programming) take-home homework for a job interview, and he got the job.

The "programmer-only" requirement seems self-imposed by the site, and it would be trivially simple to organize non-programming-centric engineering positions.

Another point is that it seems that the concept was devised by somebody with a non-programming background, as it sounds rather weird to say that they host "an algorithm".

For non-programming journalists, there's just no concept of being able to create a one-command deterministic "build" of a story...so separating the story into multiple files is very impractical...because it means you have to reassemble them by copying-pasting when it's publication time.

Obviously I'm not going to just tell them "ok now let's write a tokenizer and interpreter." The beginners I know know what (non-programming) tokens are and I'm sure they would be 100% comfortable with an explanation.