I reviewed the article but not the paper direct but this could be very beneficial knowledge for gi doctors. I wouldn't be surprised to see this at least nominated for a ig nobel prize.
vrek
Oh shit you're right. I shouldn't respond with a technical answer late at night....
As always, best choice is it's depends on situation
There is still a charger brick there...now cut a USB cable plug off and connect the power wires in to a wall outlet directly...
Plugging into a USB port on your computer? Your power supply is already converting 120/240 vac(depending on location) to 12 vdc. That's fine. Bypass that power supply and connect your phone to wall power directly and expect flames...
Yeah if your only storing username and passwords and hoping no one uses the same username. Now consider I'm running tests on a piece of hardware and storing results in the database. I run 45 tests per unit so I can't use serial number as id, I want a way to get all results for a single unit and I have 5 testers since I'm high volume but each test takes 30 seconds.
Tester 1 and tester 4 might get same pk if offline, random IDs for each record won't work since I can't combine everything for 1 unit. This is more why you use uuids for each test
Everything up to the laser welding was as a teenager.
I have the opposite situation at the moment. I bought a bag food, early last week. It was delivered last Thursday. It is supposedly suppose to arrive today, still waiting for it to be "out for delivery" though. We will see what happens, like when it's delivered they are supposed to take a picture but it's already in my kitchen.
I want like a sub sandwich with American cheese coated with manwich ...
Only with alt but yes
Oh forgot f5 for refresh
I feel like both are valuable for different purposes. Do you really have specific requirements? For example a piece of software to dispense a defined amount of a medication into a bottle. It requires plus/minus 1 ml accuracy for health safety. It will use Acme Corp stepper motor to operate the dispenser which has its own requirements. It will operate on arm based Linux for low cost. These are requirements, they will not change. We will sell the device with a high definition screen with 1080p(no one is gaming or watching movies on a medication dispenser, no need for 4k or 8k).
Then there are more agile things. Some pharmacies are 24hrs, the users want a dark mode so it's easy on eyes at night. Don't write specific colors for buttons into your requirements at beginning. Some prescriptions are sold between 10ml to 5 L(making up numbers) so users want a touch pad to enter values instead of up and down buttons(pressing up 5000 times would be a pain). How users enter amount should not be a requirement at beginning. These can change and should use a agile approach.
Requirements in my mind are things were changing is a huge investment and would require a new round of design. Those should be defined up front. That's waterfall. Other aspects should be easier to change based on whims of customer. That's agile.
If a customer says we like your software but want to use Other Corp motor, no sorry not compatible. If customer wants their logo in corner should be doable.