182 karma · joined June 8, 2010
I have worn many hats during my career, but they all have these things in common: 1. You have to ship/deliver when you say you will. 2. You can't ignore customers' needs, and this includes fixing their problems. 3. If you leave a mess, someone is going to have to clean it up - of course, it's best not to leave a mess in the first place, but do document what you've done so the next guy will have an easier time of it.
I am the sole inventor of a patent in the field of networking.
Hobbies: Amateur ("ham") radio, weather spotting ("is that cloud rotating?" "is the wind above 58MPH?" "are there any hailstones coming down that are 1 inch in diameter or greater?" => call it in!), playing music by ear, woodworking, and photography: chemical, mixed-media, and digital.
I have worked for a wide variety of companies in and out of Silicon Valley, as well as the (US) Federal government and some universities. I currently work for a Fortune 500 firm near the center of the country - please wave as you fly over.
e-mail: bandy@beals.org
The maxim then (and now) being: Don't Write Silly Code.
Gives the correct response - site is down. The www. is, of course, optional.
Totally accurate - workers are treated as red boxes in spreadsheets, to be hired as necessary and "rightsized" when the project is over.
I'm relieved.
Of course, even though they played by the current rules, Cisco got burned a while back: http://books.google.com/books?id=ZlQl08fahhkC&lpg=SA4-PA...
A "If you don't see the emoji, then download these fonts" right up-front would have been immensely helpful.
Or is the lesson we should learn is "If you're going to do anything questionable at home on your 'net connection, make sure your wifi is open."?
Coverage was there, for those who were interested in finding it. The Soviets' failures were, of course, highlighted, but their accomplishments weren't downplayed, either.
You forgot to add-on "keyboard, mouse, and monitor". Again, these are things that people usually have.
For the dev cards mentioned up-thread, you'd have to have some sort of programming dongle, which more than doubles their cost, as well as get your hands on the right magic toolchain.
I could do my project with dd-wrt/openwrt, but I'd be storage-limited. A day's worth of data is in the hundreds of megabytes range, uncompressed.
Your WR-703N plus a daughterboard would make an OK basis for a NAS.
Mine will be running some network testing software, driving a small handful of devices – doing the work a small laptop was doing before, but with a better power budget and in a much smaller form-factor. I don't need a display while it's running - it's going to sit there and collect data for me until I command it to shut down, at which point, I'll remove the SD, grab the data, and process it a bit on a more capable box, although it's conceivable that I could do it all on the Rπ itself.
Oh the horror! A proven source-code control system.
M-x My-lawn-remark$