Hacker News new | past | comments | ask | show | jobs | submit login

I had to fight a lot to stop colleagues doing the long change a variable, reload, renavigate, trigger some dom event and wait.

Obviously I come from a lisp heavy culture, but I'm still stumped how many people stay in those high latency exploration mindset.




I work on embedded firmware that has a web UI (as embedded firmwares have nowadays). I don't touch it much, but when I had to a major bit of development on it, I did as much work in JS, out of a big JSON generated by the firmware. One thing that allowed me to do was to capture the page put out by the firmware and then iterate on that, and work the changes back to the original source files. In fact, I accessed it as a local file (file:// URL). Otherwise it's: run the build to make the firmware image; flash; reboot; wait for firmware to bring up webUI server; navigate to the page, trigger some DOM event and wait". :)


Pretty sweet trick. I even think this should be a generalized strategy in computing and taught in studies.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: