Been a 12 year system coder on Win/xNix. Coded working demos for 128 byte compos in assembly in old days, versatile in asm/C/C++/C#, got to know Delphi along the way, VB enough to translate to C, etc, but most of what I did for production purposes was Web related (ASP, PHP, .NET, anything capable of JS), Oracle, MSSQL, MySQL... Been a developer, team leader, project manager too. However, my employer insist that I stay support for clients just because I know English well and can talk to them without insulting them. I hate being a support, but in area where I am there are no better jobs and my employer is seeking about 12 senior positions on market I'm more than fit to fill. Of course, they ignored my numerous requests to advance. I had one "promotion" from senior analyst programmer to head of support & maintenance, where I got two additional team members, of which one was C# expert, but it turned out that she doesn't know that C is case-sensitive language. In 5 years of service I had no salary increase. Say, what would you do? In my area, company I work for is like a Microsoft, but I feel as welcome desk receptionist there. I keep forgetting what I knew and am learning nothing new, but salary is good - the only reason I keep reconsidering over years. Boss is the girl straight from collage, no experience, but drives a team of ten (given unto her for reasons unknown) and insisting that we share knowledge, which she doesn't have. I know this is a developer's hell, my personal hell for sure that I don't wish for anyone. But job pays well. What is the tradeoff in your opinion?

modified on Monday, July 7, 2008 11:16 PM

But you can have paralellism with SATA - put two SATA drives in RAID stripe :)

Totally agree. We all used that one way or another all these years. I just wanted to learn about experiences how such site could be made available for search engines.

Here's a question for you all - I'm working on a commercial web site and I've chosen to go the Ajax way in it's design. All went well, but now I've somewhat hit the deadend when I got to the point where client has a problem advertising the site. So, what I'm interested in is - in your experience, what are the best practices on advertising an Ajax site and make it appear on a common search engine? Obviously, the site doesn't have many pages (it's virtually one page in total that can be directly called - default.aspx) and content is exclusively dinamycaly changed. Also, having no links to point to certain URLs, but onclick events, makes extremely hard for any search engine to pick up any other content except the starting page. The site is not live yet, but having this in mind, for a commercial site, I'm not sure if I should leave it as it is or start splitting pieces of it into iframes or otherwise. Last thing I would want is to make a technically superior site, but that will fail to acheive it's primary objective. Any taughts?