Comments for Josh Cogan's Projects http://joshcogan.com/wp Fun stuff Josh works on Fri, 22 Mar 2013 16:59:09 +0000 hourly 1 https://wordpress.org/?v=4.0.38 Comment on Printing TTree Branches by Josh http://joshcogan.com/wp/2013/03/printing-ttree-branches/#comment-6 Fri, 22 Mar 2013 16:59:09 +0000 http://joshcogan.com/wp/?p=51#comment-6 Thats a good idea too, but I thought the MakeClass hammer was a bit too big; also it leaves filesystem side effects. However I do use/grep MakeClass code for an application I have that auto-generates PROOF code. Hopefully I’ll get a page up about that at some point =)

Thanks!

]]> Comment on Printing TTree Branches by Jet http://joshcogan.com/wp/2013/03/printing-ttree-branches/#comment-4 Fri, 22 Mar 2013 08:54:26 +0000 http://joshcogan.com/wp/?p=51#comment-4 Slick. I always just used MakeCode or MakeClass to spit out the structure, but this is cleverer.

]]> Comment on Ineffective Sorts by Josh http://joshcogan.com/wp/2013/03/ineffective-sorts/#comment-3 Wed, 20 Mar 2013 16:42:44 +0000 http://joshcogan.com/wp/?p=60#comment-3 Hey Davy,

Thanks for sharing! You make it sound like you’re getting new ideas externally, is there some secret conference ever year where tech hirers exchange ideas or best practices? I’m guessing not, but I think it’d be a very neat conversation to listen in on =).

I love the idea of real-er problems; I love the idea of attempting problems that need more 20 minutes. Sure you can’t do it all in an hour interview, but I’d be embarrassed if I could show someone the sum total of my ability in an hour, anyway…

“Take chances, make mistakes, get messy!” — Mrs. Frizzle

]]> Comment on Ineffective Sorts by Davy http://joshcogan.com/wp/2013/03/ineffective-sorts/#comment-2 Tue, 19 Mar 2013 00:47:22 +0000 http://joshcogan.com/wp/?p=60#comment-2 At my company, in order to try and keep our inteviewing process relevant and effective, we are trying to pull in more interactive interviewing techniques. Less of the ‘quick solve this problem!’ questions and more interviews that actually get to the meat of what programmers do day in and day out. We’re going to start experimenting with pair-programming interviews, where the interviewer and interviewee solve real (or ‘real’, or real-ish or Real^TM) problems together. This should hopefully determine the things we actually care about in our co-workers: how easy are they to work with, do they think on their feet, do they understand the code they or their pair writes, and how easily can they solve problems with a computer with The Googles installed on it.

]]>