The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Why not a simple title, like "Classifying Data Using Artificial Intelligence"? And maybe the blurb can be something like, "A simple introduction to using K-Means Clustering for data analysis," or something like that. Then make the first paragraph about types of data and use cases, to draw the reader in to how to do it with K-Means Clustering. No need to scare your users by using big words in the title. The current title tells me it is going to be technical and non-user friendly except for possibly those who are already knowledgeable in the field.
You talk about what and how; but you don't say "why" this subject should be of interest. You need a "hook" to grab the readers' attention … early. Think of something in real life the audience can relate to and how your article / topic relates.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
I edited your subject line - let's keep "rude words" off the homepage, eh? Particularly when they look like something designed to start a flame war if the fanboise don't even follow the link or watch the video (like I didn't and I don't own any apple products) ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
I think it would actually be easier to support unicode in .NET if .NET didn't purport to support unicode.
I'm making a lexer generator that supports unicode and the char datatype is absolutely useless for it.
I have to read unicode data directly as raw bytes just so i can process it properly because the BCL will not give me the information i need about the characters. So much of the unicode information is hidden they may as well have not supported it at all.
Password policies are often just set by the whim of some web dev.
I just attempted to sign into Barnes & Noble site so I could buy something.
It's been about 6 months since I signed in so in their infinite wisdom they told me :
"Your password has expired since you haven't signed in lately."
So, I had to get an email link, and change my password. I tried to use the same one I had previously used and they knew it was the same one. I guess they just checked the hash...hope they don't store the pwd in cleartext.
Think about how dumb this really is. If a hacker had the password then she would've signed in and kept it fresh. But since the password hadn't been used they think it has been compromised in some way. That makes no sense.
Plus, now they used more time of a valid customer / user and I had to update my password generator to use the new key (password manager).