Protocol buffer and SQL links

PHP Protocol Buffer to MySQL (and back!) bridge
http://stuporglue.org/protocol-buffer-to-mysql-bridge/

Protobuf ORM
https://github.com/rene-post/protobuf-orm

one way: sql-protobuf
https://www.npmjs.com/package/sql-protobuf

MySQL-protobuf
https://github.com/google/mysql-protobuf/wiki

proto-sql
https://github.com/commandus/proto-sql

Epic chest

Just got a epic chest.

7 Advantages of prototyping with modular hardware

• Reuse tested hardware and software. The first time you do anything it always takes longer than you expected. There is a magnitude of things that can go wrong or were not planned. By starting with known working hardware, you can reduce the number of variables. Firmware for hardware takes time to work out all the bugs to make is reliable under all the operating states. Not only that but if you are writing firmware drivers and you have interment hardware you can literally go crazy troubleshooting your code, when the hardware is at fault. By starting with a known starting point your risk is greatly reduced.
• Quick to illiterate and experiment. If a design is modular you can try out new ideas until you figure out something that works well. You can build several versions of the hardware and see which path is the best one. If there are several sensors that do the same thing you can compare them side by side. The power to experiment provides a way to discover new ideas and truly innovate.
• Easy to pivot if something goes wrong. Murphy’s Law is always in effect, even the best designs can have unforeseen issues once put into play. With a modular design, you can swap out what doesn’t work and replace it with something else with minimal disruption of the rest of the design.
• Make a custom solution to the problem. When prototyping with a typical development board, they typically attempt to include every possible interface on one large circuit board. Often is the case you only need a few of them, and the rest is unneeded. The development board also includes power supplies and other support logic that may not apply or go against your design. This often makes a large bulky solution that can make prototyping difficult in some cases to large or inconvenient to test. With a modular hardware design, you just choose what you need without all the extra bulk, also since each block is chosen for your solution you have exactly what you need and is truly a custom solution.
• Minimize time and money designing hardware. Designing custom hardware is expensive and time consuming. The typical design process can take many weeks for a simple design, and unlike compiling code it takes weeks to try out each version to make sure it works. Often the first version of hardware doesn’t work the way you intended and you need to repeat the process several times. If you can just pick and choose from a list of proven designs this is a huge time savings.
• Only design what you need. If there exists modular hardware for 99% of your design, then you can greatly reduce the focus of your hardware design to just the 1% that is different. Now 100% of your time can be devoted to making your 1% as best as possible without worrying about everything else.
• Lower your risk before you make your final design. Once you have prototyped your entire design, you can write all your software as if was running on production hardware. Because of this you know it will work the way you designed. You can show it to potential investors and customers and get early feedback that is invaluable. The confidence of a proven working prototype that is close to the final design allows smart business decisions to be made rather than gambling and hoping that things go as you planned.

If you want to read more about this concept, check out this page: http://www.pureengineering.com/projects/modularsensor