Skip to main content

It's Companies too!

In software development, we struggle with our own thoughts for the directions we take.  Strive for the shiny new object to develop with?  Use our current tools or take a risk on a newly released tools for new project?  What is real and what is driven by our desires and personal wants.

We like to think that we make rational decisions but we don't.  We fool ourselves by pretending contraary evidence does not exist or apply for the decisions we make. This can get us in to big trouble.

This is not limited to indivuals but to companies as well.   Google has been denying that fragmentation is a problem with the Android ecosystem.  That what worked for the phones would work for tablets (it doesn't).  Adding fragments that require even more resources, id, files and references should work fine for larger screen sizes (it doesn't).  Tablets are just like phones except we can just place more of the same existing views on the screen at the same time, it will work fine (it doesn't).  Tablets are different.

Facebook knows HTML, JS and PHP, so it decided to build it's mobile applications with these tools instead of going native.    What's good for the web is good for the device (it's not).  Now they are reverting back to going native for iOS.  They can fool themselves but they can not fool the users.

The read up of Palm when creating their new OS for phones is a fascinating reading.  No-not WebOS, the one before WebOS that failed when WebOS was quickly put together to get something out.  The story of Nokia and it's OS decisions.  Even Microsoft and the reasoning for Windows 8 RT (on ARM).  Very interesting stories and justifications.

The desire to justify your choices by pretending that major issues do not really exists or somehow do not apply is not limited to individuals but also companies.  It just the different side of the same coin.

The main difference between personal and corporate choices is the possible impact on others.  I accept failure (and even expect and learn from it), but company choices have risk for other employees that have not say in justification (or self deception) that is used for major directions.

There are times the risks are worth it or when major changes are called for (thinking of RIM here) but it's important to understand why decisions are made and the personal thoughts that go into them.

Should companies have a couple of Buddhists on staff for reality checks?


Comments

Popular posts from this blog

My Current Desktop and Happy Vining.

It's been a big switch when I quit my old procession (Software Engineer) and ventured into the unknown.  So this is my current desktop.   First it's a REAL desktop and not a computer screen. Second, I've had to learn a whole new set of tools.  You would think a pencil is just a pencil and a paint brush is just a paint brush, but noooooo, they are tools into you mind and that's what needs re-tooling. The tactual nature of these tools and operation as much more rewarding (and frustrating too) than typing code in an IDE.   That had it's incentive but that well went dry and life changes,  so I changed. The pleasure of creating colors (no RGB involved) ad hoc wise is interesting.  Getting the technique to merge them on paper is very tough.  You do not know what you're going to get, so you just have to go with it. I'm glad that I can do a lot of other things instead of Software, but I hope that others in my past procession work on other pa...

3rd Try is a Charm

I've been trying to draw / paint these barns for a couple of years but never felt or got them right.  This time I think they turned out right. So What went wrong before and what's right now with this drawing?  This time, the light was right.  It's coming from the upper right and the shadows just looked right.  The other thing is the corn field on the left had to "be in season", otherwise it's just a plowed field.  I had taken other photos from different angles but they never felt right.  This angle has the road, power lines, corn field, etc. all leading to the right.  The shadows on the lower right helps fill in that corner (don't forget about the corners!).  The last part is trying to draw (ink paint maybe) the trees in the background.  Not so easy when they are kind of a blob is green shades. So yeah, it's composition that is king.  Many times I just don't see it until the drawing / painting is finished and when it's right it feels goo...

Thought Patterns

I know how I work.  How a think about, visualize a problem and go about mentally design a solution and implement it in code.  My thought pattern works pretty well for me on most occasions, but not always. There are times when I have a force myself to change my thought pattern because of the problem I'm solving requires a different mindset.  Anyway, this posting is about how I work most of the time.  Here is goes. I quickly break down a feature into operations that are required to exists and tackle that code first.  My thinking is that, if I can solve the primary issues first, then secondary features will fall into "known knowns" and I can address those at anytime (and sometimes at my leisure) and this allows me to meet my internal timeline. If I addressed features and operations that are not primary first, then I feel I risk my (and the projects) timeline without addressing issues that allow the feature to operate.  You may have seen this occur where...