Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
And that was after servinging 6 years (of a 9 year stretch) for armed robbey. He did the 6 years in dartmoor. Loved it inside - free grub, nice people - came out very much rested.
With mates like that, why does your mother's boyfriend bother you?
Drivelling in TPD is not a mental health issue. We're just community blogging, that's all.
There's no excuse for URLs that contain ridiculous amounts of incomprehensible metadata exposing inordinate quantities of irrelevant information concerning the server-side technologies and their needs
Some people feel that I'm overly strict about this, but IMNSHO, there shouldn't even be a ".html" (or, for the sad fscks who still think a Windows server is adequate, ".htm") extension on the end of a resource's name - it may be a static resource now, but it could become a dynamic resource in the future, and although it's easy to create a dynamic resource that still uses the ".html" extension, that would also be misleading, in that it would suggest that the dynamic resource was a static file.
Some people feel that I'm overly strict about this, but IMNSHO, there shouldn't even be a ".html" (or, for the sad fscks who still think a Windows server is adequate, ".htm") extension on the end of a resource's name
So what you're saying is, if the URL is simple and meaningful, it is memorable and predictable. URLs should be user-friendly:
Anyway, supper's ready - I think it's just thee and me here now BI, so nighty night, and may you have a lucrative, and maybe even rewarding, week at YourClientCorp
Comment