don't be so hard on him, if he'd read the book (get it book, preferably a big thick one like any introduction to.NET book) then he'd have his solution solved.
Books are good, though he might need to read a 2nd one to reinforce his now-elevated vision of a solution.
4 hours is too high for the average, though we can easily imagine some people watch more than that.
The Bureau for Labor Statistics says the average in the USA is 2.8 hours per day.
Watching TV was the leisure activity that occupied the most time (2.8 hours per day), accounting for about half of leisure time, on average, for those age 15 and over. Socializing, such as visiting with friends or attending or hosting social events, was the next most common leisure activity, accounting for nearly three-quarters of an hour per day.
That said, individuals aged 15 to 19 also used a computer for leisure for 1.2 hours a day, so that adds up to 4 hours, we've just shifted our attention away from TV to other video-based entertainments.
somewhat counter-productive, cut my wages and i too will work about as effectively as a H1B worker you would have got in to replace me. i guess the only benefit to the company is that i won't leave 10 seconds after I get the right to stay and find a new employer.
you;d be surprised at the requirements of the cop on the street. He doesn't really want a flash and fragile device so that management can send him emails and reports and forms. He wants a radio that he can use "percussively assist" in the apprehension of criminals, and not have to take his eyes off the surrounding area to use. See, most cops want to watch the suspect as they radio in for a check, they do not want to swipe away pressing buttons and using a tiny keyboard with their fat gloved fingers, while the perp runs off (or worse, smacks the cop round the head and then runs off with a shiny new iPhone).
A device (a mobile data terminal) in the car that can be used to fill in the paperwork afterwards is fine, but again, the requirement there is that it is charged by the car, attached to the powerful car radio, and can't get lost, dropped or stolen.
its not really goofy-ass architecture, just different. Its actually a better solution for a games console (compared to the Xbox which is basically a PC). In a way, you can blame MS for thinking its goofy-ass because (like Windows) we're all conditioned to think everything must work in only 1 way.
For games, most of the power is required in graphics, and you need a load of not-particularly-complex processing for stuff like sound, game structures and so on. So putting a load of underpowered CPUs in a box with a hefty graphics chip (which itself is really a ton of underpowered, but specialized, mini CPUs) is simply good sense.
You might not remember old style computers that had separate chips for sub functions, like the Amiga that kicked ass because it had a CPU with several discrete support chips for sound and video. The PS3 is just much more of the same.
Now the crappy SDK probably didn't help matters at all. They should learn from that when they do the next console.
or a HDMI cable, 46" "monitor" and an external pointing device connected via USB.
It works for me, probably scares the sh*t out of Ballmer - which is why they updated their programming APIs to something completely incompatible with win32.
I always thought the scoping aspect of JS was poor too, but its fine for a web page scripting language - a throwaway environment when a new page is loaded. For long-running or complex systems, its not ideal at all.
Still, hopefully people will improve the spec and update it to fit the new requirements we demand of it.
or take the REALLY bold, and risky, step of going download only?...with their own App Store and taking a measly 30% cut of every download, and tying everything into a marketing exercise in shifting Windows 8 phones and Windows 8 tablets? Nope, can't see that happening at all.
Blu-ray is for losers who want to own their own content and watch it again and again, Microsoft says you should pay to watch every movie you used to "own" every time you want to watch it.
that's true - PMs fall into 2 groups: ones who know their stuff about resource allocation and planning and generally managing a project; and those who thought "I be manager, so staff do all work while I get all glory".
You do need skilled engineers though, so the best thing you can do for any project is to improve and build up your colleagues so they are better. That requires a non-ego expert to help them, like a teacher. Unfortunately most people who consider themselves to be experts are the arrogant arseholes who really need the most help.
See the second picture on the first answer. Notice how the waterfall system as described by the original inventor shows how it iterates backwards until the major steps are completed. Surprised that waterfall isn't quite as waterfall-y as popular fable suggests?
The problem with the 80s/90s waterfall led projects were external to the methodology used. The concept of up-front design can work, if you understand you need to be a little bit flexible. I'd say there are a lot of projects today that are being built using Agile methods that will be seen to be total failures in the future (ok, they're not truly agile, they're usually bastard versions of some PMs idea of a good time spent planning) but the simple fact that you can't blame the method for human fuckups should be clear to all.
Except 'brogramming' which is pure human fuckup right from the start.
except you forget ever0changing requirements do not change, so once you have your working prototype and you begin to "refactor everything" (a misnomer if I ever heard one) you are going back to step 1, just with more of a clue than you had when you started.
Agile techniques were invented to deal with this problem, but they are in no way the ill-disciplined bullshit way of coding the article is describing. Agile requires you to be very disciplined in fact (and I refer to "proper" agile, not the "Agile" nonsense that masquerades as agile when someone tries to sell you some agile training course or materials).
For most of us, "brogramming" is just a way of saying "kids trying to appear cool and think they're the greatest". The rest of us can do all that shit without the inefficiency and poor practice associated with this type of playground activity.
most of those inventions are based heavily on work that has gone before them.
You could say the discovery of DNA is a breakthrough invention, but I'd say it was simply made at the right time - when some other processes and technologies were improved to the point where it became possible.
Think about the greatest revolution in our entire history. One person thought to squirt a bit of cold water into a chamber full of steam to create a vacuum that could "pull" a beam into it, allowing the other end of the beam to pump water. Revolutionised mining and made a lot of money but was very inefficient, then someone else thought to split the boiling steam bit and the condensing bit into 2 so that the efficiency would improve dramatically and things improved that the engine would be used for lots more work, then someone else thought to put the steam part and the boiler together with a pipe through the middle to increase the heat surface area and suddenly efficiency improved enough to allow these steam engines to be mobile.
In all the cases they really just improved what was basically a water tank with a fire under it, but each "revolution" - the Newcomen atmospheric engine, the Watt condenser, the Trevithick high pressure engine each made the Industrial Revolution happen. And as each of these happened, other areas in iron manufacture improved too - the high-pressure engine couldn't have been possible when they first began - the high pressure engine needed better materials which probably wouldn't have existed unless steam engines existed first that needed better safety tanks.
So all in all, everything builds on something else, there isn't much that is truly new in the world.
and they've done a decent job with the overall design (not the looks), the predictive text works by putting the word you might want above the next letter you type, so if you type "the" then it will put "they're" above the y key so you just swipe up from that key. without having to look elsewhere and context-switch your brain to see a list of possible words. Someone sat down and thought about that, and that attention to software engineering detail gets a big thumbs up from me.
ArsTechnica has a user comment (scroll down, its the 'editors pick') showing the problem with the camera:
I should also point out that the iPhone's applied far more contrast to the picture and, as a result, lost detail - look at the flat area of darkness in the trunk compared to the range of tones present in the pic from the BB. These are all post-processing problems, though, and (assuming both devices were on default settings) really just tell you that Apple's software is set to produce 'punchier' pictures out of the box as opposed to the lighter processing done by the BB, which ultimately retains more of the image.
so its not crap, it just doesn't aggressively sharpen everything like the iPhone does, so it appears less defined and misty. Its just appearance though, slap it through the same amount of software processing and you'll get the same result.
Anyway, they say the keyboard is excellent and can be used with 1 hand (or 1 thumb) which is a definite design win.
maybe, but they tend to get filled continually as people move from job to job. So how many "unsatisfied" job openings are there left over? No-one wants to ask that question as its too difficult to answer, not compared to a quick count of the job ads open at any given time.
true, homes are built from standardised components but you'll find those components are very well defined and fit together well enough to work. That was the problem with this - the pieces were not well defined enough to fit together well.
Of course a brick is less complicated than an aircraft component, but even then you know exactly what you want to build, and you work out how its going to be put together and then you build it. No-one thinks "I'll build a house, I'll need, umm, some bricks and some wood" and then gets started. they get an architect to draw up some plans and that'll tell you exactly how many bricks and what size and shape wood you need.
at the end they talk about how management from McDonnel Douglas was possibly to blame because in the takeover several "top" people from McD took over the top posts at Boeing, and these guys had the defence contractor mentality where you spend a little amount on R&D and expect the DoD to keep on handing cash over to you regularly until you can't milk it any longer. That meant that tried to cost-cut as much of the design as possible up front.
I think it says a lot about defence spending than it does premature modularisation.
everything is a layer on top of something else in Windows,.NET was a facade over most of Win32 anyway, but that's not my point.
If you're writing metro apps, you can't use anything except WinRT. I think the underlying layers will be present for years to come, but they will add new WinRT-only routines and no new win32 ones..NET has gone now, its a little bit of a meaningless comparison in practical terms but your C# apps now target WinRT APIs not the.NET ones - the.NET ones do not exist on Metro. I know they look pretty much the same but the distinction is relevant - your C# apps now call a native API, not a managed one.
all stores have a 7 day no-quibble return policy, and some places have a 30 day one. You might even check the law for stores obligations for returns.
You don't take it back "because you didn't like it", you return it "because it was not suitable". That's why you get the usual return policies at stores.
its already looks like Metro - as does Office 2013 on the desktop (if you like full-screen 'only' for effective working, and everything in eye-burning white).
I should imagine they're working on it right now, VS2014 might well be a metro app.
There may be nothing in it, but if there is a hint that your workers might get such "injuries" then companies will be reluctant to install such things just in case there is a lot of worker compensation claims (and there will be if it becomes known all you have to do is say "my shoulder hurts" and you get a chance of easy money).
That said, I don't think anyone is selling touch desktop PCs, everything I've seen are laptops that swivel to become hugely bulky tablets
Metro is the solution that Microsoft wants you to have - the desktop is "legacy" now, and might even be phased out in future versions of windows if they can - a bit like XPMode in Windows7.
the reason is that they see the rise of tablets and needed to get a piece of that action, PC sales are flat or falling, no-one really wants to upgrade W7 as it works as well as you'd want it to (barring a few tweaks here and there).
No, Microsoft needed to split with the past APIs (.NET, win32, COM, etc) and build a single one to replace them all. They needed to get a tablet interface. They needed to get a 30%-cut app store. They needed to get us all to upgrade (again).
So yes, Microsoft sees the desktop as the problem.
Slashdot Mirror
don't be so hard on him, if he'd read the book (get it book, preferably a big thick one like any introduction to .NET book) then he'd have his solution solved.
Books are good, though he might need to read a 2nd one to reinforce his now-elevated vision of a solution.
I think you forgot "USERS!"
but then, so did Microsoft.
yeah, but what was old is new again. (work safe).
awesome, thank you.
FYI. the values are 0 - don't send any referrer; 1 - send only when clicking a link; 2 (default) - send when clicking link or loading an image.
Incidentally, you can stop chrome from sending referrals by starting it with the --no-referrers option.
4 hours is too high for the average, though we can easily imagine some people watch more than that.
The Bureau for Labor Statistics says the average in the USA is 2.8 hours per day.
Watching TV was the leisure activity that occupied the most time (2.8 hours per day), accounting for about half of leisure time, on average, for those age 15 and over. Socializing, such as visiting with friends or attending or hosting social events, was the next most common leisure activity, accounting for nearly three-quarters of an hour per day.
That said, individuals aged 15 to 19 also used a computer for leisure for 1.2 hours a day, so that adds up to 4 hours, we've just shifted our attention away from TV to other video-based entertainments.
somewhat counter-productive, cut my wages and i too will work about as effectively as a H1B worker you would have got in to replace me. i guess the only benefit to the company is that i won't leave 10 seconds after I get the right to stay and find a new employer.
you;d be surprised at the requirements of the cop on the street. He doesn't really want a flash and fragile device so that management can send him emails and reports and forms. He wants a radio that he can use "percussively assist" in the apprehension of criminals, and not have to take his eyes off the surrounding area to use. See, most cops want to watch the suspect as they radio in for a check, they do not want to swipe away pressing buttons and using a tiny keyboard with their fat gloved fingers, while the perp runs off (or worse, smacks the cop round the head and then runs off with a shiny new iPhone).
A device (a mobile data terminal) in the car that can be used to fill in the paperwork afterwards is fine, but again, the requirement there is that it is charged by the car, attached to the powerful car radio, and can't get lost, dropped or stolen.
its not really goofy-ass architecture, just different. Its actually a better solution for a games console (compared to the Xbox which is basically a PC). In a way, you can blame MS for thinking its goofy-ass because (like Windows) we're all conditioned to think everything must work in only 1 way.
For games, most of the power is required in graphics, and you need a load of not-particularly-complex processing for stuff like sound, game structures and so on. So putting a load of underpowered CPUs in a box with a hefty graphics chip (which itself is really a ton of underpowered, but specialized, mini CPUs) is simply good sense.
You might not remember old style computers that had separate chips for sub functions, like the Amiga that kicked ass because it had a CPU with several discrete support chips for sound and video. The PS3 is just much more of the same.
Now the crappy SDK probably didn't help matters at all. They should learn from that when they do the next console.
or a HDMI cable, 46" "monitor" and an external pointing device connected via USB.
It works for me, probably scares the sh*t out of Ballmer - which is why they updated their programming APIs to something completely incompatible with win32.
I always thought the scoping aspect of JS was poor too, but its fine for a web page scripting language - a throwaway environment when a new page is loaded. For long-running or complex systems, its not ideal at all.
Still, hopefully people will improve the spec and update it to fit the new requirements we demand of it.
or take the REALLY bold, and risky, step of going download only? ...with their own App Store and taking a measly 30% cut of every download, and tying everything into a marketing exercise in shifting Windows 8 phones and Windows 8 tablets? Nope, can't see that happening at all.
Blu-ray is for losers who want to own their own content and watch it again and again, Microsoft says you should pay to watch every movie you used to "own" every time you want to watch it.
that's true - PMs fall into 2 groups: ones who know their stuff about resource allocation and planning and generally managing a project; and those who thought "I be manager, so staff do all work while I get all glory".
You do need skilled engineers though, so the best thing you can do for any project is to improve and build up your colleagues so they are better. That requires a non-ego expert to help them, like a teacher. Unfortunately most people who consider themselves to be experts are the arrogant arseholes who really need the most help.
pot, meet kettle :)
See the second picture on the first answer. Notice how the waterfall system as described by the original inventor shows how it iterates backwards until the major steps are completed. Surprised that waterfall isn't quite as waterfall-y as popular fable suggests?
The problem with the 80s/90s waterfall led projects were external to the methodology used. The concept of up-front design can work, if you understand you need to be a little bit flexible. I'd say there are a lot of projects today that are being built using Agile methods that will be seen to be total failures in the future (ok, they're not truly agile, they're usually bastard versions of some PMs idea of a good time spent planning) but the simple fact that you can't blame the method for human fuckups should be clear to all.
Except 'brogramming' which is pure human fuckup right from the start.
except you forget ever0changing requirements do not change, so once you have your working prototype and you begin to "refactor everything" (a misnomer if I ever heard one) you are going back to step 1, just with more of a clue than you had when you started.
Agile techniques were invented to deal with this problem, but they are in no way the ill-disciplined bullshit way of coding the article is describing. Agile requires you to be very disciplined in fact (and I refer to "proper" agile, not the "Agile" nonsense that masquerades as agile when someone tries to sell you some agile training course or materials).
For most of us, "brogramming" is just a way of saying "kids trying to appear cool and think they're the greatest". The rest of us can do all that shit without the inefficiency and poor practice associated with this type of playground activity.
most of those inventions are based heavily on work that has gone before them.
You could say the discovery of DNA is a breakthrough invention, but I'd say it was simply made at the right time - when some other processes and technologies were improved to the point where it became possible.
Think about the greatest revolution in our entire history. One person thought to squirt a bit of cold water into a chamber full of steam to create a vacuum that could "pull" a beam into it, allowing the other end of the beam to pump water. Revolutionised mining and made a lot of money but was very inefficient, then someone else thought to split the boiling steam bit and the condensing bit into 2 so that the efficiency would improve dramatically and things improved that the engine would be used for lots more work, then someone else thought to put the steam part and the boiler together with a pipe through the middle to increase the heat surface area and suddenly efficiency improved enough to allow these steam engines to be mobile.
In all the cases they really just improved what was basically a water tank with a fire under it, but each "revolution" - the Newcomen atmospheric engine, the Watt condenser, the Trevithick high pressure engine each made the Industrial Revolution happen. And as each of these happened, other areas in iron manufacture improved too - the high-pressure engine couldn't have been possible when they first began - the high pressure engine needed better materials which probably wouldn't have existed unless steam engines existed first that needed better safety tanks.
So all in all, everything builds on something else, there isn't much that is truly new in the world.
and they've done a decent job with the overall design (not the looks), the predictive text works by putting the word you might want above the next letter you type, so if you type "the" then it will put "they're" above the y key so you just swipe up from that key. without having to look elsewhere and context-switch your brain to see a list of possible words. Someone sat down and thought about that, and that attention to software engineering detail gets a big thumbs up from me.
ArsTechnica has a user comment (scroll down, its the 'editors pick') showing the problem with the camera:
I should also point out that the iPhone's applied far more contrast to the picture and, as a result, lost detail - look at the flat area of darkness in the trunk compared to the range of tones present in the pic from the BB. These are all post-processing problems, though, and (assuming both devices were on default settings) really just tell you that Apple's software is set to produce 'punchier' pictures out of the box as opposed to the lighter processing done by the BB, which ultimately retains more of the image.
so its not crap, it just doesn't aggressively sharpen everything like the iPhone does, so it appears less defined and misty. Its just appearance though, slap it through the same amount of software processing and you'll get the same result.
Anyway, they say the keyboard is excellent and can be used with 1 hand (or 1 thumb) which is a definite design win.
maybe, but they tend to get filled continually as people move from job to job. So how many "unsatisfied" job openings are there left over? No-one wants to ask that question as its too difficult to answer, not compared to a quick count of the job ads open at any given time.
true, homes are built from standardised components but you'll find those components are very well defined and fit together well enough to work. That was the problem with this - the pieces were not well defined enough to fit together well.
Of course a brick is less complicated than an aircraft component, but even then you know exactly what you want to build, and you work out how its going to be put together and then you build it. No-one thinks "I'll build a house, I'll need, umm, some bricks and some wood" and then gets started. they get an architect to draw up some plans and that'll tell you exactly how many bricks and what size and shape wood you need.
yes you should...
at the end they talk about how management from McDonnel Douglas was possibly to blame because in the takeover several "top" people from McD took over the top posts at Boeing, and these guys had the defence contractor mentality where you spend a little amount on R&D and expect the DoD to keep on handing cash over to you regularly until you can't milk it any longer. That meant that tried to cost-cut as much of the design as possible up front.
I think it says a lot about defence spending than it does premature modularisation.
everything is a layer on top of something else in Windows, .NET was a facade over most of Win32 anyway, but that's not my point.
If you're writing metro apps, you can't use anything except WinRT. I think the underlying layers will be present for years to come, but they will add new WinRT-only routines and no new win32 ones. .NET has gone now, its a little bit of a meaningless comparison in practical terms but your C# apps now target WinRT APIs not the .NET ones - the .NET ones do not exist on Metro. I know they look pretty much the same but the distinction is relevant - your C# apps now call a native API, not a managed one.
all stores have a 7 day no-quibble return policy, and some places have a 30 day one. You might even check the law for stores obligations for returns.
You don't take it back "because you didn't like it", you return it "because it was not suitable". That's why you get the usual return policies at stores.
its already looks like Metro - as does Office 2013 on the desktop (if you like full-screen 'only' for effective working, and everything in eye-burning white).
I should imagine they're working on it right now, VS2014 might well be a metro app.
ooh.. "I want my compensation"
There may be nothing in it, but if there is a hint that your workers might get such "injuries" then companies will be reluctant to install such things just in case there is a lot of worker compensation claims (and there will be if it becomes known all you have to do is say "my shoulder hurts" and you get a chance of easy money).
That said, I don't think anyone is selling touch desktop PCs, everything I've seen are laptops that swivel to become hugely bulky tablets
Metro is the solution that Microsoft wants you to have - the desktop is "legacy" now, and might even be phased out in future versions of windows if they can - a bit like XPMode in Windows7.
the reason is that they see the rise of tablets and needed to get a piece of that action, PC sales are flat or falling, no-one really wants to upgrade W7 as it works as well as you'd want it to (barring a few tweaks here and there).
No, Microsoft needed to split with the past APIs (.NET, win32, COM, etc) and build a single one to replace them all. They needed to get a tablet interface. They needed to get a 30%-cut app store. They needed to get us all to upgrade (again).
So yes, Microsoft sees the desktop as the problem.