got rid of the stupid overlay advertisement Slashdot puts on my phone that keeps me from ever being able to read the very bottom of anything....
Of course I live in Texas.
I've seen snow stay on the ground a maximum of one day since I've moved to Houston, about five years ago.
That Trihawk was pretty cool. It's downfall was catering to the wrong market, I can tell from the video. I don't know how $15,000 scales to 1984, I would have to look it up, but the fact they were calling a specialty car demanding a premium instead of a budget mobile like the Elio probably is why nobody knows what it is today.
Cherry 2000, haven't seen that movie since what? 1991? I liked it back then, not sure if I would now or not.
I've been worried about it getting the Tucker treatment myself.
I've had a real motorcycle. At 74 MPG it didn't get the efficiency this thing does, I also wound up wet and cold at work in February a lot. I might just get another motorcycle, but my work commute will be with this thing.
in my cars.
There are two cars I want right now (well, one is being released soon).
1. The Elio for getting to work and back. Perfect for getting me and my backpack the 30ish miles there and back, and even good for going to lunch with a coworker. Excellent fuel mileage, and unlike a Smart Car (which doesn't really get that great of fuel mileage considering) I wouldn't be concerned about having to defend my manhood every time I stepped out of it or worry about random strangers trying to give me a wedgie for driving it.
2. The Subaru Outback as my vacation and haul the family around ride. The ability to easily carry many bicycles, kayaks, luggage, and people offroad, at good high cruising speeds Not to mention, great gas mileage for a rugged/versatile vehicle.
I don't care about data platforms, just the ability to interface with what's there. The Elio would let me put whatever I wanted in there and tie it to the stereo, I'm guessing a Nexus 9 would be perfect. The Subaru support Bluetooth audio so I'll put my Nexus 9 in there too!
Mod parent up!
I've been saying this since I was a we little lad. We do the jobs we like. I like I.T. I like computers, I have since I was a kid. My sister on the other hand liked crops and animals, she works in agriculture.
How is it that science can explain how and why our hormones and evolution drive men and women to different interest, yet science (or in reality H.R.types) can't accept the findings of science?!?!
Slashdot under current management is just pandering to the H.R. and equal outcome everything crowds.
Think we could lobby to have the traditional green changed to more of a lavender color?
Come to think of it the entire
Redundant huh? I would argue the article itself is at this point.
Why aren't they bitching about trash collectors, construction workers, and cattle wranglers being mostly men?
One of my favorite things about the job I referenced is most of the people we hired were in their late teens or early 20's and were eager to learn and prove themselves. To this day it's still the age group I like to work with the most. Of course I expected a lot of churn, I would have been disappointed at my trainees if they didn't ditch that place after some training.
I love interactive documentation - I find myself hovering my cursor on a regular basis on stuff I'm unsure of and I'm always disappointed when it doesn't work.
So years ago I was in varying positions at an ISP, but regardless of title "head tech" pretty much applied. We kept getting kids right out of high school that claimed to know computers well but had never used a command line, didn't know what an IRQ was etc.. As this was the Windows 95/98 era and this was a dial-up ISP some manuals had to be written.
I of course wrote them.
I made flow charts for email troubleshooting (I hated Visio so I used a graphical editor instead), I had grids for IRQ/Address settings, I had step by steps for undoing AOL I.P. stack sabotage (how many of you remember that?) Fact was I wrote really good documentation that anyone from teenager to adult could use to troubleshoot the "normal" day to day issues a worker at an ISP faces without making a condescending script. If you used it for reference it was an answer key, if you read every word you often would know why that problem occurred. I'm of the belief understanding an issue is always better than just knowing what the fix is.
Long story short - the documents leaked out of the company. On the north side of town there was a help-desk outsourcing company that tended to have a lot of employee migration with our own - in both directions. A buddy of mine went to work at a different ISP and saw my documents turn up there with my name replaced on the credit line (he knew I wrote them - he watched and knew the marks I put in things that were dead giveaways it was my stuff).
I no longer worked at the old company and was still finding out about my documents leaking all over the damned place. I decided to put the documentation GPL on the things and throw them out on my webserver. If figured if I put them out on the web myself then there was a verifiable copy out in the wild, it would shine a light on the plagiarizers, and I was hoping to maybe get offered jobs or something. Later I was criticized with "that really should have been Creative Commons". Fuck you, I did this before Creative Commons even existed.
My web server and the backups were physically stolen from my home, but there's still an archive. To this day I still write in the "explain it, don't step it" method.
Turns out lots of places want idiot guides and don't care to understand.
Because anyone who deserves the label tech knows better, it does however suggest you're an idiot.
My Casio is up to year 8 on the original battery. If my corpse fell where there was plenty of sunshine but not so much dirt as to wash up and bury my wrist I could see it going quite some time more. It's good for 200 meters diving, it should handle exposure for a good long time.