Much of Angular’s built-in functionality is provided by modular slices of code called directives. You can write custom directives to perform form validation, to minimize code repetition, to attach events to elements, to inject markup into templates, and more. Directives are so powerful that their usefulness is limited only by how well you understand them. Get more out of Angular by learning how to write custom directives today.
Assessing the Problem
For months, I have been battling connectivity issues with Exchange Online from home. My Outlook seems to function fine at work, on wifi tether, but when I get home, the connectivity is unstable. Some of the symptoms I’ve been seeing are:
- Message stuck in outbox
- Frequent Sync Errors
- No messages coming into inbox, then all of a sudden a stream of messages come in
Some of the sync errors I experienced look like:
One of the easiest ways to deter users from your website is to provide them with a frustrating experience. Be that with broken features, outdated information, or more times than not, an unfriendly user interface. Even the most feature-rich websites will lose users if they don’t have a website that users can access, navigate, and view, no matter what device they’re on. The aim of this post is to help you keep customers by familiarizing you with responsive design and give you the tools to quickly implement these principles in your websites as well as your SharePoint solutions.
It’s a simple enough question to ask and answer. In almost every introduction to a foreign language, it’s one of the basic phrases we learn. We’ll leave aside the irony that we almost never ask the question of another person, because of mobile phones, tablets, and myriad ways which we can answer that question ourselves. As developers, we’re often given the task of producing output that includes some date value, usually in a grid or table that provides the user with information about when a particular thing happened.
So far, pretty easy stuff. But I was recently asked to provide users with that information displayed in local time, with some users were scattered over a plethora of timezones. This led to some interesting discoveries I thought I should share below. So grab your sonic screwdrivers, absurdly long scarves, throw the switch on your TARDIS and allons-y!
We all know the feeling. You sit down in a Sprint Planning meeting and a project manager walks in. The instant that he sits down you can tell there will be some tension. He wants to do it. He is compelled to. He will absolutely try to force real world hours on your estimations. He lives in a world of black and white and the only justification of the work that you are doing is measured in time. He will take your Story Points, and turn them into something they are not. Time. If you can empathize with the story above, you are not alone. This blog post will talk about tackling the ideology change I believe is needed to ensure accurate estimations.
A Simple Question
One of the most frequent questions that comes up in the realm of enterprise applications is:
Who has touched / modified this data?
Short questions usually have long answers, and this one is no exception. To understand the implications of this question, one has to understand the principle of temporal versioning. This essentially means that time is treated as a dimension over which changes to data are persisted and observed. A full discussion on this topic can be found here. This post identifies a new feature in SQL Server 2016 called temporal tables and contrasts it with the manual process of creating and managing temporal tables in previous versions of SQL Server. Continue reading “Temporal Tables in SQL Server 2016”
As technology continues to advance and more companies start to see the need to stay up-to-date on the “newest and latest,” the more I have become invested in researching ways technology is starting to impact roles in the workforce. As I dug deeper on Continuous Integration to elaborate further on my previously explored “DevOps” path, I stumbled upon this great concept referred to as “Infrastructure as Code” or “Programmable Infrastructure” and it really peaked my interest. This blog post will cover a high level description of Infrastructure as Code and how developers can start taking advantage of it while incorporating it into their everyday tasks.
Hard-coding “magic numbers” in your code has always been a problem for several reasons: they’re not meaningful, they’re difficult to search for reliably, and the chance of using the wrong value is unacceptably high. The first improvement was preprocessor macros in C: