Last friday I made a presentation about non-metric methods, non-metric methods is a small subject in another bigger subject named: pattern recognition.

you can download the presentation here (zip file, 566KB).

I've found this three articles:
Someone I don't know but I think that he starts with this
Scott Hansleman
Ken Egozi
So I couldn't resist the challenge.

Things I Learned about Software in College

1) Math.
2) Your code should only give the results the lecturer want, this ain't need pattern or not even need to run tomorrow morning.
3) Assembler\Unix\Perl\shell\bash and more other things in computer science that you will never use, but good to know they are there, like the sun, moon and ...

Three things I learned about software while not in College:

1) This is a world of Ego - try to be calm and listen to your friends you don't know everything, in such way you will earn more friends and learn more from people. moreover not every person who make noises of genius (or maybe make noises he knows something) he truly knows it {after all we all need to say something that every one else would know that we out there}.
so first, listen to him\them. Afterwards,  try to dig more to found out if you can use this details.
2) Only time (and experience) make you better, so don't stop reading, coding and talking about architecture.
3) The coder who is sitting near you is your friend love him & hug him after all you see him more than you see your wife\girl(boy)friend\son.

Keep learning

I've finally found some time to explore the nmf format and the AGX capabilities a little bit more than I used to read at the ESRI site.

In my office we made the first installation on production of the AGX in Israel and I'm pretty sure we are the first in the world.
One of the problems with being first - is the lack of knowledge and documentation, moreover this product (AGX 350) has many bugs.

despite all those cons I am very happy with this decision, as I wrote in my last post.

Today I will light your eyes with two properties I found, Visible & HideFromContents
Visible - is pretty straight forward, true - will show the layer on screen, the false - will hide it from your screen.
HideFromContents - is also straight forward but I didn't know it exist till today, this will decide whether your layer will be in the Table of Contents (TOC) or not.

I played a little bit for you - I hope those screen shots will help you to remember this post.

 
{Visible=true,HideFromContents=false} the layer(Bountiful_images) can be seen and can be managed by the TOC on the left.

{Visible=true,HideFromContents=true} the layer(Bountiful_images) can be seen but can't be managed by the TOC on the left (magic-layer).

{Visible=false,HideFromContents=true} there is a different layer on the screen than the layers above moreover you can't manage it using the TOC.

Pay attention that in the last (Visible = false, HideFromContent=true) you cannot see the layer at all, but you can find it in tools -> manage layers .
The problem is that you will never see this layer :). bug or feature, you decision.

Business logic as a bonus:
One of the customers came to me and told me they want to see a specific layer but stop users from managing (showing\hide) it.
To me it sounds stupid, but hey this is the customer decision, and it won't cost me a thing.

Last week we launch our new products, after three months of intensive develop, we finished and gave our evaluation version to our customers.

Our product based on the ArcGis Server 9.2 of ESRI, based on dotnet Framework and using WCF Capabilities for performing intranet Service Oriented Architecture.
I should admit that this buzz-words works, I am not sure why and I can't tell how simple is to implement it, but every manager\team-leader\programmer that heard it has a stupid smile on his face, "Hhaaaaaaa so we can use it too?" yep, this was our intention, write it once, use it everywhere.

One more thing on my mind, our complicated server architecture include lots of business-geographic logic, but it worth nothing, cause managers cannot estimate the time you spent on writing your inner algorithm.
Here are some example:

• We published a coordinate transformer service for everyone usage
• We implement a logic for retrieving\querying maps from our server (imagine a clothing-catalog now transform your thoughts to maps-catalog)
• We can also export Rasters from our DB to every customer
• And we have more other server side stuff that we spent a lot of time on it, but the real people to worth it will probably be the other programmers\team-leaders on the near by office.

Lets take a typical manager\customer, try to explain him all this stuff,
It will sound like this:
Me: We implement a great server side logic, every one in our company could use this it will save the other teams days/months/years.
Customer(thinking): he spending my time and money on other teams\projects?!
Customer(saying): what can I see from it right now?
Manager(saying): Yes, show him something, give him to play with this new baby.
Me: Hmm, no. see, now you can't do a thing but in the near future ...
Customer(hearing): bla bla bla... [feeling angry]
Manager(thinking): How do I hired this stupid

This reactions can vary from one to another, but at the end point, customer can only understand things we sees.
Don't try to sell them server side capabilities, and it is a cool feature that everyone can use it, but you should know what every one need and want to get and you should give it to him.

Here are my tips:

1. Programmers & Team-leaders - we always wanted to do a generic things, cool things and other stuff, so we could smile on our way home, (for example: code WPF on GIS Engines using the DLinq underneath all this while writing coast-to-coast unit test using our new mock object with those cool new TFS features for nightly build&running those tests) - do not give up on those features, it will make you happy after all, but use them wisely.
2. Customers - they have a business logic to catch, we should understand their needs and give them something to play with, not just Doom/Fifa like to play with , we should listen, ask interact and understand what will make them smile when this product will ship.
3. Managers - wants their customers happy and they also want something to play with, something to show their managers and other partners\customers to bring more money, listen them too, try to understand what can help them bring more money.
4. Probably if you will listen carefully you could find a good point at the middle when both the customers & managers would be happy, now start thinking what can help you perform those dreams come through,

How do we did this?
I should admit that we do it unintentionally, but it works just great, We used the new AGX(350 build), it gives us a great UI almost for free, why I am saying unintentionally? because while sitting with the customers (long time ago) we talked about UI and Google-Earth-like, This tool is a beta but probably the worth beta in the world, why? because the customers want it, because it makes the customer-friends happy and when the smile we can blow his chest up and smile every time he plays with it.
about the managers? they can do this too, their customers happy, the project in time, you also gave a great buzz-word the always like to say.
For my team? you should ask them, but for me, I am happy because they are, we use the best technology in the world and keep doing cool things. so why not.
This simple customer-driven technic (you can also call it Agile :) gave our team a lot of time\space to implement our server side code\architecture for further usage of other teams.

