The creators "invested" in foreign companies that would buy their product. They had realized that $1 of product sold was making them much more than that in the stock exchange...
Be cautious about calling their customer support if you have "bought" DRM stuff: you can be banned for any reason at any time.
I complained about a failed delivery (broken box, one item missing). They refunded me but then immediately put me on a watch-list, threatening to ban me if I ever complain again. I will never buy anymore on amazon.
Please see the link i sent. These are good wheelchairs. There is ZERO reason why a cushioned seat on a pair of wheels should cost more than $1K. I am always amazed at the extent to which Americans go to justify the crazy cost of medicines, healthcare, equipment etc in the US. Folks, you are being taken for a ride. Don't keep making excuses for the profiteering healthcare companies in the US.
I am from Europe and chairs are a bit less expensive here, but an "active" wheelchair is usually more than 2k$ anyway, often closer to 3k$. And some are much more than that (for instance if you want a soldered chassis)
You are missing the experience of being tied to a wheelchair for a complete day.
None of the chairs you have shown are suitable for daily use. Even the "Magnesium" one.
One of the most important point (beside being the right size) is to be able to move the center of the rear wheels just behind the center of gravity. Too far rear and you have very good stability (hospital chairs), but you need to use most of your strength just to be able to turn (and you take a lot of space for turning). Too far ahead and it becomes dangerous. So it must be adjustable. In theory this should be possible on a cheap wheelchair, but I have never seen it. Probably the weight ditribution is too different (most is on the rear wheel) that the chassis must be thought differently?
I am on a watch-list too because of a recent problem with a broken package with only one item out of two inside. It was clearly a too light packaging for a heavy item with sharp corners.
The only other problem I had was a warranty claim 5 years ago.
My account is not closed (but they "reserve the right to close it" anytime). I am glad I have no kindle or DRM stuff...
I tried to get an explanation, but just got a robot email.
I will never buy there anymore. Even if some stuff are hard to find elsewhere
When I was about 10, I was able to swim but I was not great at it.
For some reason (I think someone dived just in front of me), I needed to stop swimming and ended "vertical" in the water. It was quite unusual for me at the time. For a moment, I tried to go back to swim horizontally on the belly, without success. Then tried on the back, no success either. After a few tries, I began panicking like it is said the the video: I was just climbing an invisible ladder... A guard finally helped me reach the border of the pool and that was over.
After that, I tried to put me under the same circumstances: vertical in the water, 2 m from the border. And then convert to horizontal swimming. Every time it was easy. To this day, I still have no clue why I was not able to do that
the brainstem probably takes over, which will disconnect the rational, logical part of your brain from your extremities.
i'll just comment my comment here instead of crapping up the entire thread. I went through about 20 videos and only missed two because the site assured me the person who the lifeguard rescued was "splashing around". My median time was -5s, with an upper bound (probably site limited) of -15s. The videos are just a toy, though. You know someone is going to need rescue, and probably about 10 seconds in. I was picking the people who looked like they'd need help. I'd make a great lifeguard but it would be because i'd point and yell at people to get out of the deep end 30 seconds before they even had any issues.
I learned to swim at 5-8 or so, and from 10-15 we spent summers swimming in the pacific ocean. I never had to be rescued during that time. I went swimming with a bunch of friends at Huntington Beach directly after a sewage leak into the ocean near there and they had put bleach into the water. I have asthma, so when i crossed the "can't touch the ground" part of the undertow and had an asthma attack, i yelled at a friend "get a lifeguard, i won't be able to get back to shore" - he relayed that on and then came to make sure i didn't "freak out". The lifeguard did have to tow dead weight, though, i couldn't move due to lack of breathing - not breathing water.
It is good to know that i can watch a decent sized group of people in inner tubes swimming and notice if one is struggling.
+1
And usually, the one person in the meeting not using headphones does not feel the problem: he can speak all the time and be heard correctly, while the others cannot interrupt him while he is speaking
Just a fun anecdote on end-to-end testing I did 20 years ago while working on the compression of images.
Some parts of the algorithm were easy to test, others very hard. On the easy part was loading and saving the file. I tried to test as best as I could, but the lossy part was not really tested.
Then time to benchmark the algo on some images.
The results were kind of OK, but some images compressed much better than others at low bit-rate, while the content did not look much different.
On square images, everything was fine.
On rectangular ones, at high-bit rates it was somewhat fine, but strange patterns like ghosts of another part on the image started to appear for lower and lower bit rates.
Of course, I searched on the mostly algorithmic parts what was going on, and failed.
Only after a holiday break and fresh eyes did I found the root cause: inversion of height and width in some part of the loading AND saving.
I had "end to end" test of the loading and saving, but the error was symmetric, so undetected. Young engineer error...
"Refactor your codebase to put the related code together"
Of course it is a goal, but not always possible. You sometimes have two (or more) conflicting "relations" in the codebase. E.g.: you are dealing with taxes in various countries. Do you group by country or by kind of taxes (on sales, profits, earnings, energy, real estate...) ?
The right answer really depends on how your team is organized and how you are making changes.
> E.g.: you are dealing with taxes in various countries. Do you group by country or by kind of taxes (on sales, profits, earnings, energy, real estate...) ?
Seems like you would be dealing with one of 2 reasonably well defined problems in this case. How to group would follow logically. It's either:
1) "If i will be dealing with one specific type of tax at a time and how it is applied in different countries. (i.e. What are the sales taxes in UK, France, and Germany? )" Group by tax.
OR
2) "If i will be looking at one country at a time and their assorted taxes. (i.e. What are the taxes in the UK for income, sales and value added?)" Group by country.
Else "i have failed to properly define the problem." that's gonna be the problem.
How about when supporting both use cases? A multinational company might need the former for people making decisions across the whole company, and a country specific department doesn't need anything but what's relevant to that country.
You could make two tools, but now you're duplicating implementation. Factor out a shared library/service/modularization-approach-de-jour? Good idea, but we're back to the question of how to structure things.
The creators "invested" in foreign companies that would buy their product. They had realized that $1 of product sold was making them much more than that in the stock exchange...