|
I think that it was unnecessary to remove the Start button, but i aggre that removing the Start Menu and replacing it with the Start Page was a good choice, althought i believe they must have implemented it as a more direct replacement of the Start Menu (yep, with folders or categories and all), because, sometimes, not everything i install ends in that page (for example configuration files, or help files), and not everything i install is needed in that page, a lot of unnecessary and disorganized apps lie at the end of it and i need to organize it to make them useful.
|
|
|
|
|
Right-click on an empty area of the start screen, and click the "All Items" button that appears at the bottom. I discovered that on accident when I was looking for the same thing.
Which is a major part of the problem I've had with Win8. In their quest for "simplifying" the screen, they've eliminated so many visual cues as to where things are, that I've found many of them "by accident". There's an excellent video floating around on YouTube where a guy showed his father Windows 8 (Customer Preview), and he spent 20 minutes looking for the "Start Button". There's nothing on the screen that tells you that you need to move your mouse to the lower left to bring up the start menu. There's nothing telling you that you need to right-click on an empty area of a web page to bring up the Metro version of Internet Explorer's tab menu, address bar, etc. There's nothing showing you that you *can* snap windows side-by-side, let alone *how*.
Besides that, I may be comfortable experimenting with the system to see what it can do and how it works, but (1) I'd rather spend my time *doing* instead of trying to figure out *how* to do, and (2) my mother certainly won't be, and will be very confused as to how to do things (even if they have a "tutorial" when the OS first starts, do you think anyone is going to remember everything it has to teach?).
|
|
|
|
|
Thanks, for the hint, my only gripe with the Start page right now is that it automatically puts there every program i install without order or logic there.
Regarding the video, i've seen it and it remarks very well that changes like that without proper training (or tutorials) can be disorienting at first, my own experience: i found pretty frustating in the Developer Preview the way the "Start button" worked and i wasn't able to hit it properly in the first week, after that i accostumbred to it.
Also there is another video, i believe is in one of the Windows blogs, but i don't remember exactly where, that shows a user testing Windows 95, and is pretty much the same history.
|
|
|
|
|
Reading the Steve Jobs biography, I was impressed with an anecdote about an illiterate boy who was able to pick up and start using an iPad without any instruction. I've also noticed my own kids use my Windows Phone and my wife's Android tablet. While I'm sure a large part of it is how little kids have no fear of trying new things to figure it out, what struck me was how truly intuitive these devices are, how they are usable without any instruction.
Windows 8 is going in the wrong direction. For all they talk up how "intuitive" it is, the fact that they are having to put in a tutorial for the most basic functionality is completely backwards.
|
|
|
|
|
I have really mixed feelings about it...
I really like Win 7, even with the changes that made a few things more difficult (security). I have a Windows phone and love it, so I was really looking forward to Win 8.
I have a home built Media Machine for my auto. It uses a 7" touch screen 1024x768 resolution. My media machine currently uses XP and will probably be using XP until it dies of old age. Here's why...
I installed a fresh drive and Win 8 Release Preview. After some playing I was able to get the touch screen drivers to work, kind of. I realize this is the fault of the screen and/or driver, but gestures don't work. The screen is so small that trying to do anything with your finger other than launching an app on the metro screen is impossible: the scroll bar at the bottom of the metro screen is very difficult and getting the cursor into either hot-spot cannot be done.
So I tried using it with a stylus, which won't work well in a vehicle by the way (think bumpy road). The scroll bar can be used, but I still can't get to the left-hotspot.
For this application, Win 8 will not work at all, unless I 'hide windows' with an all encompassing user application. Then it doesn't matter what the OS is.
Before removing the Win 8 drive and replacing it with the original XP drive, I tested it with a desktop monitor, keyboard and trackball. It took a little getting used to, which I expected. The extra clicks to do some things when using the desktop is annoying. other than that I liked the desktop experience.
I have no opinion on using it on a tablet because i haven't tried it.
My 2 cents.
|
|
|
|
|
If you can’t get to a conference, let the conference come to you! There are a ton of free recorded conference presentations online... Coming soon to a cubicle near you.
|
|
|
|
|
There are a lot of good webcasts from Microsoft.
|
|
|
|
|
What about free beer and useless toys? It's not a conference if I haven't won yet another USB-powered rocket launcher in a Gran Turismo contest.
|
|
|
|
|
Second
Sincerely Yours,
Brian Hart
|
|
|
|
|
As if the level of social interaction we get wasn't bad enough already.
|
|
|
|
|
Historically, the lengths of text messages were usually limited due to technical reasons. For example, the data packets holding SMS messages only had room for 160 characters (see below). Now that those technical reasons matter less, people are recognizing that limits have other advantages. I would have written a shorter letter, but I did not have the time.
|
|
|
|
|
Definately on phones don't want long messages, and I do like short emails on some topics.
|
|
|
|
|
This post describes the relatively undocumented API for debuggers (or other low level programs) that can be used to enumerate the existing threads in a process and receive asynchronous notifications when threads are created or destroyed. This API also provides asynchronous notifications of other interesting thread-related events and feels very similar to the interface exposed by libdl for notifying debuggers when libraries are loaded dynamically at run time. Understanding this might also help unravel the plot in Primer.
|
|
|
|
|
The difference between a bad developer and an average developer is small, but the difference between an average developer and a great developer is enormous. It’s an ocean of difference. A great developer is 20x more valuable than an average developer, easily, and so it’s critical to hire one great developer, instead of 20 average developers. Help us Rockstar Ninja Developer. You're our only hope!
|
|
|
|
|
So I posted a comment on his website and he didn't like it so now he's blocked me from ever posting on his blog. I wasn't even that rude. I only asked where he got the 20x number from and suggested he made it up. He doesn't, apparently, have the courage of his convictions and felt it better to delete my post and ban me rather than try and answer my questions.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
nils illegitimus carborundum
me, me, me
|
|
|
|
|
Rockstars sometimes have huge, but fragile, egos.
|
|
|
|
|
I take it these are your posts:
"•Mark
What a pile of festering crap. 20x? Really? Where did you get that number from? Thin air is my guess. There is no objective way to decide who is a great and not so great developer. It can change with time and project and by the people you are judged against in the team you happen to be in at any given time. And you might be awful at distinguishing great developers because you’re a self-obsessed and talent-less twat but some of us have gotten reasonable enough at it not to keep hiring morons. Keep your mouth shut and let people think you’re a fool; open it and let them know you are a fool.
•John
Seriously? You think by deleting my post that makes you right? You’re not right: you can’t just pluck a number out of thin air and not expect to be lambasted for it. Still, I suppose you’ll delete this as well – your ego must be terribly fragile if it can’t take any criticism."
|
|
|
|
|
Your point?
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
nils illegitimus carborundum
me, me, me
|
|
|
|
|
No. I'm assuming they are your point, not mine. I found his article too poor to even summon up the energy to be apathetic about it.
|
|
|
|
|
They are indeed. Normally I don't bother but I am 86.7% against people who make up random numbers or statistics to make a point.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
nils illegitimus carborundum
me, me, me
|
|
|
|
|
I'm 15.2x more likely to agree with that point than with a poke in the nose with a wire brush.
|
|
|
|
|
|
20x seems too high to me. I seem to recall that it's been measured as 10x difference in productivity between different ability levels (I forget where this stat comes from, probably Mythical Man Month, Code Complete or Joel Spolsky, or maybe a combination of all?)
|
|
|
|
|
TLDR version: good developers contribute code, bad developers contribute crud (not "create, read, update, delete").
|
|
|
|
|
I kind of agree with the article but the 20x figure is completely arbitrary. To me good developers along with getting the job done also consider future implications of their actions. There are too many developers who get their immediate tasks done, only to stock your codebase up with future WTFs as soon as you need to reuse a part of it.
|
|
|
|