I am not someone who generally suffers from claustrophobia, but as a tall person (6ft 5in) who is by no means fat, I can honestly say it was one of the worst things I've had to do. My shoulders are broad enough that it felt as if I was uncomfortably wedged within the machine, and that I was far enough inside the machine that should something go wrong it would be impossible for me to get out unassisted.
Perhaps it wasn't so much claustrophobia in my case, more my total dependence on someone else to get out. I am definitely not looking to go through that experience again any time soon.
I think there are definitely things that can be done to improve the experience.
Also worth noting: I do realise that these machines come in different sizes, but they are also expensive to purchase (replace), so I am not holding my breath for regular updates at every hospital when they can add another inch to the diameter of the chamber.
You can shorten it even further to typing 'fori' then triggering the expansion by pressing tab.
Best shortcut that every IntelliJ user should know is "Find Action" (ctrl + shift + a on Win), press and start typing what you want to do. Will even present shortcuts in the list for next time.
I might be missing something here, but where is the passphrase negotiated? Apart from calling or talking to the other person, the only way to define this common key that I can see would be electronically. Isn't this a bit of a problem?
What is the best way to establish optimal pool size? The article seems to gloss over this and instead mentions 'you need to set pool: 25', but I doubt this is a one size fits all solution.
Anyone have any experience profiling these sorts of things that can share some info?
> If you’re using Twitter and Facebook for signup too you’ve got a bigger problem. A user’s credentials are then bound to another account on another service that could be canceled at any time, breaking access to your app without the user knowing
I'd never really thought about this. What do people suggest doing to handle this sort of use case?
One problem I have with the current 2FA on Google Apps is that there is no way to enforce 2FA for all users before everyone sets up their mobile device. If you've set the requirement for all to have 2FA, then new users can never log in.
You're then left in this limbo of some with/some without 2FA, and unless you actively pursue those without it setup, you can never change that system wide setting in the control panel.
I'd like to mention SourceTree[0] for a GUI DVCS. I typically drop to the terminal for git usage, but every so often use SourceTree when I need something that is easier achieved with a mouse.
These decisions typically have much wider reaching ramifications, like an existing tech stack which relies on some quirk of IE6, or activeX. Yes, it's simple to upgrade a browser, but the potential impact must be evaluated, and this takes time (more than 10 mins to install a new browser).
I think this really depends on your target market. Big corps such as banks are typically slow to move and I know of at least one which is only just moving from IE6 now.
I think this stems from the memory these people hold that the item (whatever it is, doughnut, site access etc) was once free. People will wonder "why did this change?". It could be many things, but people will most likely jump to the easiest conclusion, the seller is greedy.
Using the doughnuts analogy, I wonder how things would have worked out if they continued to give away the plain doughnuts for nothing, but added a new line of premium iced doughnuts which attracted a charge? Personally I wouldn't mind, and I think that a lot of people would be ok with this.
Stemming from this, you really need to have a good reason to charge people for something they were previously using for free.
Personally, I don't think you can start charging for something that was previously free (without significant value add). By all means offer a paid upgrade with particular value add, but never do the wrong thing by your (thus far) loyal users.
Appreciate the feedback! We're working to add the field labels now so stay tuned.
With regard to price, its a tough one. We purposefully left it out initially because it's subjective. If we use RRP - should a 2000MY Suzuki 650F be filtered because a brand new (2013) one is outside your price bracket? Obviously there are going to be differences, but we're thinking hard for a way to include this. I agree it would be a big helper!
Yep definitely more info required here isn't there :)
This targets the Australian market, and more specifically the state of New South Wales.
Some of the bikes may be expensive (or not worth learning on), but this list is provided by the Roads authority (RMS) as to what you can ride, not necessarily what you should ride.