Mono-Culture -vs- Strength

There was the potato famine of Ireland, there was the Wintel consortium. Both examples of mono-culture where the majority share holder of a segment (food and tech) is owned by a single player. Sound good, easy to get used to, lots of benefits and, for a while stable. Also very fragile and prone to sudden collapse.

The Irish had it's potato blight. The Wintel consortium has fought off virus and malware (see a pattern?) to a draw only to be quickly overtaken by a new evolutionary animal (mobile / tablets). No external asteroid needed, it's just a mono-culture, it's going to happen.

You see the same desire in the mobile OS market share today. Android was all the market share, iOS fans want the market share for them, and Window, well Windows would like to be in the game.

But the truth is that the complete market is stronger with a mix of OS's in the market. Each with their own strength and weakness. This a plus for everyone. Each being the favorite in different sub-sections of the market with also being an alternate if a gap opens up or if another OS missteps. It's a strength, not a weakness.

The same for the development of software. I'm a native engineer at heart (Java:Android, Objective-C:iOS, etc.), but while these have their strengths, there sub-markets where other development tools are stronger. A mono-culture of tools is bound to collapse in time.

Personal engineering styles, development processes, design, religion, communities, etc. are all the same. There is no one player that should dominate or should dominate.

Diversity is strength.

Comments

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...

A Person, Artist, Software Engineer, Geologist.

Search This Blog