876 karma · joined March 12, 2012
"...an externality is the cost or benefit that affects a party who did not choose to incur that cost or benefit."
Noticed it was on sale, so I just picked up a two-year subscription. Suggest others do the same. Well worth it.
As an aside, I would also be willing to pay a _lot_ more for the quarterly, like 100-to-200% increase.
I've always viewed success as passionate curiosity. If the mindset is there, but not the skill, you can teach the later.
Or a brutally fast Handlebars implementation.
Sorry.
What kind of tech stack do you run? Last time I check it was mostly Javascript (ugh).
It's just a name for a mixture of a whole bunch of ingredients, notably onions and chutney.
Here's a recipe: http://www.food.com/recipe/monkey-gland-sauce-266015
The inevitable mixture of monkey-gland sauce with mayo when eating steak, is well, nothing short of glorious.
With enough focus and effort you could really turn this into a stellar product that I would use daily.
I manage my most of development through GitHub. Unfortunately, the processes around getting user input and bug reports, communicating changes and updates back, etc. all suck. Usually, you have to marry a thousand-and-one services together and thereby die by a thousand cuts, or setup some customized process (manual, with automation eventually).
Having that all tie in/around GitHub would be such a time saver, and would reduce a lot of duplication of effort.
---
For example, I want to:
1. Setup a milestone.
2. Create issues for features, bug fixes, and re-factoring that needs to happen.
3. Communicate this to users.
4. Tie in user feedback.
5. Develop the product, providing releases on some schedule.
5. Rinse and repeat until the milestone is reached.
6. Release. That means tagging, running CI to generate for all target platforms (native, woo!), and getting a Github release put together.
7. Communicating and delivering that to end users.
---
I can achieve this with a hodgepodge solution, as I mentioned before, but one service would be killer.
Only when the difference in performance is end-user discernible. I do make sure the code is well crafted in those bounds though. There's no _valid_ excuse for crafting ugly code.
Coincidently my stuffed toy that I have kept throughout my childhood was named "Mel the Pal." I just noticed the irony of that. :)
In the end, however, my reservations are mostly due to a "get off my lawn" mentality.
This is great for the general programmer (someone who is not knowledgeable or caring about details like this.)
Unfortunately, this blows for people who do (someone like me.)
Additionally, it sometimes makes sense to duplicate data to minimize cache misses. For example, translating/rotating/scaling entities in game engines. It makes sense to copy entity transforms (usually a matrix computed once) from a central manager to sub-managers for certain components. The memory overhead is traded for more efficient processing in sub-systems like rendering, animation, physics, etc.
---
[1]: http://en.wikipedia.org/wiki/False_sharing
[2]: https://software.intel.com/en-us/articles/a-case-study-compa...
[3]: https://software.intel.com/sites/products/documentation/docl...