Cas Bitton wrote:XViper wrote:You hold things back until EVERYTHING is ready to go.
Risk assessment when delivering a product within a fixed timeframe is also part of that process. You can't just make arbitrary delays because you feel like it.
From the feedback I've seen from your community, and how I personally feel, the delays or reasons for them would have hardly been "arbitrary".
Cas Bitton wrote:XViper wrote:Car manufacturers don't go releasing new car models if the ENGINE isn't safe and reliable? Like seriously......
And here come the car analogies

Fair enough. Didn't put alot of thought into it, but analogies are always good.

Cas Bitton wrote:XViper wrote:You don't?
Where do your files sit?
What file system?
What OS?
Almost every Server OS I know of has a managable folder structure.
I don't understand :\
The answer to this isn't really that relevant, it has little to do with the file library management. Well, from a customer experience/delivery POV.
I think it has some relevance. I guess my point is, the previous system made sense. It had a flow to it. Your users are obviously on computers, most of them probably Windows machines. People are familar with folder structure. Folders and files being inside other folders. This is what you had before, a structure. Now you don't.
If you as a server admin have a system in place that makes the content easy to manage and sort, then you need to apply a similar logical approach to the system the end-user has to use to navigate that content. Of course if your backend is **** or non-existant, this point is moot. Which appears to be the case at current. (your point below)
Cas Bitton wrote:XViper wrote:How do you manage the file content?
By using a combination of web tools that have been internally developed over the years

. At present they are being reworked and reintroduced to work with our current website.
These tools are unavailable to me at this time.
I guess again my point is they should have been completed and ready to work with the current website before it was developed.
I work in a University IT environment. We make large modifications to server content all the time. You would NEVER introduce a new system without the ability to maintain and manage it. By the sounds of it, this is essentially what you have done.
These changes aren't the end of the world, but I can't help but feel you guys seriously screwed this one up. It seems like one big massive mistake. One which; knowing you Cas, I don't believe you wouldn't have taken a different approach to many of these issues.
Edit: Just noticed your edit:
Cas Bitton wrote:At some point Tim and I are probably going to have to slow down when it comes to replying to a lot of these topics, I mean it's great and I'm happy to answer questions all day....but we still have a lot to take care of eg: fixing things instead of being reprimanded by the public for our failures
We have spent a significant amount of time over the past week addressing community concerns, feedback and responses alongside a lot of really great progress. At the end of each day It's awesome to see things are shaping up!
I apologise if my comments have come across as being "reprimanding", it's certainly not the intent. I also did'nt expect you to be replying so promptly. Cas; I have a great deal of respect for you and your positive attitude towards almost everything, regardless of the negativity around you. I'm just really surprised that what seems to be such a massive cock-up, happened on your watch. I'm also really surprised that Tim especially seems to be saying how everything has gone exactly as he wanted, everything is great, and there are no regrets on moving forward as you did. I honestly can't see how you can look back on this deployment and go "Yeah... that's exactly how I wanted it, and wouldn't do anything differently."