ben-coman

8 ms·

31.
by ben-coman 9y ago
Mostly construction and commissioning for industrial/mine site 11kV distribution through to MV/LV motors; and a stint in asset management at a 400MW generation plant. Haven't touched transmission.
32.
by ben-coman 9y ago
I'm only a hobby Pharoer (my day job as electrical power engineer is not programming) but on the mail-list I see newcomers describe Pharo as "fun" and as "a breath of fresh air" compared to their day job. You would
33.
by ben-coman 9y ago
I came to Pharo after the fork from Squeak. What I have picked up is that prior to the fork, there was significant tension between those that wanted to maintain backward compatibility and those that wanted to move the language forward. Th
34.
by ben-coman 9y ago
You may be interested in the bootstrap work Pharo has been doing... http://www.esug.org/data/ESUG2016/04-Thursday/1000-1030%20Mi...
35.
by ben-coman 9y ago
The development workflow for Pharo is that every code change has a CI performs a bootstrap build of the whole system pulled from a git repository. Then your CI adds your production code on top of that. So it doesn't get lost in the mas
36.
by ben-coman 9y ago
Pharo doesn't need to be "installed". It can run from any directory. Typically your Image may be 30MB and the VM 5MB, so you just need to drop the two in the same folder via a zip file or whatever platform packaging tool yo
37.
by ben-coman 9y ago
Here is a nice Pharo TDD video (thx Avi) from an author of several Ruby books, when he was trying Pharo... http://www.virtuouscode.com/2015/05/11/in-which-i-make-you-h...
38.
by ben-coman 9y ago
A bit of context from the original community mail list post, "it supports post mortem debugging by saving a zipped execution context onto S3. This is particularly satisfying as at a recent serverless conference (JeffConf) there was a p