One more tip (including example):
For each module you write\design on the server try to give something cool that every one can see. (think about a customer-driven name for this module)
Think about the SOA-team that is doing the hard work which no one can appreciate. Show the managers something, do it simple, with minimum time, just do it COOL, well-designed. try it to get to their business-logic.
For example:  If they need to travel around the world and you create a great logic of minimal distance (shortest path), implement it on a simple map, you would probably do this for your own experiments so just publish it so every one could see this.

Enjoy, Relax, Freedom.

I finally found time to test the LiveWriter(Beta) and this is my first test to add a post to my blog, It looks pretty cool and easy for now.

                                   Me Editing this post using my new LiveWriter(Beta)

I'll probably have more thought later.

I've Added new capability to my blog, this called Snap Preview Anywhere.
You probably see this before in some Web2.0 sites, but I was surprised how easy is to add it to yours.

I like this new feature of mine :).

You should try this too.

P.S. 1
This cool feature of snapshots is enable only on the left panel, (links and blogrolls).
I should check why this ain't work on the main page, I think that dasblog saves its links using *.ashx instead of pure href.

P.S. 2
I would like to hear your opinions about this feature and other recommendations for new features.

We are using the Team Foundation Server and we start using the Code-Analysis in our build process.
Migrate Code-Analysis: this option migrate a predefined Code-Analysis rules, so the team-leader can create a template Code-Analysis rules (from now on will be called: Team Code-Analysis) each programmer should click the Migrate Code-Analysis on his solution, (the result on the local solution will be called: Programmer Code-Analysis).

From MSDN: "The ability to migrate allows you to stay synchronized with the settings on the server.".

My co-workers told me that even when we create an empty Team Code-Analysis they still get annoying warnings for Security Rules, Usage Rules and more rules that I didn't turned on. After playing on and off with our solutions I found out that the migration will save the most strict rules.
for example:
 Team Code-Analysis: only Naming Rules
 Programmer Code-Analysis: Usage Rules
 At the end: the solution will have them both.

This all not so bad, the real problem starts when I changed the Team Code-Analysis templates:
We start the project with full rules, but realize very quickly that we cannot have them all, so we turned off most of them, and today we have only the Naming Rules.
But the solution itself: still holds the strict rules, so it will hold them all.

I am pretty sure that such behavior is by design, but I think that this one is not the best choice. why won't you ask me what I want to do with my migration...

One more tip:
If you have issues like this, it is not a great fun to tell all you programmers\Co-Workers to turn off the unwanted rules (each solution * each project).
The pragmatic approach: Those configuration will be saved locally under your BIN directory inside a file named: AssemblyName.dll.CodeAnalysisLog.xml, so all you should do is to make a sample solution and sent it to everyone, including a simple batch with xcopy to the right folders.

Enjoy.

We created a bunch of DLLs which we would like to share between different solutions on our computers. We thought that gacutil.exe all alone is enough, probably not.
When we tried to find the file under the .NET tab - we couldn't find it, but the it was registered to the GAC.

I will start by showing some ladybugs:
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=105471
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=105884
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=111950

Those ladybugs help me get better understanding of this issue.

I searched a little bit and found out two ways to resolve this problem:

• The first solution is to put a copy of your DLLs in the VS IDE Directory (C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727).
• The second solution is to create a sub key under: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NET\AssemblyFolders] and insert the real directory path to its value.

For me I prefer the second idea, this look more organized, and you can get better management of your DLLs.

After you will make one of those you could simply find the Assembly in your "add reference -> .NET tab.".

Three new Bloggers are in town, they all my child, I love them all and each one of them has a lot of good stuff to share with you.

Doron Yaacoby, Yossi Shmueli (aka YsA), Yoav Michaeli (Hebrew).

I wish you all luck and love.

I am not sure yet what is the problem, but I have a strange syndication error, I read Oren's post about his Syndicate bug but I found out that mine Syndication error occurs even when I simply write and publish. like this post (which did not saved before published).

Oren even check with Scott Hanselman but they couldn't reproduce his error.
I'll check my xml files and and keep updating later on.

As you already know my team works on ESRI products, which are off-the-shelf products, we have daily battles of understanding and solving performance issues. the main challenge is to understand where in our branched architecture the problem.
I already wrote about this ESRI processes and the "Process Explorer" I also called this Debugging the unknown.

I always said that we all good programmers, we all know to write (more or less) readable code, but most of us lack the understanding of how things are working at the background. The difference between a good programmer to an expert is that the experts truly know what is going on behind the scenes.

Last week Liran, talented boy from our Unix team, shows me this magic: Cacti.
Cacti is an RRDTool which can help us gather important details about the OS functionality and its background operations.
I am still not sure what we wrote their in his scripts, but I saw that it was short&easy to write new scripts.
The real cool thing is that creates an intranet site, which makes this easier to connect, it runs in front of our UNIX\Linux servers. I know how to run some cool scripts in UNIX, I also wrote some scripts using shell\bash\kshell, but this is better, you can get everything using graphs, and do not need to remember even you DB server name.
We are using Cacti to monitor our SDE server (Linux) and our DB Server(Oracle 10.2 on AIX5.3).

Two days later, we return our investment, when we had two crashes because of Virtual memory, you can easily see that in those graphs, which saves the history in MySQL DB.

Again, It won't solve all your problems, but you must understand that without such tools you will spend hours on hours when your DB fall again and again.
With such tool you can also predict errors when you are doing you exams at the development phase.

I would like to hear about more tools you know and use.