You are reading a single comment by @allObjects and its replies.
Click here to read the full conversation.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@allObjects
If I could start over, I'd place the code in git hub, because it has repository quality, most of all it has version control. Since this forum started on this platform, most of the code sits spread out in the posts of conversation. I was thinking of writing an extractor that would put the whole forum into a better searchable place. But this may stay just as a thought. For sharing and discussing, the forum has a nicer format than github has with its comments. Often it is not possible to share the full project, so aspects are extracted and abstracted and discussed in a focused form on the forum. Asking for help works better on a narrower scoped subject than a complete project. The completeness of a project complicates the understanding of the issue at hand by others, or at least obfuscates it.
The reference documentation is complemented by the tutorials and the module examples. Where there is more about a particular feature, the reference documentation points to it. Most of my input I draw from the module examples and what forum members posted about it and their experiences.
Project with MCs are usually smaller and have a smaller set of - but very distinctive -requirements, last but not least because of the resource restrictions. Pretty quickly I adjusted my style of solutions to preserving resources, even the few there are.
Writing large (admin and self-service) Web application across full stack with nearly unlimited resources grew a pattern on me that was not portable into the space of IoT peripheral devices. I get remembered the time when business applications had to fit into 16KB or KWords - words of 8...14..18 bit - including indexed/keyed record access software and basic disk access/lock instructions do do multi-user applications. I'm glad these times have passed, but thankful, because the lessons learned still serve me today when in big data performance and footprint tend to stress the limits no matter how much resources are thrown at the problems. Certain things just have to happen full circle within an hour or two to have a global availability. Just like a great infomercial figure claims: *There is always somewhere sunrise that justify eating the favorite cereal any time!
Is your first application the equipping of the wind direction and speed indicator in the back yard with a MC? The MC could measure direction and speed - and may be temperature as well - and be a wireless connected Web server to provide data for personal weather station on desktop / laptop / wifi gadget?