Personal

Microsoft – Aston Martin for Trying Windows Azure – Desperation?

Posted by Marius Dornean on September 23, 2013  /   Posted in Personal, Technology

Today I received an email that states:

 

Dear Customer,

Don’t miss your chance to win a 2013 Aston Martin V8 Vantage. Deploy a Virtual Machine or a Web Site using your MSDN Windows Azure benefit by September 30, 2013.

 

I was shocked to read that they are giving away an Aston Martin! I wouldn’t mind if this becomes the norm type of prize for trying out providers but this wreaks of desperation.

I personally have a bad taste in my mouth after having tried Azure. Could this be their attempt at recapturing a small percentage of those who gave Azure a try and only walked away feeling disappointment?
Read More

How to Become and Stay A Successful Software Architect

Posted by Marius Dornean on May 31, 2013  /   Posted in Informational, Personal, Technology

What exactly is a software architect anyway?

Software development, relatively speaking, is an incredibly young craft. Additionally, the role of an architect within a software development organization is a very fluid one (same goes for CTO). I believe it is important to understand how an architect fits in the software development environment, both within the engineering and the business organisations, before we can discuss how to become one!

Requirement #1 – Experience and exposure

Let’s image we are equating software development to rope making. The following chart will express the equivalent experience level expected in each of the different position:

Position Relative Experience
jr developer learns about rope
developer can tie basic knots
senior developer calculates rope strength and knows a lot about knots
architect knows more about rope than you ever will
senior architect invented nylon

Read More

Keeping Up With Technology – Learning to Pick Your Battles

Posted by Marius Dornean on September 14, 2012  /   Posted in Informational, Personal, Technology

Prerequisites

One of the questions I get asked most often, from both industry experts and otherwise, is what my strategy is for keeping up with technology. While there are industry professionals who are experts in this matter and can help with creating checklist style approaches, the following is derived from my experience.

As most modern-day software professionals, my fascination and passion for technology started at an early age. Early enough where I had the opportunity to make software development, logical thinking, and the art of continually searching for and acquiring knowledge a part of my personality. I grew up tinkering with computers, learning how to code, and scratching my forehead trying to wrap my immature brain around the concepts of object-oriented programming, router ip tables, matrix manipulation, and other fun technology related topics. I can first handedly attest to the difficulty this poses for a brain who has yet to be introduced to the f(x)!

Yes, abstraction, polymorphism, inheritance, and other fancy words that describe the beautiful world of object-oriented software development sounds scary to those who are unfamiliar with them, but as you slowly delve into these concepts, a true, honest, and remarkable world emerges. In this world, things are black and white, 0′s and 1′s. Things either are, or aren’t. Using incredibly simple building blocks, things such as Facebook, stock exchange trading platforms, and even aircraft auto pilots have been forged.

As you can tell from my digression (something I can’t help but indulge in when on this topic), my expertise is really derived from passion, which is my key focus for this post. I am making passion a mandatory trait to even begin discussing keeping up with technology.
Read More

Communicating Technology Initiative Business Value Across Business Units

Posted by Marius Dornean on September 05, 2012  /   Posted in Communication, Informational, Personal, Technology

Preface

The true value of a software Architect in an organization is the ability to translate the business’ vision and strategy into effective enterprise change, usually starting with the solution architecture. This means that an Architect needs to truly understand the business drivers and how they lead to features at the product level in order to successfully guide a product’s architecture road-map. Inversely, an Architect should be able to communicate both the technical and business aspects of this strategy to any audience, technical or otherwise.

The communication style used to deliver the message to distinct groups varies widely based on the audience’s duties. Technical folks focus on the technological implications of the architecture strategy and are usually more interested in the how rather than the why. If you take a group of developers they would rather know how their specific areas of concern are affected and what they need to focus on.
Read More

^ Back to Top