Russia is quite like the U.S. when it comes to expanse of the land. There's plenty of superbly beautiful and unspoiled areas in Russia, if that's your thing. If remote work was feasible, he could live in the middle of nowhere just as well as in the middle of a big city. I would not generalize Russia to be a shithole. If you're on the wrong footing with the authorities, you'll fare equally poorly in any "civilized" country.
Frankly said, I'm at this point just tired of people who can't set up their build tools to automate common tasks, and who think that code generation is some disease that has to be valiantly fought, because obviously if you call anything besides the compiler it's too complificated.
Look, you're wasting lots of your time by not using code generators. And I do mean lots and lots. You even publicly and proudly admit to it. In any project of considerable size, you'll be using dozens of tools to produce the final executable, the documentation, etc., so you just make yourself look very silly.
If you're whipping up something quick and dirty in Qt, you don't care about any code generators that Qt internally requires. A four liner
Your rant sounds silly.
Given that from 10.9 onwards you have IP over Thunderbolt, I don't think you need Infiniband anymore. You can run XSan over Thunderbolt just fine, with a bunch of macs in a mesh network. All you need is thunderbolt cables, no other hardware needed.
Agreed: Arduino is really just a packaging for a common Atmel microcontroller, with a bootloader, and a development environment that tries to pretend it's not C++. Anyone who actually knows how to program microcontrollers doesn't specifically care for an Arduino, they'll use one the the bajillion Atmel parts that are exactly fit for the job, use Atmel Studio to develop and debug, and a proper tool to connect to the chip. Atmel has such a variety of parts available that constraining yourself to a limited sub-family of parts is just going full retard about it.
Arduino is a platform designed for hobbyists. Asking for an "experience" with it, when looking for engineering talent, is almost insulting. Any EE worth their salt will understand what the platform is good for and will be able to leverage it where it makes sense. And about the only situation it makes sense, in a commercial product, is when you specifically want to have very easy firmware tweakability using simple development tools. Basically if you're targeting people who get confused by all the buttons in a full-blown IDE.
I can't agree more. If you really need external sensors, put them in simple $0.50 off-the-shelf enclosures with a couple minutes of kitchen table machining done to adapt them to your application. Learn how to cleanly superglue lenses/windows etc. Repurpose other off-the-shelf parts - say use IR motion sensor lenses for your trigger lenses, if you need a wide-field Fresnel sort of an IR lens. Reuse $1.00 off-the-shelf cables that you can buy in bulk on eBay to connect sensors to the main unit. If they break, you can even afford a warranty replacement with $1 for shipping via USPS, duh.
Again, use off-the-shelf enclosure, get a custom keyboard/label combo, but for crying out loud, don't go into making full custom plastic molds! And have some in-house talent to at least run the engineering team. I do agree that 3-4 people should have had it wrapped up in 6 months. Geez.
They've made some very major blunders. First of all, for that price and that sales volume, you go with an off-the-shelf enclosure and machining that can be done in your kitchen, if need be. Yeah, the custom pluggable enclosure looks cool, but is wholly unnecessary. A membrane keypad with display and other windows can be had cheaply even when full custom. All in all, they've totally overdesigned it physically. If I wanted to develop open source firmware for such a device, giving my time away for free, I could probably make a profit on such a device in qty 100, never mind thousands. Sure it wouldn't have a full custom look, but it could be done for the price point they quoted.
IOW: What a clusterfuck.
That's nice, but I really don't understand the uproar. The quality of some answers is very poor, and the average quality of both answers and questions seems to be, well, nothing to write home about either.
Holy shit, the CMD controllers! You brought back some bad memories.
I don't think that the shortcomings of broken blog engines are supposed to influence programming language design.
If I have to copy-paste something from a blog into an editor, then run autoformat on it, I might just pass on. Frankly said, people with shit worth posting know how to manage their formatting. If a post is so broken as to be unreadable, it's most likely useless code anyway.
If your blog "engine" can't handle a simple pre-formatted code block without tabs, you're doing things wrong. A lot of blogging tools out there seem destined for the barely literate, where a few paragraphs of text and a few pictures is the pinnacle of expressiveness. It's too bad that those tools mess up Python, but they mess up C/C++ and everything else equally badly: it becomes an unreadable mess.
Given that a space cannot be re-configured to mean something else, as opposed to tabs, I simply stopped using tabs for indentation long ago. Any decent editor knows how to deal with indentation without a 1:1 mapping between the Tab key and the TAB ASCII control code. So, I really don't see a problem.
echo 'int main(){printf("hello\n");}'|gcc -xc -&&./a.out
Nope, you don't need the spaces.
He would have saved way more, then, by simply blowing in $250 of insulation into his attic, and investigating an upgrade to his HVAC system. Heck, even with the old HVAC system, just replacing the windows one-by-one yourself offers a way better payback. He must have had it real bad beforehand.
Never mind that a modern HVAC system's "thermostat" is really an application-specific terminal with a 24V power input and a CAN connection in the back. It's like an OBD-2 scanner: you have access to full diagnostics of the heat pump and the "furnace" (fan coil), and a multitude of settings to fine-tune it all. You will get informed when your air filter restricts the air flow too much due to it being dirty, when you lose refrigerant, etc. That's what you can get with a $7k system for a 2000 sq.ft. house, give-or-take. On such a system, a Nest thermostat is just as bad as a dumb thermostat would be - and you definitely don't want a dumb thermostat there!
Really, no modern HVAC system should have a dumb thermostat, but it shouldn't have a Nest either. It needs a terminal-thermostat that's designed to bring the system's features to the end user. And nobody who owns a house over 1000 sq. ft. should ever replace their HVAC system with a dumb one that doesn't have modern controls and diagnostics - it's a waste of money.
Nest is, unfortunately, an idea so dumb that it truly baffles me how can supposedly intelligent people come up with it. Any decent residential HVAC system comes with a smart thermostat already, and most of the efficiency gains are due to the efficient two-stage heat pump, variable speed blower fan, and a multitude of sensors that monitor it all and let the thermostat drive it appropriately. If I were to replace my default thermostat with a Nest, I'd actually lose lots of functionality for what: a perhaps better aesthetics and a remote access feature of dubious value.
At the very least, the Nest people should have reverse-engineered the rather trivial CAN-based protocols used by the few common smart thermostats and supported those. If you don't have money to buy a decent, modern and efficient HVAC system, you're not in Nest's market anyway. And when you do have a modern HVAC, a Nest is a step back.
It seems to me that Nest's designers only ever lived in crappy housing with old HVAC controls, and have no engineering background in HVAC. I feel a bit sad for the consumers who got tricked into buying a Nest - it's about the worst way they could have spent their money. In all seriousness, they'd get more utility had they spent the same amount on a used tablet or somesuch.
I don't rally know what point you've tried to make. I did not address at all whether the problem is endemic to engineers or not. I'm not saying that all engineers around me are incompetent, only that a lot - way too many - are not. The people I work with are always better at me at many things - that's a precondition to their hiring
Always draw your curves, then plot your reading.
