If you are using Windows Phone 8 Lumia devices and wondering whether you will get the next big update of the OS or not, here’s the good news. Microsoft confirms to few consumers over Twitter about availability of Windows 10 in future updates. That’s definitely a good news for the consumers using Windows Phone 8 Lumia devices and everyone will get a big relief.
While Microsoft is working on building Windows 10 and pushing multiple releases to the consumers as part of Windows Insider program, the official twitter handle @lumia recently confirms about Windows 10 for phone devices too.
Earlier Microsoft mentioned about one OS across all it’s devices, there was news about new phone devices with Windows 10 but what about existing WP8.x users? In the past we already noticed that there was no upgrade path set to Windows Phone 7.x users to get the bits of Windows Phone 8, thus currently running WP8.x users were wondering about future updates with Windows 10 in their devices. So, this cloud has been removed by @lumia twitter handle. According to them, all Windows Phone 8.x Lumia devices will get Windows 10 in their phone devices in future. Here you can find...(Read whole news on source site)
I use SQL Server Database Projects to manage my project’s DB schema changes and keep them version controlled. I recently got a new laptop and installed SQL Server 2014 on...
The AllJoyn™ open source project enables devices in close physical proximity to locate, negotiate connections, and interact with each other using peer to peer connections over a variety of transports. I
The AllJoyn open source project provides an object-oriented approach, making peer to peer discovery and connection easy and avoiding the need for developers to deal with lower level network protocols and hardware.
a small sampling of the sort of devices that might fit into such a definition could be:
Light switchesThermostatsAir conditionersVent dampersSmoke detectorsMotion detectorsHumidity detectorsMicrophonesSpeakersEarphonesDoorsDoorbellsOvensRefrigeratorsToasters
the AllJoyn ecosystem expands, one can imagine any number of applications. For example:
Create a playlist consisting of music, and stream the songs to an AllJoyn-enabled car stereo system, or store them on a home stereo (subject to digital rights management)Sync recent photos or other media to an AllJoyn-enabled digital picture frame or television upon returning home from an event or tripControl home appliances such as televisions, DVRs, or game consolesInteract and share content with laptops and desktop computers in the areaEngage in project collaboration between colleagues and students in enterprise and educational settingsProvide proximity-based services like distributing coupons or vcards...(Read whole news on source site)
Originally posted on: http://geekswithblogs.net/theArchitectsNapkin/archive/2014/11/16/feedback-centric-development---the-one-hacker-way.aspx
Erik Meijer got something right in his talk "One Hacker Way
". There's a lot of bashing and ranting... but at the core there also is a precious diamond to be found. It's his admonition to be driven by feedback. As software developer we should focus on production code - and let ourselves be guided by feedback. How true! How simple! But contrary to the audience's belief it's no easy feat. He got much applause when he suggested, attendees who had not committed code recently should leave. People liked him extolling the virtues of "hacking",
of focusing on code - instead of on fuzzy stuff like a process or even talking or thinking. No, it's the code, stupid! Unfortunately they did not get the implications of this, I guess. And Erik Meijer did not tell them what that really, really means. So I'll try to describe how I see what truly and honestly focusing on code and feedback means. Purpose I'm sorry, but before I get to code, we need to lay a foundation. We need to be very clear about why we should produce code in the first place. Code is a tool for...(Read whole news on source site)
Azure Websites Authentication / Authorization (Preview Release) | Microsoft Azure Blog
more details on Websites Authentication / Authorization in this blog post from Byron Tardif
Websites Authentication / Authorization only supports interactive login in this release, we are working on enabling headless authentication in a future release.
this solution is stack agnostic so it works for all the different stacks supported by Azure Websites today, regardless of your site being coded in .NET, PHP, Node, Java or Python and since this solution is provided as part of the platform
Last week, I wrote about splitting a hot aggregate
. Discovering that specific hot aggregate was easy; it would cause transactional failures from time to time.
Long-lived hot aggregates often are an indication of a missing concept and an opportunity for teasing things apart. Last week, I took one long-lived hot aggregate and pulled smaller short-lived hot aggregates out, identifying two missing concepts.
Hunting for more hot aggregates, I could visualize event streams and use my eyes to detect bursts of activity, or I could have a little function analyze
the event streams for me.
Looking at an event stream, we can identify a hot aggregate by having a lot of events in a short window of time.
Let's say that when six events occur within five seconds from each other, we're dealing with a hot aggregate.
What I came up with is a function that folds over an event stream. It will walk over each event, maintaining the time window, allowing us to look back in time. When the window size exceeds the treshold, the event stream will be identified as hot. Once...(Read whole news on source site)
In Android development, what XAML coders call “code behind” is stored in a class deriving from Activity. This is where you will handle the UI events, prepare the view, etc. Just like in XAML, the code you put there is less testable and less shareable but for view code, this is the place to do […]
Today is the day that Netflix has decided to shut down their public API
. They stopped giving out API keys a long time ago, but except for a select few apps, all others are dead…including mine. As I shut it down today I have no regrets. I actually am surprised by how long it has lasted because the road was rocky and I learned a lot. When I built the app, I was trying to build a service that I wanted. Unfortunately without Netflix, I don’t think the service is worth keeping alive. The reality is that
I really believe that every success is built up other perceived failures. The net result of HowToWat.ch is a lot of learning that has served me well and I am sure will serve me well in my next idea (whatever it is). I thought it would be an interesting list to see what I actually learned by building HowToWat.ch: I learned that a one person startup is a lot of work. That finding co-founders is a great idea. I learned that validating your business idea is crucial to success even though as a dev all I want to...(Read whole news on source site)