Building Web Apps & Services with Entity Framework and Web API

Building Web Apps & Services with Entity Framework and Web API.
If you already know JavaScript, C#, an ORM, and IoC, and all of the other stuff for dealing with, then this is a fast-track to getting on-board with them on the MS platform. Yea, it is fast, but you can get the details elsewhere. This is the place just to see it happen. So many value-adds are referenced in the video. Don’t want to talk it up to much, but it is just very valuable. The major failing here is that the examples are no longer correct though, so you have to do research just to make sense of what is happening and how to implement it.

C# Tips and Traps

C# Tips and Traps.
Each session contains 5-10 pieces of information. The topics are varied and unrelated. That is OK. Basically, everything that you learn here, you ought to know. They are things that will, were you to not know these things, would easily identify you as not being a real .NET developer. Don’t get me wrong, you won’t learn anything here that will radically change your contribution. Rather, it is just little things, that, if you don’t know them, you will look really stupid, not dumb, just stupid. You probably won’t even remember them either, that is, until you run into that situation. At that point, you will recall “Hey I saw that video…” and that is where it pays off. Even just stuff like partial classes and functions, I haven’t thought about that for a long time, and hey, thanks for the reminder. Another nice one is seeing how easy it is to implement debugger visualizations with annotations. Knew you could, but didn’t realize it was that easy. So if you have 2-3 hours, then watch it, at 2X.

Lightweight DevOps

Introducing DevOps to your organization can be done really, really simply.
First have the project team lead set up the development environment on his machine, all the while documenting how to do so. Second have a another team member follow and execute the steps. The lead and team member should discuss and review the process and make improvement. Third, have an engineer totally unfamiliar with the project follow the steps to the point where he can successfully run the automated tests in less than sixty minutes.
When this may be done successfully, it is time for a DevOps engineer to automate that process.

Probably Try to Avoid local-set-key

When I first learned how to set up Emacs, I really liked local-set-key because you didn’t have to know about the keymap for the mode you just had to make the call in that mode’s hook. That is simple and makes total sense. That has worked well for me for years until two things happened:

  • Wanted to use prefix commands
  • Re-started using Windows again on a daily basis

The former is part of the natural expansion of use and its refinement. The latter is similar, but specific to running Emacs on Windows.

The last time that I ran Emacs on Windows I did not use the Super key. Then I went off into the wilderness and use it a lot only to return and find that Windows owns lot of my keybindings. Not only were they owned, but they would not let go of them no matter how I tried! Because if this major inconvenience, I’ve got no reasonable choice other than refactoring some of my perfect bindings into something, ahem, better.

This refactoring would have been pretty easy if I’d jus done normal keybindings against keymaps, but I didn’t, I used local-set-key. So this becomes a good learning opportunity about the key-map names and additionally how, at least for myself, this is generally a bad approach because makes re-factoring harder.

The good thing is that at least up front there is a good time savings, I suppose.