71–80 of 80 posts
Earlier quoted context omitted.
Quoting from aphyr as it still brings me joy and might encourage others to read through the interview pages there, > “In Lisp,” you offer. “We often write domain-specific languages to solve new problems.” > “C is not a DSL!” > “If you insist.” Keep going anyway.
My favorite: > The Church. The lambda calculus. The gay agenda. It has known a thousand names, a thousand forms.
Gorgeous. I'm not versed well enough in the theory to validate his code, but I know enough to see where he's going with this. As an aside, there's a lot of rightful complaining about the interview process. I've been on both sides and it sucks either way. As a hiring manager for a small company, we never had the 'process' that bigger companies have, so it was always a seat of the pants decision. Not my favourite thing…
You could have at least clicked on the LinkedIn link before assuming the author was a guy... https://www.linkedin.com/in/naomi-w-liu/
Earlier quoted context omitted.
You could have at least clicked on the LinkedIn link before assuming the author was a guy... https://www.linkedin.com/in/naomi-w-liu/
My bad, should’ve used “their”.
Mis-stating gender might be careless when as you imply “their” is the always the safe bet, but it’s probably not enough to justify OP’s unduly critical response. He / she or they could have just replied with “I checked their LinkedIn and Naomi’s a girl, btw”.
Earlier quoted context omitted.
My favorite: > The Church. The lambda calculus. The gay agenda. It has known a thousand names, a thousand forms.
Why gay agenda though? What is the connection?
> how their work ethics share the same ability to resist deformation as their play habits "We work hard, we play hard" in case anyone missed it :-)
Great writing, hilarious. I feel like we all could know someone who fits these characteristics.
"Know" or "be"?
:-P
Earlier quoted context omitted.
I always liked the version with no branching statements. In python it would be roughly: def fizz_str(n): return "FIZZ" def buzz_str(n): return "BUZZ" def fizz_buzz_str(n): return "FIZZBUZZ" def to_str(n): return str(n) indexes = [3, 0, 0, 1, 0, 2, 1, 0, 0, 1, 2, 0, 1, 0, 0] def fizz_buzz(n): funcs = [ to_str, fizz_str, buzz_str, fizz_buzz_str ] return funcs[indexes[n % 15]](n) for i in range(1, 101): print(fizz_buzz(…
Here is another version of similar idea as oneliner. Additional feature - no loops and no conditions. fb = lambda n : n == 0 or not fb(n-1) or not print(['{}',"fizz","buzz","fizzbuzz"][((n%3)==0)|(((n%5)==0)*2)].format(n)) fb(100)
Earlier quoted context omitted.
In a code review, I’d given a junior programmer advice to avoid magic constants and use defines instead (c, not c++). Resubmission came back with: #define SEVENTEEN 17 Last I spoke with him, he was a Java instructor.
It is truly amazing. One can rave about OOP all day and not understand the basics of programming or good, readable code. Truly mindboggling.
E: in other words, those who code to live vs live to code.
Earlier quoted context omitted.
In a code review, I’d given a junior programmer advice to avoid magic constants and use defines instead (c, not c++). Resubmission came back with: #define SEVENTEEN 17 Last I spoke with him, he was a Java instructor.
The truly brilliant thing to do would be #define SEVENTEEN 16
#define MAGIC_16 16
It takes all kinds.
A personal favorite ruby -e 'puts (0..99).map {|i| srand(46308667) if (i%15).zero?; ["FizzBuzz", "Buzz", i+1, "Fizz"][rand(4)]}'
It also has the side effect of making me feel better for never attempting to write my own encryption algorithms! :D