608 karma · joined April 13, 2011
https://www.amazon.com/Art-Fear-Observations-Rewards-Artmaki...
My main concern was finding a way to keep the things that end up in the back of the fridge from staying there for weeks and weeks. I waste more food than I care to because I'm the opposite of what you're attacking me for being -- I'm the guy that puts stuff away and forgets about it the next time I go to eat. That, and it's hard to coordinate with my fiancee on meals when she works midnights.
Anyway, I'm sorry for offending you with my ideas. I just think a smart fridge could actually be handy for wasting less food without having to be obsessive compulsive about tracking and without being a great judge of freshness with my nose. You just glance at the fridge and pick out things to eat before they go bad.
For made at home items and non-tagged items, they could also make RFID stickies, where you scan them when you put the item in the fridge, give it a name or take a snapshot with the built-in camera, set your own expiration date, and it tracks how long it's been in there.
If you focused enough on usability, you could make the whole thing feel streamlined and natural. The fridge itself could dispense the RFID tags, and you could just reuse them by reloading it with the old ones, for example.
I originally read about it on Corvette forum (I used to be a C4 vette owner and was always looking for interesting tips or projects).
If you're mechanically and electrically inclined, it's more than feasible.
http://en.wikipedia.org/wiki/Long-term_support
The basic idea is that once released, the LTS version of the compiler would continue to receive fixes and updates for several years (at least two according to Wikipedia), no matter how many new versions are released during that time.
I see GZIP optimization and fingerprinting in your deployment overview on the homepage, but do you include any built-in support for avoiding render-blocking CSS and JavaScript? And if so, then what about handling load order and dependencies between the asynchronously loaded pieces?
It looks like your homepage actually fairs pretty poorly on PageSpeed Insights:
https://developers.google.com/speed/pagespeed/insights/?url=...
I realize PageSpeed scores can be something of a red herring in a lot of cases, and I'd like to know if you think it's not worth addressing. I know for my place of work, if it influences SEO to any significant degree, then it's important to my boss.
Currently we use Middleman, which from the description I saw of Cactus, would be the Ruby equivalent using Sprockets and Padrino instead of Django. We had to make a custom template with special helpers to address various PageSpeed issues. It'd be nice to have a tool that has features addressing these things out of the box though.
Anyway, great work! I think tools like this are really the future as far as content on the web is concerned.
As for the women, plenty of college girls and other young women notice what I'm driving and give me complements. A nice car definitely still gets attention from the ladies. Quite a few I've know even enjoy driving stick and like to go pretty fast.
I'll admit, young people may be more practical and economical with their vehicle purchase decisions, but car culture is still very alive and strong here.
It was definitely a worthwhile investment. After a month and a half of coaching with a personal trainer, I feel a lot more confident with going to a gym or using my own equipment now. I'd still be going to the same trainer if I could fit it into my schedule.
Still, this appears to be a useful step up from having packages delivered at random times throughout the day.
He plays his online Texas hold'em (flash based), looks up unfamiliar destinations on Google Maps to see the satellite imagery, and checks the weather radar regularly to avoid storms. He's also able to better keep in touch with us now that he can shoot off e-mails whenever he wants.
It's actually a handy, useful tool for him.
But to answer your question, I think the real plan is that you don't try to do your work on a Windows 8 tablet without a keyboard. Instead, you get a lightweight, convertible Windows 8 tablet. That way, you can have your cake and eat it too.
The way I see it, people don't turn food into energy -- they simply move energy around and transform it by breaking the chemical bonds in the food and forming other chemical bonds using enzymes to keep the activation energies low enough to make a net gain despite losses to heat. So based on the conservation of energy, people don't turn anything into energy. The energy was already there -- they simply transformed it.
But then with the conservation of mass-energy, we know that some mass is converted to energy when chemical bonds are broken. So technically the statement is true in a sense. But the amount of energy created from mass is so small it can't even be measured or detected, so for all practical purposes, the statement is false. You have to be breaking nuclear bonds before you see that.
The article's author says the statement is true, using it as an example of a statement that's consistent with our preconceived ideas, but instead of explaining it, he simply does some pseudo-scientific hand-waving -- digestion, respiration, metabolism, and all that. This suggests the author somehow considers energy as something that is created and used up on a regular basis.
Which makes you wonder, what if the writer of the statement was an expert biologist whose major focus isn't understanding the concept of energy or the chemical underpinnings of microbiology? What if they also saw energy in the same way as the author of the article? What if the answer on the answer key is true, despite being arguably false? In that case, the answer is true in the sense that that's what the writer of the test wanted you to answer.
I think a better test would give the option of adding a statement or two to qualify or explain your choice on the test. I know that would allow me to finish such a test sooner, especially if it was computerized and I could type my explanations.
Meanwhile, if you look at the other photos with the horizon present (e.g. http://mars.jpl.nasa.gov/msl/multimedia/raw/?rawid=RLA_39750... ), the ground is dark because in order to capture the details in the bright sky, the exposure has to be adjusted so that less total light is captured (usually by using a faster shutter speed). Otherwise, you'd blow out the sky and get no details there.
It looks like the dynamic range of these cameras is limited, so keep that in mind when looking at any photos that come out of them. Something that's bright in one shot might be extremely dark in another, depending on its relative brightness compared to other parts of the scene. Take a look at the last few rear camera shots with the sun in them:
http://mars.jpl.nasa.gov/msl/multimedia/raw/?s=0
The sun causes all the sky detail from the previous rear camera shots to appear black, since its overwhelming brightness requires the exposure to be extremely brief.
Anyway, I hope that gives you a better idea of what to expect from these cameras and how to interpret the photos.
As an aside, the devil thing isn't isolated to non-Western countries either. Linda Branagan famously recalls one instance of where the BSD "Daemon" mascot, which also looks devil-like, nearly got her into real trouble in Texas: http://rmitz.org/freebsd.daemon.html
References:
[1] https://developer.apple.com/library/mac/#documentation/apple...
[2] http://appscript.sourceforge.net/py-appscript/index.html
[3] http://rubyosa.rubyforge.org/
[4] http://appscript.sourceforge.net/tools.html#asdictionary
8-bit PIC and AVR microcontrollers have very simple instruction sets and can be connected to simple I/O devices like switches and LEDs, but they both use Harvard architectures, so you have different address spaces for code and data. The newer 32-bit PIC micros use a MIPS core, but the development tools aren't very open, despite being based on GCC.
The 16-bit MSP430 is fairly simple, has good open-source development tools, cheap development hardware (check out the Launchpad), and a more conventional von-Neumann architecture. Check out some of Michael Kohn's sample code for the msp430 assembler he wrote:
http://www.mikekohn.net/micro/naken430asm_msp430_assembler.p...
When I realized it was just a slideshow, I was disappointed. Slides are meant to highlight points, illustrate concepts, and provide focus during a presentation, but they aren't meant to replace it. The only purpose in sharing slides is so that the folks who saw the presentation can remember it better.
Which makes the complete entry look like:
title Arch Linux
root (hd0,0)
kernel /vmlinuz-linux root=/dev/sda5 ro pcie_aspm=force i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1
initrd /initramfs-linux.img
I also use thinkfan to keep reasonable fan speeds along with the ondemand cpu-frequency scaling policy on battery power keep power usage down. I also minimize disk usage by taking advantage of my 8GB of memory and placing /tmp in tmpfs. These days I usually get 8-10 hours of actual use on a single charge, but most of that is writing/running code and browsing the web. If you usually do something more CPU taxing, you'll probably run closer to 5-7 hours. That's using the 9-cell battery that juts out from the case slightly and a low power SSD.The most annoying part of the X220 is the buttonless clickpad. It works really well if you use the tap to click features, especially since the multi-touch lets you scroll around and double/triple click with multi-taps, but in the end I just couldn't get used to tap to click. Using the actual click/button, click and drag is so horribly broken with clickpads on Linux (and even Windows, if you ask me), that I gave up on that fairly quickly too. Finally I just disabled the touchpad in the BIOS. The touchpoint works too well to bother stressing over the ill-conceived touchpad on this model.
The IPS screen is great, but there is some occasional ghosting. It's only a temporary effect though, so it's a price I'll gladly pay for having a better image than any of the external monitors here in the house. It's also extremely bright, so I suggest turning down the brightness a few steps and letting your eyes adjust, otherwise you'll unknowingly burn your eyeballs out.
The battery also has a little bit of looseness when it's locked in. Based on what I've seen on other forums, this one's hit or miss, with some people having the same problem and many others not. Overall though, the laptop feels fairly solid without being heavy, but it's not nearly as solid as the X120e (which feels dependable) or the aluminum-body Macbooks.
Finally, the keyboard on this thing is great. The keys are nice and big, the escape key is prominent and in the right spot, and the quality of the tactile feedback is perfect.
If I had to choose all over again, I would've gotten an X220T, since I underestimated how much I use my wacom tablet, but other than that, I'm quite happy with the X220.
Seeing an ultrabook that transforms into a reasonably compact, multi-touch tablet just made everything click. Windows 8 may not be the best tablet OS or the best computer OS, but it's the perfect OS for notebooks that transform into tablets or tablets that can be docked into a desktop setup.
Then again, a good number of the people I do know don't even understand the concept of a web address or even how to use bookmarks -- nevermind speed dial. Usually when I watch someone try to find a site, they just search for it in Google, and if Google isn't the default search provider, they search for Google in whatever search engine is the default. They also rarely use any browser "feature" except the back button, and they're afraid to try out new features. Even tabs and multiple windows are often underutilized or avoided by simply using one window at a time and closing it if they want to start over or visit a new site.
In fact, whenever they accidentally activate a feature they don't use (history, right-click context menu, rss feed view, gestures, etc.), it often just leads to confusion because they weren't paying attention to what they did to set off the unfamiliar feature's action. As a result, they just close the window and start over, and if it happens again they get frustrated and do something else.
Also, learning new features isn't free. There's a cognitive cost involved and it takes a certain amount of training and repetition to solidify the ability to use new features. For some people, it's higher than for others, and eventually it gets to a point where people like my Dad have to basically relearn the same features over and over again every time they use a computer. Listening to older relatives talk about their computer experiences, it also sounds like most of the time they're too deeply afraid of accidentally breaking their computer by clicking or doing the wrong thing to learn features by experimenting, further reducing the ability for them to solidify their learning through repetition and practice.
By comparison, those individuals I see who are willing to learn new features or who can notice what they did to set off a feature are usually pretty tech-savvy (or soon will be) and would be able to figure out how to use and install extensions anyway.
So personally, I think it's a good idea to aim for a default, minimalist interface and avoid gestures and interactive UI elements that users can accidentally click or activate. But that's just based on my casual observations of people using computers, which is why I'd love to hear yours, since apparently you disagree.
My only regret now is not getting the convertible tablet version, since I underestimated how much I use wacom tablets, and having one built into the screen would be extremely convenient for me.
However, what's best for me isn't best for you. If you use Linux and don't like tap to click or the Thinkpad trackpoint (the famous red pointing stick in the center of their keyboards), you might test drive the X220 before considering it, because the clickpad they put on these models will probably drive you nuts -- especially if you're used to the multitouch clickpads on Macbooks.
Also, about the screen size. It's big enough to see what you're doing, but since it's a lot wider than it is tall, you should consider how the development software you use will work with it. I spend most of my time inside of VIM, so I just maximize the window and split everything vertically. With a nice bold 9 or 10pt font (96dpi), I still get about 100-110 columns of text in each vertical window and almost 50 lines, without having to resort to small fonts (I don't like squinting). So for me, this screen size and ratio actually works out very nicely. If you spend all of your time inside of Eclipse or Visual Studio though, the lack of screen height will probably cause some pain.
Some people also report problems with noisy fans on this model. I haven't had this problem at all, but I intentionally avoided getting a soup'd up Core i7 configuration.
That said, I would also suggest considering a Macbook Pro. They usually have excellent battery life and a fairly solid design.
I'd especially like one that suggests hyperlinks for documents based off of what users typically make hyperlinks for or based off of some kind of algorithm with heuristics built on content and formatting conventions, because even though just being able to create your own hyperlinks would be handy for studying and reviewing, having them appear magically would be a killer feature.
However, that'd probably be too hard for a single weekend. For one thing, it'd still have to be a good PDF viewer, which means nice features like being able to custom crop/zoom pages to hide margins in documents with lots of extra white space, and it'd have to perform well with the large, complex kind of documents that people would want to add hyperlinks to.
It also lacks long term viability due to the slow rise of eBooks with hyperlinked content on delivery platforms like the Kindle.