yaddayadda
Joined 14 years ago
Joined 14 years ago
As we submit to present at tech conference abroad and invite others to come to our country to present, we should be aware of situations like Rachel exprienced.
The BC I attended claimed to have a flipped classroom model, which would have been better that in instructor in the front of the class demonstrating code. In addition, I was apparently one of the few students who actually did want to change careers, so my "peers" were never willing to work outside of class. Despite my day job, I put in at least 2 hours outside of class for each how in class.
Even with the after-hours approach, if the classroom model had actually been flipped, and there were several peers to work with outside of class, it would have been significantly better, and I think I could get a junior dev job.
I certainly can't move to a full-time web dev job at a reasonable salary after the bootcamp I attended. If I was willing to intern for 6-12 months at minimum wage, I would be able to - but I could have done that without the bootcamp.
The bootcamp doesn't share stats, only a post-graduation "employment" percentage. Which is pretty meaningless, for example, I'm employed but not doing web dev.
Funds are being raised through https://www.indiegogo.com/projects/save-robomongo#/
I don't currently use Robomongo, but someone recently mentioned it as a useful tool and, well I'm a sucker for high-quality, open-source projects - I want them to be able to succeed or fail based on the product's merit not on the team's ability to raise funds! So, I'm trying to do my part and bring them a bit of HN visibility.
The explanation for smoothing days is that it "[controls] how strongly each weight value affects the trend". It takes an positive integer value or 0. The recommended value is 7, but I ended up with 14. With higher values, both the forecast line and average line tend to be less dependent on recent weights and average out over a longer period.
The forecast days "[control] how many days to use for the forecast calculation. It doesn't specify what the acceptable range is, simply that the minimum value is 2 and the recommended value is 7. I ended up with a 14 here also. This value only impacts the forecast line, not the average line.
[1] On my phone, reached via Android's hamburger physical button. [2] Reached via a button that looks like the ai-settings icon from the http://www.androidicons.com/ set.
http://www.appbrain.com/app/libra-weight-manager/net.cachapa...
https://play.google.com/store/apps/details?id=net.cachapa.li...
That's awesome!