5 ms·

Reminds me of the "Evolution of a Haskell programmer": https://www.willamette.edu/~fruehr/haskell/evolution.html https://www.willamette.edu/~fruehr/haskell/evo

by ot 9y ago

Reminds me of the "Evolution of a Haskell programmer": https://www.willamette.edu/~fruehr/haskell/evolution.html https://www.willamette.edu/~fruehr/haskell/evolution.html Make sure you don't miss the punchline, "Tenured professor". It's the same with the progression of engineering seniority: increasing levels of cleverness and unnecessary sophistication, until you reach a point where you don't have anything to prove anymore, and you can feel comfortable writing the simplest and most elegant solution.

madsohm 9y ago
I've been doing a lot of Haskell on Codewars.com recently. This is exactly what I see. I write up a long solution, that uses the basics like pattern matching, heads of lists and such. The solution that has the most "Best practise" up-votes are usually something involving importing control.monad and other similar stuff.
- Unkechaug 9y ago
  Sites like Codewars seem to me like good ideas starting out, but it doesn't take that long to turn into an arms race of complex one liners that people vote up as the coolest solution, not the best in terms of productivity for a company.
- hinkley 9y ago
  If you write code that other people have to ask you about, you will reach a point where you don’t have time to write code anymore because you’re too busy answering for your own code. You may interpret this as “helping your less fortunate teammates” but the wise know they can reduce your influence on the team by sending more people to ask you questions. Giving them more time to clean up your mess and you none to make it worse.
jrs95 9y ago
It's kind of amusing to me that a lot of engineering interviews also seem to be focused on doing things that you generally won't and shouldn't be doing for the position. What's the point of seeing if someone knows data structures and algorithms they won't be using if they can't write a web application that interfaces with a SQL database without doing queries in a for loop?
- e12e 9y ago
  > What's the point of seeing if someone knows data structures and algorithms they won't be using if they can't write a web application that interfaces with a SQL database without doing queries in a for loop? Isn't this the basic architecture of a node js "event loop" Cms that gets content from a rdbms? ;-) # pseudo code While new_user_request query_db with request parameters I know it's not what you meant, you meant do the above, rather than: # pseudo code While new_user_request query_db for user data query_db for session data For parameter, user_data, session_data query_db with each item
52-6F-62 9y ago
That was great— though not being versed in Haskell, I tried to follow their link to the original version, but it had died. Here's the original: http://www.ariel.com.au/jokes/The_Evolution_of_a_Programmer.html http://www.ariel.com.au/jokes/The_Evolution_of_a_Programmer.... The punchline got me pretty good.

by ot 9y ago

madsohm 9y ago

I've been doing a lot of Haskell on Codewars.com recently. This is exactly what I see. I write up a long solution, that uses the basics like pattern matching, heads of lists and such. The solution that has the most "Best practise" up-votes are usually something involving importing control.monad and other similar stuff.

Unkechaug 9y ago
Sites like Codewars seem to me like good ideas starting out, but it doesn't take that long to turn into an arms race of complex one liners that people vote up as the coolest solution, not the best in terms of productivity for a company.
hinkley 9y ago
If you write code that other people have to ask you about, you will reach a point where you don’t have time to write code anymore because you’re too busy answering for your own code. You may interpret this as “helping your less fortunate teammates” but the wise know they can reduce your influence on the team by sending more people to ask you questions. Giving them more time to clean up your mess and you none to make it worse.

jrs95 9y ago

It's kind of amusing to me that a lot of engineering interviews also seem to be focused on doing things that you generally won't and shouldn't be doing for the position. What's the point of seeing if someone knows data structures and algorithms they won't be using if they can't write a web application that interfaces with a SQL database without doing queries in a for loop?

e12e 9y ago
> What's the point of seeing if someone knows data structures and algorithms they won't be using if they can't write a web application that interfaces with a SQL database without doing queries in a for loop? Isn't this the basic architecture of a node js "event loop" Cms that gets content from a rdbms? ;-) # pseudo code While new_user_request query_db with request parameters I know it's not what you meant, you meant do the above, rather than: # pseudo code While new_user_request query_db for user data query_db for session data For parameter, user_data, session_data query_db with each item

52-6F-62 9y ago

That was great— though not being versed in Haskell, I tried to follow their link to the original version, but it had died. Here's the original: http://www.ariel.com.au/jokes/The_Evolution_of_a_Programmer.html http://www.ariel.com.au/jokes/The_Evolution_of_a_Programmer.... The punchline got me pretty good.