Tuesday January 24, 2012 at 12:51

SR Development Podcast #2: Technology Shift

This is show #2 of the Development Podcast. The search for a name that is not completely lame is on, and I am continuing my education in the art of podcasting.  Along with software development, music and technology, I have a related interest, even passion, for audio recording and production technologies, which is part of my motivation for podcasting—combine things I love to do and work with, and talk about them.

That said, this week we discuss technologies that I will be focusing on this year and why they are important or relevant.  These technologies include:

Web/Internet Development

  • HTML5
    CSS3
    HTTP

Functional Programming

F#
Haskell
OCaml
Lisp

Mobile/Device Development

Android
—Phone
—Tablet
—Googel TV
—Other

iOS
—iPhone
—iPad
—iPod (Touch)

Windows
—Phone
—XBox

Show Links:

Xamarin.com

Appcelerator/Titanium

Windows Phone

Functional Programming

Tuesday January 17, 2012 at 22:00

Process

This is show #1 of the Shepard Road Developer Podcast, a.k.a. I don’t have a name yet. In this kick-off episode, in addition to an overview of the ideas behind it, along with some beginning podcaster rabmling, the discussion is on the importance of defining a development process and developing routines and habits around that process, whether you are a professional or hobbyist developer.

Monday January 09, 2012 at 21:53

Sunday December 11, 2011 at 9:18

Google’s 3 Top Executives Have 8 Private Jets http://ping.fm/i42I2

Saturday December 10, 2011 at 20:24

CodeSOD: The Andy Pattern http://ping.fm/mrR0D

Friday December 09, 2011 at 11:57

[Flash 9 is required to listen to audio.]

ojezap:

I was on Saturday Night With Esme Murphy yesterday to talk Christmas gadgets, primarily new tablets like Amazon’s Kindle Fire and Barnes & Noble’s Nook Tablet.

I recently reviewed the former, while Esme recently purchased the latter.

This post was reblogged from Julio Ojeda-Zapata: Tech writer. Nerd. Boricua..

Saturday December 03, 2011 at 17:52

Sorting It All Out…

The past few months have been a time of craziness and chaos professionally, with a fair amount of frustration but also tremendous learning. There are so many light bulbs going off in this rapid-fire brain of mine that I am fighting the urge to chase each one of them, which is why I am trying to step back and put some perspective on all of these things—ideas, inspirations and a generally overall feeling of excitement about the technological landscape today and the endless opportunities that are evolving from its growth. I honestly believe that the times we are in today are the beginnings of an era that will make the internet boom of the late ‘90s a forgotten blip on the radar.

Take all of this and lay it out in the context of the challenges in the world, both globally and the one around us, and there is limitless opportunity to contribute to efforts to address these issues and have an impact for the better. I have been in the healthcare space for several years and have struggled with the enormity of a system that is clearly broken, yet in the middle of that brokenness lies opportunity to fix at least parts of it. While I have been struggling, I have been realizing that it is in the middle of the circus that I call my job, complete with clowns (morons is a common descriptive noun that is used) and monkeys flinging s#%*, (with my team routinely cleaning up the mess), that there is an incredible amount of knowledge and experience to be had.

My team is a small one, and up until recently I was the only developer. We have added 2 developers in the past 6 months, which in itself required a complete re-design of the development process and release cycle. That alone has been a huge opportunity for learning as the development lifecycle has been maturing from a single dev slinging code to multiple devs working against the same code base…and that opportunity is not even directly related to the industry that I work in.

I do have the advantage of being the lead developer on a team that is relatively small, which means that I am able to drive and implement ideas and methodologies with little political resistance, and point the team, which is growing, in the right direction and to do things right.

In upcoming posts, I will be sharing more of my experiences and more detail about the incredibly exciting times we live in as IT professionals and the low-hanging fruit that is the unparalleled access to technologies and communities of like minded developers. From open source projects to perfecting the craft of software design and development, there is so much to choose from. However, these times are accelerating, and the treadmill we walk on is speeding up from a brisk walk to a full-out run, requiring a mindset of continuous learning, expansion beyond the religious boundaries around platforms and languages that have been common in the IT community and a willingness to not just show up to work, but to think beyond 40 hours. I believe it will only be those that really love what they do that will survive in this brave new world.

Saturday December 03, 2011 at 17:51

T-SQL Table Column Lookup Query

