Also continuing the basic Game Development (Unity3D) course at Coursera
Rather than fighting to understand webhooks from the various git-hosting services I've decided that volume is low enough that I should just host the git repositories myself.
I've spend a few evenings preparing for this transition, updating documentation, and reworking my codebase to avoid all use of webhooks.
It's a fun update, which will simplify the service for new users, but keeping both systems in use at the same time makes it a little more complex than I'd like. I guess I need a flag-day in a few months where I drop the old webhook support.
Even if the manipulation were local, the Amazon API would be remote, and not within a company's control.
Interesting idea though. Most of the backend is portable perl and easy to pull out..
Selling that as a one-off utility would be hard, but it does currently work well as a hosted service via the webhook integration-layer, and a small amount of git-magic.
I will have a think to see if people would prefer it self-hosted, though nobody has expressed any interest in that previously.
Fundamentally it involves picking a feasible solution from a solution space of (225 choose 45) possible solutions.
That number is obviously too big to brute force randomly, but I was able to get very close to a solution by hand, and so it feels like there ought to be an algorithm to generate a solution. (It doesn't feel like a problem where the solution wouldn't be polynomial time.)
It feels like some kind of branching with aggressive pruning would deliver a solution but I have much I need to learn first to actually develop it.
Continuing: Coursera Modeling Discreet Optimization: I wish MiniZinc had better tooling and documentation.
Can you whole-world clone the entire stack you're working on/with?
1. Verify the bug exists in your whole-world clone
2. Chop bits out of one of the copies until the bug goes away, and/or see if you can copy the whole world to another machine (which you've probably already tried)
Alternatively, perhaps let fixing this bug go, and as was suggested, use another machine (or a VM, if that's fast enough and it "fixes" it) for now. You might figure it out while you work on something else.
This position is horrid to be in :P but letting go right now in this situation is sometimes the least long-term damaging solution.
I'm currently polishing a Slack chatbot for engineering-notebook-chatops, working on some boards in Eagle for a universal, multicell NiMH charger, and also hacking on my fork of ReplicatorG (I'm trying to clean the code up, it's a bit WTF-y right now).
Also, I am working on adding a test suite to one of my previous applications that I made. I finished up the model/controller tests, so am on to the integration tests.
In terms of critiques, I know this seems like a petty critique, but it's important: make sure to check your spelling and/or improve your spelling in English. The word is spelled "definitely", for example. Since you're representing Heynay, it's important to give a good impression, and I can tell you that major spelling errors will give a poor impression to the majority of the population, particularly among exactly the people you want to impress.
Again, it's a petty criticism, but the small details like spelling are well worth paying attention to, as they serve as useful signals to many people.