Building Web Apps & Services with Entity Framework and Web API.
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.
The Case for PowerShell.
Brief, terse, compact, too many jokes. Excellent details. Not training, rather informational. Must have scripting/automation experience to appreciate the implications of what is covered. Without that experience, the presentation could be viewed as too light-weight.
IIS for Developers.
Brief, terse, compact. Excellent details required to deploy a system to IIS. Not training, rather informational. Must have server/system-deploy experience, and therefore questions, before viewing.
Table.el is a package that lets you utilize tables in plain text files.
It also works correctly within org-mode files.
What I found most interesting was the ability to split individual cells vertically and horizontally.
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.
Of course it does.
Nice lightweight example of the difference between a document’s definition on the storage media (file-system) and its presentation to the user. Not to lean too hard on this, but if you grok what is happening here then you will enjoy Emacs a lot more.
Of course there is one. Via org.
It will face major adoption issues in the enterprise due to the fact that it is not based upon XML.
It will face major adoption issues on the web due to the fact that it is not based upon JSON.
That is OK though because it will outlive both of them.
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.
Pose the question “Is there ever a time when Emacs users should be running out-of-date bytecode instead of the up-to-date bytecode or lisp?” to yourself.
All Emacs users should probably run auto-compile.