This is how audiophiles talk. If you have one as a friend, it is best for everyone if you simply never talk about music.
Well, you don't seem like the original poster, but I think you answered my question.
Earbuds:
1. Fit in a pocket
2. Are more than adequate for most pop music produced in the last 75 years.
3. Are more than adequate for most mobile listening environments.
4. Are more than adequate for podcasts.
5. Can passively cancel ambient noise without looking like Princess Leia.
6. Might, depending on personal preference, be more comfortable.
7. More amenable to wearing during physical activity.
8. Starting cost is around $1.
But yes, they completely suck for all purposes.
And how do we know that the real benefit doesn't come from hitting yourself with birch branches?
How about every female bus rider who doesn't want to be spoken to and doesn't want to mess up their hair...
I miss the good old days, when you knew to blame everything on the Axis of Evil, and you could solve all our problems by bombing Iraq.
It's to help decide "whether" to bomb someone.
Space heaters are fire hazards.
A lot of people? Is this a "who has a TV, anyway" kind of question meant to sound superior or a serious question?
I think the PIAP activists have started eliminating the competition.
zblockquote>See: Cabin_Pressurization [wikipedia.org]
A person needs at least 20kPa *from the mask to breathe*. Not 20kPa *ambient pressure*. Please learn to read.
The "problematic loading on the capsules" is from the high speed aerodynamics, not the ambient pressure
Aerodynamic loading = pressure. If you have high loadings, you have high pressures. Period.
I was using my samsung Smart tv for youtube, as Roku didn't have a youtube. That changed ~6 months ago so I started to use both. Then Samsung tried to insert ads into my playback , so I disconnected the TV from the network.
What will it take for companies to learn if you don't want to provide support for 10 years don't design a device that requires your constant support for 10 years?
yeah it's always bad when vocal participants like the client(product owner whatever) wants to add complexity to actually make the product do what it is supposed to do..
and if you actually make an uml diagram that results in hundreds of thousands of lines of java code that does the same thing as 100 lines then you have fucked up quite badly in both making the uml diagram and writing the code.
I think the OP was asking for a solution to do just high level design anyhow, to slash up the work into smaller logical segments - so that they don't end up writing hundreds of thousands of lines of unnecessary code.
a whiteboard is useful that you can draw anything on it.
like drawing the flow of the program from ui side for example to communicate to the team what the end product needs to do so the team can figure out what the backend has to be capable of and so forth. if that part is skipped the server guys can for example write some shit that they claim fills the role of the server but is fucking horrible at doing what it needs to do and ends up needing a total rewrite before the product can ship.
"Look! There! Evil!.. pure and simple, total evil from the Eighth Dimension!" -- Buckaroo Banzai