In the first article in this series (Git: Rebase vs Merge) I covered the tactics of rebasing. I discussed what merge commits are, and how to avoid them with rebasing. In this post I'll cover the benefits of rebasing, including how its use speeds up finding hard to track down bugs via git blame and git bisect.
SRV_JAVA_OPTS=”-Dfile.encoding=UTF-8 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Xms20m -Xmx1024m -Dsun.net.inetaddr.ttl=300 -Dnetworkaddress.cache.ttl=300 -Dsun.net.inetaddr.negative.ttl=0 -Dnetworkaddress.cache.negative.ttl=0 -Dc42.native.md5.enabled=false”
I firmly believe ReSharper is the best thing to happen to .Net since Visual Studio (NCrunch is a close second). In evangelizing it I managed to convince my program to purchase copies for every developer. One caveat: I had to train everyone.
Exposing Web API endpoints from DotNetNuke is very easy to do and is extremely useful for accessing the internals of DNN. For example, if I want to get a list of all of the custom roles that are available for a particular DNN site, I can easily do so by creating a custom endpoint as illustrated at http://www.dnnsoftware.com/community-blog/cid/144400/webapi-tips.
Distributed version control (git): Check.
Feature branches: Check.
Rebasing: Ugh, seriously?
On multiple projects I've attempted to introduce the concept of rebasing commits. It rarely goes well (at first). The initial reaction tends to be reluctance and confusion.
At InfernoRed Technology we have a team of awesome developers and technologists. When we're not building amazing products for our partners and customers all over the country we're out getting involved in our local developer communities. Throughout the year InfernoRed hosts, sponsors, and speaks at developer events like meetups, code camps, and conferences. This next month is no exception! Here is what we'll be up to:
Have you attended a presentation on the hottest bleeding-edge technology and the presentation turned out to be less exciting than watching the paint grow (or the grass dry)?
When it comes to technology, I don't learn by watching somebody else do it; I have to do it myself.
So why do so many technical talks consist of reading slides or pasting code blocks?
Topics: Best Practices
I have to admit, the first time I tried HoloLens at //Build in 2015, I was underwhelmed. The demo was scripted, and the product was clearly not complete. There was literally a main behind the curtain debugging the device as we went through the motions.
This article explains what Xamarin is, the basics of how it works, and dispels four common misconceptions.
When Mary Jo Foley and Paul Thurott attempted and failed to describe Xamarin on Windows Weekly a couple of months ago, I grumbled about pundits not performing due research and moved on. But when even Scott Hanselman (who I worship greatly admire) mischaracterized it on his most recent podcast, I realized there is sufficient confusion within our industry that additional clarification is needed.
If I can be a little honest, I feel like the HoloLens might be a solution in search of a problem. But that's probably because it is so new and we are just beginning to understand its impact. I think credit goes to Microsoft for understanding this, and that is likely why the device is not marketed to consumers. But what about businesses? Who can benefit from this technology?