[psynapse]

"Let me talk to your biz people to see if I'm the right person to solve your problems, and let the technical folk go over code I've written and we can deep dive on that if there is any question about my chops."

I feel you here.

With becoming longer of tooth (in the trade) comes an understanding of how to contribute value via the multitude of avenues that are not just grinding out lines at the keyboard.

I am surprised over and over at the incandescently bright young people who can wax lyrical about monad transformers, but to whom it does not occur to model a domain properly before cutting code, or who lack basic schema design and/or SQL knowledge.

I am also in the boat of having vanishingly few technical interviews in recent years, but on a good deal of those occasions it has been obvious that the interviewer is just so not the person I should be talking to.

[quickthrower2]

Modelling a domain is very underrated by companies as well as individuals and it's a shame because we end up with code bases full of mixed purposes language and confused naming that makes it harder to work on legacy.

Monad Transformers FWIW are bread and butter in Haskell. So it a bit like going on about dependency injection. Not necessarily a sign of being stuck up or head in the clouds.

[heartbreak]

In some circles writing Haskell in the first place is a sign of having one’s head in the clouds.

[btilly]

https://aphyr.com/posts/342-typing-the-technical-interview comes to mind about now...

[quickthrower2]

Feels that way in the c# world sometimes. Ironic given the love for Linq, Rx, Generics, Lambdas etc.

[jeremiep]

Where do you think these ideas come from? :)

Microsoft has Haskell in R&D pushing ideas to F# which in turn pushes them to C#.