Seriously, play games like DDR, or Rock Band's drums, and you can get a heck of a good cardiovascular workout. I wouldn't bother trying to get significant exercise at work. Save it for after-hours.
That's a good point. Maybe it would be more feasible to have the server cache the current password in RAM during the mandatory password change process, so it can at least compute edit distance from the previous password.
Or for added fun, have a server dedicated to brute force password cracking. When it gets somebody's password, their account gets flagged for a mandatory password change.
I find that a decent SQL database platform is better for complex data manipulation. Install SQL Server 2012 Express Edition With Advanced Services (it's a mouthful, but it's free). It supports import/export from Excel spreadsheets, and a number of other data formats, and also includes Reporting Services for creating nice presentable reports without coupling the layout with your data storage (as with a spreadsheet).
Some SQL knowledge can take you a lot further than Excel will on its own.
Exactly what I thought of. This is a solution in search of a problem, one which ShockWatch already solved. (No, I don't work for ShockWatch, and I don't even know if my employer uses them. I've never seen them in our warehouse.)
If I print my corporate email, it's on paper, and they can't do anything about it when I quit. Or export the data. Or photograph the screen.
You don't want to hand everybody the keys to the kingdom, but I feel like all the emphasis on securing smartphones is a bit like installing steel security doors when you've got loads of single-pane windows everywhere. The security chain is only as strong as its weakest link, and it's usually not hard to find a much bigger security deficiency that's worth targeting before losing sleep over email on people's phones.
Now, pushing corporate apps can be very useful if you've got a large number of employees, but I'm pretty sure there are options for doing that with iOS and Android.
Yeah, give them a simple task. Something that any reasonable programmer should be able to do in 15 minutes. Then give them a solid hour to work on it. If they can't produce something working in that time, that's a pretty informative result. The time limit isn't a speed challenge; it's meant to be very generous, and act as, "Look, we need to move on..."
Personally, I like to give a few different options from which they can choose freely. Something procedural, something OO, and maybe something in SQL or a functional language. Perhaps a couple different choices for each - around 6 to 8 total. That way you don't run the risk of excluding a worthy candidate because you happened to design some problem they aren't really specialized in, and if they can't handle any of them, that's a nice big red flag.
3. Multi Monitor support was changed (Task bar now goes across all monitors).
You can change this behavior right from the taskbar settings. The default is to put it on each monitor, showing the same things on each, but you can also have it show the active windows only on the corresponding monitor, or switch to the old single taskbar mode.
Seriously, play games like DDR, or Rock Band's drums, and you can get a heck of a good cardiovascular workout. I wouldn't bother trying to get significant exercise at work. Save it for after-hours.
Movement's coming out.
Same. And now I am disappointed.
Yeah, Christ, I'll stick with my Tandy 102. Don't need an external keyboard, either.
Some guy tried to shank me with a RAZR.
That's a good point. Maybe it would be more feasible to have the server cache the current password in RAM during the mandatory password change process, so it can at least compute edit distance from the previous password.
Or for added fun, have a server dedicated to brute force password cracking. When it gets somebody's password, their account gets flagged for a mandatory password change.
Well when I fart in my car, that sucker doesn't go anywhere until you force it out, so I wouldn't be too worried then.
Not if you enforce a minimum Levenshtein distance between the new password and the user's entire password history.
And all the media lobbyists will grease up their dicks and take us to the cleaners. USA! USA!
I find that a decent SQL database platform is better for complex data manipulation. Install SQL Server 2012 Express Edition With Advanced Services (it's a mouthful, but it's free). It supports import/export from Excel spreadsheets, and a number of other data formats, and also includes Reporting Services for creating nice presentable reports without coupling the layout with your data storage (as with a spreadsheet).
Some SQL knowledge can take you a lot further than Excel will on its own.
And you view this as some sort of problem?
It's almost as if there are two subsets of the population, both with differing opinions.
Exactly what I thought of. This is a solution in search of a problem, one which ShockWatch already solved. (No, I don't work for ShockWatch, and I don't even know if my employer uses them. I've never seen them in our warehouse.)
Or worse still, the last.
+5 Sad But True
You can't spell "Pyrrhic victory" without "victory"! Yay!
If I print my corporate email, it's on paper, and they can't do anything about it when I quit. Or export the data. Or photograph the screen.
You don't want to hand everybody the keys to the kingdom, but I feel like all the emphasis on securing smartphones is a bit like installing steel security doors when you've got loads of single-pane windows everywhere. The security chain is only as strong as its weakest link, and it's usually not hard to find a much bigger security deficiency that's worth targeting before losing sleep over email on people's phones.
Now, pushing corporate apps can be very useful if you've got a large number of employees, but I'm pretty sure there are options for doing that with iOS and Android.
I think I'd call them "rallying factions" moreso than communities.
Yeah, but the failover time gets worse the more distance you've covered.
Street Fighter: The Movie: The Game
That's what Scrabble is missing! Power creep!
Distributed Denial of Revenue attack?
I don't know about you, but I wouldn't go anywhere near a "mysterious installation in the Chinese desert". I'm guessing due process wouldn't either.
Yeah, give them a simple task. Something that any reasonable programmer should be able to do in 15 minutes. Then give them a solid hour to work on it. If they can't produce something working in that time, that's a pretty informative result. The time limit isn't a speed challenge; it's meant to be very generous, and act as, "Look, we need to move on..."
Personally, I like to give a few different options from which they can choose freely. Something procedural, something OO, and maybe something in SQL or a functional language. Perhaps a couple different choices for each - around 6 to 8 total. That way you don't run the risk of excluding a worthy candidate because you happened to design some problem they aren't really specialized in, and if they can't handle any of them, that's a nice big red flag.
You can change this behavior right from the taskbar settings. The default is to put it on each monitor, showing the same things on each, but you can also have it show the active windows only on the corresponding monitor, or switch to the old single taskbar mode.