282 karma · joined July 14, 2009
You can also just run a sed style substitution in most shells, e.g. '$ !!:s/before/after/' or '$ !!:gs/x/y/', which is safer IMO.
Migrated my emacs configuration to the remote server as a git repository, along with any programs that aren't available (e.g. git, which I use for unofficial code; official code is managed via perforce). Use GNU stow to move those configurations and binaries to the right places. If I need to move non-confidential information around I collect it in an emacs buffer and then use M-x compose-mail to send it out. The home directory is an NFS mount so I can also mount my home directory and exchange files that way. Etc, etc.
I also set up a lightweight Arch virtualbox VM that I SSH out of, because I really don't like the available Windows terminal applications, and every so often I need a local Unix box for some random reason.
A lot of my coworkers use Sublime and remote file editing, but I work faster when using Emacs (comint-mode is a godsend). We mainly work in Perl, Javascript, and HTML so none of the bigger IDEs are really appropriate.
Edit Since people seem more interested in the Sublime workflow, I asked for a few more details. Coworker replied: "Sublime SFTP [...] you might want to mention that the only advantage to SFTP over remote mounting the server is the save time, as with SFTP, you save local and push in the background, meaning frequent saves don't constantly stall workflows. Otherwise, there is no real advantage over just mounting directly." It is worth noting that he is working on a Mac, which has some severe bugs [1] when it comes to NFS mounts, and Samba has some latency issues in this instance.
Case example: while I don't remember all of the details (it was 15 years ago), there was an exhibit in a small museum in my hometown that had several civil war era percussion fuse cannon balls. An explosives-certified agent at the local ATF office heard that one of the curators would occasionally show children visiting the museum how neat they were, since they would warm up when you shake them. Ends up they were still live, but that the explosive had degraded; a little more energy (say, from dropping it after shaking it for a while) could have set the charge off, killing or seriously injuring the kids at the exhibit. They were safely destroyed, but it stuck in my mind as a cautionary tale not to screw around with old ordinance.
Sounds to me like they modified the driver so that it had some kind of emissions pattern they could track. Driver could be modified via a virus or something.
1: What is the actual capacity of the battery demonstrated? If it has a high C but low capacity, this isn't really notable. The paper [1] indicates that total charge capacity is a function of how fast the battery is charged; what tradeoff are they making?
2: How many charge cycles is this battery capable of at those rates?
3: What thresholds are they putting in place for temperature, and are all the components of the phone rated for repeated thermal cycles to those levels and back to ambient?
4: What is the failure mode for this battery? Outgassing? What compounds are released in overcharge?
[1] - http://www.nature.com/nnano/journal/v9/n12/abs/nnano.2014.24...
I call bullshit on this. The majority of the people using Facebook have no clue what information they are giving up to a third party, and would be very concerned if they realized that their browsing habits were tracked by Facebook without their explicit authorization.
I guess you could theoretically pull salt out of the water, but there is no telling what impurities may be left. Reverse-osmotic water filtering makes water so pure that it supposedly extracts minerals back out of your bones and teeth, so impurities are no concern when it used as an exchange fluid.
http://en.wikipedia.org/wiki/Selective_laser_sintering
http://www.solid-scape.com/products/solidscape-3d-wax-printe...
http://www.contourcrafting.org/
Also, plastic 3D printing is a low-part-order replacement for injection molding, and is significantly cheaper for short-run or prototyping. And it is not designed to be a one-stop solution, but simply part of a workflow that can be brought to small fabrication shops to permit them to construct a wider range of things.
That said, the biggest limitation of the Makerbot series of printers in my opinion is the lack of a soluble support material. The Dimension printers [1] allow you to fabricate models with both a structural plastic (ABS) and a support material (unknown) that will dissolve in a lye bath, meaning you can make complex mechanical components in one pass and then dissolve out the unnecessary sections.
http://features.blogs.fortune.cnn.com/2012/06/27/fast-and-fu...
First, you could put the piezo film (commonly used in speakers for cellphones, more efficient for smaller transducers but requires a special amplifier) directly below (but in contact with) the display and use the display as the 'diaphragm'. Makes the entire display a speaker, but would require some interesting sound cancelling tricks to avoid feedback with the microphone.
Second, you could use a piezo below the display with an airgap and use something akin to the laser used in the power LEDs on the Macbooks to poke enough airholes to direct the sound toward the ear.
A third method, which I'm not sure would work, is to suspend the piezo material between two ITO layers (like that used in the capacitive touchscreen) and put it above the display. Depends on if someone has found a transparent piezoelectric material yet; I haven't been keeping up with the materials science side of things.
However, I was referring more toward the recording system than the staff. If the recording systems were all using unix time stamp with a GMT system clock synchronized over NTP, there would be no ambiguity as to when a record was added to the system. End user systems could be responsible for keeping track of what time zone the user is in, and could convert as necessary. The important thing is that the "One True Datum" have the appropriate stamp.
... like NTP?
Sorry, but I'm not sure what point you are trying to make here. Anything with a computer, even a microcontroller, and basic network connectivity can use NTP, it is an extremely simple protocol.
Anything that doesn't connect to a network could be kept in sync via a wireless pulse/tick, though then you have security issues unless you cryptographically sign the clock signal. Though I'm not sure why anybody would try and screw up a clock signal like that other than general asshattedness.
That aside, I'm unsure why they are using local time for logging data anyhow. If the folks managing the hospital were rational, shouldn't there be a regulation to use GMT and 24-hour clock? My home town is right on the Eastern/Central timezone split, and I know it causes all kinds of problems in day-to-day life. I just hate that kind of ambiguity.