Here is a quick snippet of T-SQL that I use to find the column names in a given table in SQL Server:

SELECT ORDINAL_POSITION ,COLUMN_NAME ,DATA_TYPE ,CHARACTER_MAXIMUM_LENGTH ,IS_NULLABLE ,COLUMN_DEFAULT FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_NAME = ‘table_name’ ORDER BY ORDINAL_POSITION ASC;

Just replace ‘table_name’ with the name of the table you want to get information about.  This is extremely useful especially when the list of columns is large and I need to access data on a field by field basis for transformation, comparison, etc…

Tuesday October 11, 2011 at 19:25

Subversion 1.7 is out

2011-08-31 — Apache Subversion 1.7.0-rc2 Released

We are pleased to announce the release of Apache Subversion 1.7.0-rc2. This is the first public release candidate of Subversion 1.7.0 (rc1 was not publicly released). It is thought to be free of blocking issues, and if none are found will become the final release. For this reason, we encourage thorough testing in as many environments as possible. This release candidate begins the four-week “soak” period to allow for further testing, and barring show-stopping bugs, the final 1.7.0 release can be expected on or near Sept. 28.

Please see the release announcement for more information about this release, and the release notes and change log for information about the 1.7.0 release.

To get this release from the nearest mirror, please visit our download page.

Friday September 30, 2011 at 10:49

Outsourcing Is Not A Corporate Culture Change Strategy

I need to preface this post by saying that I believe that there are times in the life of every company that require significant change—transformational change. In fact, this type of change should be at the core of any organization that wants to innovate and even survive in today’s world. Sometimes this means cuts when the existing resource base does not fit into the new model. I do not believe in job security, nor should anybody in the workforce today—that is a dangerous mindset to adopt. However, the culture of a company is a driving factor contributing to the success of any organization. This is the angle, the starting point for the following observations about outsourcing models. I also need to qualify this as well by saying up front that these are my own personal observations, and I do not claim to be an expert in the study of corporate structure, culture or psychology.

Outsourcing as a corporate culture change strategy simply reveals a complete lack of innovation and creative vision. While some would argue that it is not a strategy relevant to changing the culture of an organization, it really is—self destructive, but it is. However, it is all too often overused or implemented incorrectly. It’s typically treated as low-hanging fruit for the bean counters and those driven purely by numbers. In these cases, it becomes all too easy to cut the fat and continue cutting through the muscle of the organization and into the bone. This is irrational and seems to indicate much bigger problems at the core that this model on its own cannot address.

There is a truth in that corporate culture starts at the very top and filters down through the organization. Implementing an outsourcing model to replace existing functions in an organization almost always means someone else loses their job. There is a saying that the strongest rats are the first to jump off a sinking ship, and that holds true with any organization implementing this model, and as these layoffs continue, fear permeates the culture of the organization made up of those who are still employed. This typically results in anger and ambivalence, jeopardizing business continuity.

Fear can make people do irrational things…When the “strongest rats” are gone, and those remaining are driven by fear, they tend to create work that gives the appearance of relevance and value, but is not driven by corporate objectives, rather those of self-preservation. And what about the major initiatives that were in process when the top talent left? Those tend to continue as well, business as usual…the only problem is that those who designed and drove these initiatives have left, and no qualified leadership in those positions remain, leaving the train running at full speed with no engineer. Compound this scenario with the fact that it’s not business as usual for those that remain, rather an environment of fear and duress, which is counterproductive to optimal performance and execution of business activities.

The problem with all of this is that adopting an outsourcing model seems to always neglect consideration of the costs associated with doing so, while simply focusing on all of the money that will be saved and the bottom line. But that is just smoke…where are the savings, and what will the bottom line actually look like after factoring in the drop in productivity and stability of the organization? There is so much more that can be added to this, but the point here is simple: adopting an outsourcing model has costs and implications that are seldom considered when making the decision to do so, all of which have a much longer lasting impact than the savings that are supposed to be realized by this approach.

These types of changes are usually presented under the guise of changing the corporate culture, attempting to rally the troops behind some grand transformational plan which implies that each employee—each person in the organization matters, and that they all add value. At the end of the day, it really isn’t culture change, it’s organizational change; let’s call it what it really is: reorganization. Changing and improving the corporate culture is not the objective, as it is pitched to the worker bees, rather replacing the existing culture with one from the outside.

Page 1 of 5