The cool startup I worked for couldn't make enough money selling to scientists. "The money" insisted we try selling to the military. This went fabulously well: we got bought by a defense contractor. I walked out on moral grounds.
Absolutely! In my experience, statically typed languages are great when your goal is production; dynamically typed languages are great for quick demos.
Right. It's not the poor guy that turned off the power supply. It's the shit-for-brains managrrs who wouldn't let the engineers put in redundant power supplies and hired cheap lobour that had no clue how to architect for fault tolerance.
If you're slightly more flush with cash, an NVidia TX2 is freaking awesome for this. The DevKit has all you need, except the battery and a box. Fancy devtools like NetBeans and IntelliJ fly.
I've had one curved TV, and it was very nice when my head was in the sweet spot at the center of curvature, but anywhere else, meh. Monitors are another thing: I've got one of the 34" Samsung monitors, whose curvature is set for a good reading distance, and it's an awesome experience. I now find extended periods with flat monitors to be awful.
I know, I know. It makes me sound like a fanboy. But the feature that pushed me over the edge was the Auto Unlock feature. Now I have a strong password on all my computers that I don't have to type. Totally life changing.
People have been building such systems for quite a while: long-duration robust robots that have to survive in hostile situations without continuous human assistance. Just look at what Liquid Robotics builds.
Relieve the nightmarish congestion in (for example) the San Francisco Bay Area by tunnelling new freeways. If Tech can bring the cost of tunnels down far enough, we could really improve cities everywhere.
Lots of cellphones always have their microphones on, listening for things like "hey Siri". Gunshots are easy sounds to recognize: recognize them and automatically post alerts (911?? Human to double-check sound?)
A key success metric will be milliseconds-to-first-lawsuit. 4 digits? 5? It'll sure be a non-Samsung shopping opportunity for me if my TV starts exhibiting this behavior.
I've had great luck with the modules from Leopard Imaging. They have a REST interface for configuration and stills. RTSP works perfectly with clients like VLC. Nice range of lenses. Designed to be embedded. Sweet.
I'm north of 60 too. Very well paid. I still get in the hacking zone frequently. I work on cool new stuff all the time. Learning has been lifelong. Took a couple of turns as a manager and didn't like it. I keep getting asked to be a manager, I mostly say no. Age discrimination is very real, but in talking with friends it's clearly worse in management. I'm totally happy with having stuck with what I love.
I've been involved in 5 of these ERP conversion efforts. The ones that failed used big expensive commercial products and giant teams of consultants. Hugely expensive. Kinda limping along. Both of the successes were outfits that decided to just build what they needed inhouse, skipping consultants and giant ERP packages.
I'm an inch away from 60. Happy as can be slinging code (mostly Java). I've had periods in my career where I've been up the management chain, but I never really felt alive. There's something about the magic of getting something really complex to run. Coding pays at least as well as management, especially if you're working somewhere that has Hard Problems (as opposed to just cranking out yet another form). The added bonus as you get older is that you need less sleep.
The last months of a persons life are overwhelmingly the most expensive, but the outcomes are predicable. There was a great article in the WSJ on this called Why Doctors Die Differently - http://online.wsj.com/article/SB10001424052970203918304577243321242833962.html . The basic point is that doctors understand death, and when their condition makes death inevitable. They almost always opt for more life in their years than more years in their life. From a healthcare point of view, doctors have much less expensive end-of-life care.
As a life-long programmer myself, I've always had great relationships with the tech writers I work with. For one, I may be excellent at coding, but I'm crap at prose, and the delicate task of writing prose that is both understandable and accurate is a truly hard skill. Programmers need to have a little humility towards, and understanding of, tech writers. The other big thing about tech writers in my career has been that if a tech writer comes to me and says "I don't know how to describe this" it occasionally means that the tech writer is an idiot, but more often it means that my code isn't as clean as needed, and almost certainly has a clumsy UI.
Check out http://sveasoft.com/ - they have firmware loads for commodity WiFi nodes that turn them into excellent mesh's that do exactly what you want. Excellent tech, dirt cheap. Easy.
It's a game. Get over it. Give him an account that has zero privileges. And set it up to log whatever he does. 99% chance that he only logs in once and does nothing more than peer around for a minute. 1% chance of interesting:-)
Slashdot Mirror
The cool startup I worked for couldn't make enough money selling to scientists. "The money" insisted we try selling to the military. This went fabulously well: we got bought by a defense contractor. I walked out on moral grounds.
No, "real men" have better things to do with their lives than wade through drivel. I browse at +2
Absolutely! In my experience, statically typed languages are great when your goal is production; dynamically typed languages are great for quick demos.
Right. It's not the poor guy that turned off the power supply. It's the shit-for-brains managrrs who wouldn't let the engineers put in redundant power supplies and hired cheap lobour that had no clue how to architect for fault tolerance.
If you're slightly more flush with cash, an NVidia TX2 is freaking awesome for this. The DevKit has all you need, except the battery and a box. Fancy devtools like NetBeans and IntelliJ fly.
I'm still waiting for the "Tales of Known Space" to turn into a movie series.
I've had one curved TV, and it was very nice when my head was in the sweet spot at the center of curvature, but anywhere else, meh. Monitors are another thing: I've got one of the 34" Samsung monitors, whose curvature is set for a good reading distance, and it's an awesome experience. I now find extended periods with flat monitors to be awful.
I miss the word more that I'll miss the company.
I know, I know. It makes me sound like a fanboy. But the feature that pushed me over the edge was the Auto Unlock feature. Now I have a strong password on all my computers that I don't have to type. Totally life changing.
People have been building such systems for quite a while: long-duration robust robots that have to survive in hostile situations without continuous human assistance. Just look at what Liquid Robotics builds.
Relieve the nightmarish congestion in (for example) the San Francisco Bay Area by tunnelling new freeways. If Tech can bring the cost of tunnels down far enough, we could really improve cities everywhere.
Lots of cellphones always have their microphones on, listening for things like "hey Siri". Gunshots are easy sounds to recognize: recognize them and automatically post alerts (911?? Human to double-check sound?)
A key success metric will be milliseconds-to-first-lawsuit. 4 digits? 5? It'll sure be a non-Samsung shopping opportunity for me if my TV starts exhibiting this behavior.
I've had great luck with the modules from Leopard Imaging. They have a REST interface for configuration and stills. RTSP works perfectly with clients like VLC. Nice range of lenses. Designed to be embedded. Sweet.
I'm north of 60 too. Very well paid. I still get in the hacking zone frequently. I work on cool new stuff all the time. Learning has been lifelong. Took a couple of turns as a manager and didn't like it. I keep getting asked to be a manager, I mostly say no. Age discrimination is very real, but in talking with friends it's clearly worse in management. I'm totally happy with having stuck with what I love.
I've been involved in 5 of these ERP conversion efforts. The ones that failed used big expensive commercial products and giant teams of consultants. Hugely expensive. Kinda limping along. Both of the successes were outfits that decided to just build what they needed inhouse, skipping consultants and giant ERP packages.
The definitive "kitchen sink" for how to do everything.
If you want AWS compatibility, use Eucalyptus. It's solid, proven, open source. I've never understood the hype around OpenStack.
I'm an inch away from 60. Happy as can be slinging code (mostly Java). I've had periods in my career where I've been up the management chain, but I never really felt alive. There's something about the magic of getting something really complex to run. Coding pays at least as well as management, especially if you're working somewhere that has Hard Problems (as opposed to just cranking out yet another form). The added bonus as you get older is that you need less sleep.
As an aging geek, and as much as an aging body sucks, I wouldn't trade my wiser more developed brain for my younger body.
The last months of a persons life are overwhelmingly the most expensive, but the outcomes are predicable. There was a great article in the WSJ on this called Why Doctors Die Differently - http://online.wsj.com/article/SB10001424052970203918304577243321242833962.html . The basic point is that doctors understand death, and when their condition makes death inevitable. They almost always opt for more life in their years than more years in their life. From a healthcare point of view, doctors have much less expensive end-of-life care.
As a life-long programmer myself, I've always had great relationships with the tech writers I work with. For one, I may be excellent at coding, but I'm crap at prose, and the delicate task of writing prose that is both understandable and accurate is a truly hard skill. Programmers need to have a little humility towards, and understanding of, tech writers. The other big thing about tech writers in my career has been that if a tech writer comes to me and says "I don't know how to describe this" it occasionally means that the tech writer is an idiot, but more often it means that my code isn't as clean as needed, and almost certainly has a clumsy UI.
Check out http://sveasoft.com/ - they have firmware loads for commodity WiFi nodes that turn them into excellent mesh's that do exactly what you want. Excellent tech, dirt cheap. Easy.
It's a game. Get over it. Give him an account that has zero privileges. And set it up to log whatever he does. 99% chance that he only logs in once and does nothing more than peer around for a minute. 1% chance of interesting :-)
This is just Oracle's way of saying "Hey, you remaining engineers in Hamburg, your RIF notice is in the mail"