Interacting and exploring APIs is either the newest fad or a gold rush for new business, but one of the biggest things stopping me from using them is integration into my existing stable tools. webshell.io is another service which is hosting your code on an external service, leaving you vulnerable to fluctuations in their uptime or stability as a company. There may be new opportunities in turning this into a desktop application.
There's no automated service, but you can have the post office hold any package for you for a week or so. These guys look like they're going after the online retailer distribution market though, similar to Amazon's upcoming "lockers" platform.
That's a pretty interesting situation. I certainly don't think there's any "something" blocking you, I'd guess it's more of a vague feeling of caution that you're clinging to because you can't quite understand it. It's easy to get into these traps when it's something very important (like your job).
There are a few things you can try. You can create a personal project to explore the depths of "not refactoring", in hopes that you'll get used to it. You could also just try getting faster at your newer technique: writing code and refactoring in an hour instead of 3 (learning your tools like a master helps with this).
Your "sudden change" probably wasn't so sudden, but rather your experience with hitting the limitations of writing shitty code. Now you want to avoid those pitfalls in the future, but your boss doesn't seem to understand.
There's also plenty of places for you to go still, if none of the above works for you.
Edit: Creating a checklist of "the smallest chunk of work" can help you keep moving rather than getting stuck in tweakfinity.
Pair that with a slightly stronger form of data hiding by using TrueCrypt's hidden partition feature to encrypt the second OS partition. Just make sure not to ever boot into the honeypot os afterwards, or it could overwrite parts of the hidden partition. You can safely load the honeypot os by typing in the hidden password as well so that true crypt can load the proper partition boundaries.
In my current project we do actually stand up, although only due to the pleasure of the team leader. The main reason it's called a "stand up" is to serve as a reminder that it should be very short, 5 minutes max, or otherwise the time most people would feel comfortable standing for a meeting.
I'm not really sure how you're implementing scrum. Our scrum standups are always just the programmers, once a day in the mornings, and are used to keep all the programmers on the same page and talk to each other to find out if features might have a codependency, or if other blockers can be solved by something else another dev is working on. There's no "watching" of people or "intimidation".
You might want to speak to your manager next time something like that is happening, because there's no way it can be good for your productivity or the other people on your team. It's certainly not a normal practice. At the very worst, if someone isn't pulling their weight they should be dealt with in private.
The exchange doesn't have much of an effect when most goods are priced relative to the exchange rate (many sites even automate this). The only thing the currency price represents is the relative change in market size where these coins are used.
The sampling frequency doesn't directly effect the audio frequencies it can encode. Telephones do PCM encoding (meaning it has data representing the graph of the sound wave) at 8 kh/z. Following the nyquist sampling theorem (cut your rate by 2), this can allow frequencies up to 4 kh/z (as you said). It's not a hard cutoff though, you can still get most of the sounds above that pitch, they'll just sound pretty weird (as if you were talking on the telephone!)
There's a certain allure to saying code should be a certain way because of natural properties of computing, or our own feelings on what things are different and similar from what other things.
The reason OO shines is because it allows you to make that distinction at the domain level rather than the code level. You organize your software into business objects, or components, and have these interact with each other. They allow you to separate it out in a way that a new developer can come to the project, understand what the code should be doing, and look for the classes which seem the like objects involved, including the types of data it has and the things it can do.
There are all sorts of nasty things we've invented in OO over the past few years (mixing up inheritance and composition, using way too much state), but it gives us a lot of advantages from an engineering point of view.
Piracy isn't stealing; it's copyright infringement and often a contract violation. Using metaphors for complicated legal issues is not a good way to approach things.
I can't verify this, but unless you installed Helvetica manually, windows installations won't have it and will fall back to whatever is specified next in the family (usually Arial or the default Sans Serif).