Checking In with Erik Meijer: Erik Meijer

Play Checking In with Erik Meijer: Erik Meijer
Sign in to queue


No, Erik Meijer doesn't interview himself! :) However, it actually is checking in with Erik Meijer (it's been WAY too long since we last caught up on camera...), so we figured it was a great idea to rehydrate this show with the master himself in the hot seat.

As you can imagine, we cover a lot of ground in this one hour plus conversation. Erik has been busy hacking, teaching, and writing, but mostly hacking. Tune in to learn about the latest work Erik has been doing. You may be surprised as it's not Rx++ or even code at all.

Huge thanks to Erik for taking time from his hectic schedule to hang out in my office for a while and talk about, well, lots of things related to the craft of making software in 2014 and beyond. Always a real pleasure to get a chance to ask Erik random questions and learn from him.

Tune in. Enjoy.



The Discussion

  • User profile image

    @Charles, is Erik still a Microsoft employee or he left the company?

  • User profile image
    Awesome conversion, as always.
    In the company where I work, it's definitely the case where leaders coming from the dev side push harder to create productive environment for their developers while trying to improve existing internal processes.

    Is Erik's new paper going to be publicly available?
  • User profile image

    @Pazz At 23:30 Erik says he left Microsoft 18 months ago

  • User profile image
    Fabio Galuppo

    great conversation as usual!

    Especially, this part: "... You should take away all other distractions, there's should no meetings, no stand-ups. Developer should be focus on writing code. And the goal of the management is to create that context where the developer can focus on code ..."


  • User profile image

    @Charles where can I find that 9 page guide that you mentioned?

  • User profile image

    Towards the end the discussion is about having a "feedback loop" that goes something like this--depending upon whether a software feature is generating more sales or more support calls, that should determine the proponent's bonus (or he/she gets a shock every time he/she touches the keyboard). Straight-forward thought but very hard to implement in practice. How do you distill out the true value of a feature? Alternatively, how do you determine commercialization potential of an idea. What if you can't prove that you have lost a sale because of not having that feature.

  • User profile image

    Hi Erik and @Charles,
    I've been very happy tonight when I discovered a new talk with Erik on Channel 9!!!
    I've not listened to the episode yet but I always enjoy his talks!! He's for me a font of inspiration and more over the guy that introduced me to the functional programming world (I avidly listened to all his lessons on Channel 9).
    Erik: a great thank You for Your time!!!!

  • User profile image

    @scyonx: Unfortunately, the .NET API Design Guidelines Digest is not available. I've asked the .NET Framework people (some of them long time Niners... Hi Immo!!) when it may show up again (and understandably with some updated guidelines given it's age...).


  • User profile image

    I'm re-encoding this one to produce higher quality output. I hope to post the updated files tomorrow.


  • User profile image

    The thing that occurred to me when you guys were talking about API design was when Erik said that "its a discipline and it takes talent"...It seems that lots of large organizations are actually trying to find management practices that are trying to squeeze creativity out of development or other IT areas because they don't want to need people that are talented. It's seen as a liability. They want replaceable cogs. (Pardon the hyperbole.) They don't want to pay talented people, for one thing, and they don't want to be "held hostage" by talented people that are hard to replace.


    I don't know. It's just a thought.

  • User profile image

    Vim is fast, simple, and provides powerful editing features, which is where most people live while writing anything, including code. Who needs a refactoring tool that requires mouse clicks when you can quickly type a replacement string or visually copy and move code around? I gave up on ReSharper several years ago when VsVim became available. VS no longer crashed as frequently, and I didn't have to hunt and click any longer. (I even knew the R# shortcuts fairly well.)

    For scripting languages, vim is almost as good as anything else, since most code completion is of the form, "Here's everything I've seen following a '.'" Static languages are another matter, and I find an IDE much nicer b/c of the better code completion. Even for dynamic languages, it's certainly gotten better, and I like Visual Studio, Xamarin Studio, and WebStorm, the IDEs with which I'm most familiar, quite a lot. However, I cannot function nearly as well in a non-vi environment as I do with vim. Each of those IDEs offers some level of vi support.

    Lastly, I don't think general IDEs do a very great job. The absolute best environments I've tried include Light Table and CloudSharper, which give you in-context results. That's the next step beyond simple text editing. Code completion is helpful, but not nearly as useful as in-context execution. (I tried to add links, but I keep getting a message stating the post appears to be spam.)

Add Your 2 Cents