Very nice thread. This topic once a while comes back on our screens.<br>My two cents.<br>After various years of talks with OS and purists and not, software farms, university departments, etc. from back to white visions, passing through grey, I've pacified with my questions about where is the "truth": it is where a solution that solves your needs is. All the rest is personal preference or, worst, hideology.<br>
The need can go from a personal scale to a global one, requiring different approaches if we're talking about a self-employed practitioner, a local administration, a multinational farm, or FAO. Forgive me but I think this discussions are non-sense, because, using the first topic, the is no absolute metric to say .NET is worst then Java,C++,or whatelse.<br>
In these days I suggested a customer to use ArcGIS Server for their needs. The day before I was configuring Postgresql and Geoserver for another one.<br><br>Last line. When I discover new softwares being shared I really don't care very much what technology they used to make, I just wonder if it brings new ideas, solutions, etc. that can help our needs. Recently I've set up an algorithm in Python, taking ideas from three different softwares: one was written in C#, one in C++, and one in Java. They were quite different, but each one brought complementary ideas that helped me to solve my problem.<br>
This is what I like from software sharing.<br><br>giovanni<br><br><br><div class="gmail_quote">2010/3/26 Brian Russo <span dir="ltr"><<a href="mailto:brian@beruna.org">brian@beruna.org</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
On Fri, Mar 26, 2010 at 11:54 AM, Chris Puttick<br>
<div class="im"><<a href="mailto:chris.puttick@thehumanjourney.net">chris.puttick@thehumanjourney.net</a>> wrote:<br>
</div><div class="im">> Terribly off-topic now, so feel free to stop reading...<br>
<br>
</div>Yes.. if anyone wants to ping me offline about this feel free..<br>
<div class="im"><br>
> ...not realising high or often any business value. Business value is where what you expend money and get more in return than you spent. Incredibly easy to measure in small businesses with few employees and a simple business model, harder the larger the business or the more complex the concept of value becomes e.g. in a charity or government organisation. There is good evidence that collectively western economies have spent more on IT than they have realised in value.<br>
<br>
</div>I 100% agree that most IT procurement is terrible. People go after<br>
'shiney' technology that solves an immediate perceived requirement but<br>
do not go through the more expensive (in the short term) work of<br>
really assessing how their IT infrastructure is actually<br>
enabling/supporting their business processes.<br>
<br>
However this has absolutely nothing whatsoever to do with how the<br>
software is licensed. You can make similarly horrible decisions using<br>
open source software… proprietary... whatever. It doesn’t matter.<br>
Remember all the crappy linux based phones out there? They sucked<br>
until we got Android ones. Companies would have gotten better value<br>
using blackberries or something before that time The true reason<br>
people end up in that situation is because the technology they bought<br>
isn’t supporting their business properly. It’s like buying a gym<br>
membership you never use. Does that mean the gym sucks? It might, but<br>
all it really means is that you're not getting value out of the cost<br>
you expended. It doesn't tell you why.<br>
<div class="im"><br>
> The business case is not simple, any more than it is in marketing; but here's my base position in simple terms. I select solutions that maximise our future choices and reduce our costs; a further benefit is derived if I can move any remaining costs from fixed annual overhead to per employee or pure capital; while there may be short term pain as people get used to the changes, any increase in costs for that short period will be more than offset by the long term decrease in costs and increases in flexibility for the organisation.<br>
<br>
</div>This is where I disagree with you. If you focus on cost as the thing<br>
to reduce you will more often than not lose. Lowering cost should be<br>
an incidental outcome that happens as a result of increasing value and<br>
efficiency. It's quite possible to end up spending more money on IT<br>
than you were in the first place (more frequently you end up spending<br>
it in the right places instead of the wrong and net overall IT<br>
savings) - but if your overall business value has increased more or<br>
commensurately then spending more is probably the right outcome.<br>
<div class="im"><br>
> Luckily for me I don't have to justify to others other than in my long term results. I'm aware that this continues to be a rare privilege for the top of the information systems tree and that many organisations continue to not have technical expertise at the highest level, resulting in many decisions in that area being taken with the wrong information and wrong motivations. I'm working on that too.<br>
<br>
</div>I would instead argue that the main problem is a lack of<br>
differentiation between CIOs and CTOs. Most organisations involved in<br>
IT are still primarily technology-driven in terms of their procurement<br>
- rather than remembering that their IT is only a means to an end<br>
(supporting business processes & content).<br>
<br>
Running a cheap subversion + trac server on Linux is better than<br>
spending $10k on some proprietary software with more substantial<br>
hardware requirements. However an even better solution may be to<br>
outsource it to someone else and pay them $20/month to manage it all.<br>
As long as they support my business process (managing code) and I have<br>
no other reasons to insist on a specific platform I may not really<br>
care. Shifting host providers down the road isn't really a big deal so<br>
even if they're basing it off proprietary software that's transparent<br>
to me. I have my cake and eat it - I pay someone $3/month to host all<br>
that stuff for me using subversion + other tools.<br>
<br>
Look at it this way - do you care if your ethernet switches run<br>
proprietary firmware? There's fundamentally no difference between that<br>
and an operating system if I abstract my processes sufficiently. Means<br>
to an end. I realize the real world is a bit muddier, but the point is<br>
to focus on what's important - your information and process continuity<br>
- NOT the system it 'happens' to be running on now. Assume that will<br>
change and plan accordingly. So when you say that you think .Net is a<br>
bad platform to base systems on - I understand your reasons elicited -<br>
but you're acting like a CTO, not a CIO.<br>
<div class="im"><br>
<br>
--<br>
Brian Russo / (808) 271 4166<br>
_______________________________________________<br>
</div><div><div></div><div class="h5">Discuss mailing list<br>
<a href="mailto:Discuss@lists.osgeo.org">Discuss@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/discuss" target="_blank">http://lists.osgeo.org/mailman/listinfo/discuss</a><br>
</div></div></blockquote></div><br>