Do Browse like a user wouldTake natural pauses that users would take to consume page contentFocus on the most common use cases, rather than all the possible use casesTake note of pages where forms/logins occur, you will likely need to complete some scripting there

But, let’s be pragmatic for a second, the 80/20 rule states that you get 80% of the value from 20% of the work and a couple of simple tests are vastly better than no tests at all. Start small and simple, make sure you get something out of the testing first, then expand the test suite and add more complexity until you feel that you’ve reached the point where more effort spent on realism will not give enough return on your invested time.

Load Testing Manifesto Simple testing is better than no testingLoad testing should be goal orientedLoad testing by developersDeveloper experience is super importantLoad test in a pre-production environment

I was able to use the "Gift to a Friend" link on HB on a game I already owned and was able to generate an email to a friend. They were able to successfully get the game.Seeing that my Steam account is linked to HB, I was more worried about clicking the "Reveal Your Steam Key" and getting hosed that way.

It's a good practice to create respond_to_missing? if you are overriding method_missing. That way, the class will tell you the method you are calling exists, even though it's not explicitly declared.

In my opinion respond_to_missing? should never return true as default. Instead, it should be something like check_if_method_meet_condition || super . Another thing is that it is usually defined as respond_to_missing(method_name, include_private = false)

On Fri, May 29, 2015 at 5:04 AM Apurva Jalit <apurv...@gmail.com> wrote:Hello all,I want to use the hypothesis chrome extension/bookmarklet with my own backend. Great. I have written APIs at the backend that enables actions that can be performed from the chrome extension. To test that, I used the files on my system that were installed with h chrome extension from the chrome.google.com/webstore/. I just changed the value of href on lines 18 and 25 of app.html and set it to my localhost server and everything seemed to work.That's most of it :).Sometime soon it would be nice to have a build system that makes it easy to build the extension without all the Python dependencies and the main repo. I think we should extract the Chrome extension to its own repository at some point, and the same for the main client code. But I eventually want to build a different chrome extension that internally uses hypothesis scripts for the annotation functionality. Thus I need to make it completely independent of any resources hosted on hypothes.is. To do that I certainly need to make changes in the hypothesis chrome extension source code and not use the files I have been using till now. To do that, I seek answers to the following questions. Apart from changing the server details, I also need to make some changes to the sidebar: Just add some text boxes to be able to kind of bookmark the page in addition to ability to add notes. It depends on the changes you want to make. Here are some thoughts and ideas to get you started:The Chrome extension is a small amount of code (in h/browser/chrome) for managing the state of each tab. The rest is just the vanilla client code (in h/static/scripts) and the sidebar view rendered to a static file (the h/templates/app.html served by /viewer stored into an app.html file in the extension bundle).To build everything without changes, but just using a different API server, you can run the extension build command: hypothesis-buildext. $ hypothesis-buildext --help usage: hypothesis-buildext [-h] config_uri {chrome,firefox} ... positional arguments:  config_uri        paster configuration URI optional arguments:  -h, --help        show this help message and exit browser:  {chrome,firefox}    chrome          build the Google Chrome extension    firefox         build the Mozilla Firefox extension Doing this right now makes me realize we're missing documentation for two very important options for this command, --base and --assets.--base is the base URL of the server. It is the root where /api is the API service document (see https://hypothes.is/api).--assets is the base URL for static assets. For a Chrome extension, this should be chrome-extension://<extension id>/publicThe build output goes into build/chrome.Customization gets more complicated from here. Everything is tied to the Python package for building. This makes it harder for someone not familiar with Python and Pyramid, but it's also powerful.The best way to make changes to the application is to make your own Python project and add a dependency (using a requirements.txt file) on the h repository. Then, copy the .ini from h and start changing things to your needs.Examples of things to change:- Enable or disable feature flags- Set the webassets.bundles key  This defaults to "h:assets.yaml" which means "the file called assets.yaml in the h package" to Pyramid. This can be a whitespace separated list of files, with precedence to those files listed first. See the assets.yaml file and then make your own, redefining any bundles you want to change. This is currently the best way to change the JavaScript or CSS without forking.- Make template overrides  If you create a Python package, foo, and have an __init__.py with a function called "includeme" at module scope, you can use Pyramid's asset overrides to substitute your own templates in place of anything in h/templates.For the last of these two ideas, you will need to be familiar with Pyramid and particularly its asset system: http://docs.pylonsproject.org/projects/pyramid/en/1.5-branch/narr/assets.htmlThen there are modications you can do to the JavaScript. You can use Angular's dependency injection to override any of the built in services or controllers, but you will have to figure this out on your own.One thing that is designed to be pluggable right now is authentication. If you have no need for the user account system, or you want to handle authentication your own way, the accounts bundle is kept separate so that you can write your own JavaScript for that. It is not necessary to implement our user API. It is designed to be optional and separate from the annotation API.2. Is there a list of resources that the extension uses from the hypothesis server in the production mode? Any other files like app.html which are fetched from the server? I will need to host all such on my server too.None. The production extension bundles all its assets. Show trimmed content

Robert Sedlack, my professor for Visual Communication Design I (who also happened to be my advisor and the driving reason why I decided to join the design program) banned two phrases during critiques in his class: “I like” and “I don’t like.”

Teaching classes

teaching

Success

intentionally take on projects your only partially qualified for.

Finding your teaching groove after a long stint away from the classroom.

check in with your students; extend availabilities to meet; offer feedback, and follow up

Thoughts on bringing current events into your classroom.

assignment sheets

female graduate students

A Scholarly Approach to Your Career

Afterwards I followed up with practitionersand asked if the conversation provided useful information addressing their cu

It’s aspirational porn, which serves the dual purpose of tantalizing the viewer with a life they cannot have, while making them feel like some sort of failure for not being able to have it.

I don't think passing the entire http client is very idiomatic, but what is quite common is to pass the entire "environment" (aka runtime configuration) that your app needs through every function. In your case if the only variant is the URL then you could just pass the URL as the first parameter to get-data. This might seem cumbersome to someone used to OO programming but in functional programming it's quite standard. You might notice when looking at example code, tutorials, open source libraries etc. that almost all code that reads or writes to databases expects the DB connection information (or an entire db object) as a parameter to every single function. Another thing you often see is an entire "env" map being passed around which has all config in it such as endpoint URLs.

One thing Component taught me was to think of the entire system like an Object. Specifically, there is state that needs to be managed. So I suggest you think about -main as initializing your system state. Your system needs an http client, so initialize it before you do anything else

For the sweet spot you're looking for, I suggest being clear about if you're designing or developing. If you're designing and at the REPL, force yourself to step away with pen and paper after you've gotten some fast feedback.

Writing is selection. Just to start a piece of writing you have to choose one word and only one from more than a million in the language. Now keep going. What is your next word? Your next sentence, paragraph, section, chapter? Your next ball of fact. You select what goes in and you decide what stays out. At base you have only one criterion: If something interests you, it goes in—if not, it stays out. That’s a crude way to assess things, but it’s all you’ve got. Forget market research. Never market-research your writing. Write on subjects in which you have enough interest on your own to see you through all the stops, starts, hesitations, and other impediments along the way.

Create an environment where your peers understand they don’t need to give up their entire worldview to consider your viewpoint or agree with you on one point.

Well, I worried about that. I sometimes don't like to confess how little I know about these things when I start them, but I'm starting to admit to myself that the less I know at the beginning probably the better it's going to go.

Listerine, for example, started life on the shelf as an antiseptic, sold as both floor cleaner and a treatment for gonorrhoea. But it wasn't a runaway success until it was marketed as a treatment for bad breath. 

But many ideas are destined for improvement

There are many people with good ideas who don't have the means, the will, or the courage to action them. Similarly, there are very talented business people who have no ideas, but are brilliant at the execution.

By decomposing the problem into pieces like this, we make it easy to build our project. Instead of one messy script that does everything, we define the data that will pass between the scripts, and make them completely separate from each other. When you’re working on larger projects, it’s a good idea to do this, because it makes it much easier to change individual pieces without having unexpected consequences on unrelated pieces of the project.

Rather than write a story true to the character or true to his situation, I wrote a puzzle piece to fill in negative space that didn’t need filling in. I don’t know WHAT WE GOT out of it in the end, and in terms of practical advice, if I can’t answer WHAT DO WE GET out of a story, then I don’t have a story.

less is more in a pitch. Imagine your editor on their most busiest day, on a day when all of their projects are seemingly on fire and due at the printer by lunch time, and then imagine that YOUR email is the one that comes in their inbox. A page. TWO pages at the most for a pitch. Unless they tell you otherwise.]

Continuity – the strict adherence of prior texts and their treatment as sacrosanct records – paralyzes comics all too often. It punishes new readers by their virtue of being new. It rewards trivia over opening up the world and blazing new trails. It cuts the pie into smaller pieces instead of making the pie bigger. It builds barriers and creates gatekeepers. And it’s really hard to write well.

As you get older, if you’re wise, you eventually stop trying to impress strangers who will probably turn on you anyway. You learn that you can still have good things and fun experiences.

keep the following in mind:

would like to encourage them to be as creative and inventive as possible. But the reality is that the academy is incredibly conserva tive .

If you are not pushing the envelope, why write?

When you write something, you never know who it is going to affect, or how it could help someone who’s struggling and feeling alone, or how in a low moment in their life, desperately searching on Google for answers, they will come upon your words when they need them most. And despite what our culture will have us believe—that metrics and stats matter above all else, that the number of clicks tells the whole story—somehow, in some calculation, impacting one human being has got to be worth more than all the unique page views and Shares and Likes in the world.

to make it "future-facing”

Advice to software development interns

People in this position have lost their sense of sight to detect when someone is approaching them. When you add headphones to the equation, they’ve now also lost their sense of hearing. Headphone use in a noisy open plan environment can be a catch-22. The noise is so oppressive that you want to block it out, but then you have to deal with the feeling of vulnerability and frequent startles of people approaching you from behind without hearing them.

Science says we're full of it. Listening to music hurts our ability to recall other stimuli, and any pop song -- loud or soft -- reduces overall performance for both extraverts and introverts. A Taiwanese study linked music with lyrics to lower scores on concentration tests for college students, and other research have shown music with words scrambles our brains' verbal-processing skills. "As silence had the best overall performance it would still be advisable that people work in silence," one report dryly concluded. If headphones are so bad for productivity, why do so many people at work have headphones? That brings us to a psychological answer: There is evidence that music relaxes our muscles, improves our mood, and can even moderately reduce blood pressure, heart rate, and anxiety. What music steals in acute concentration, it returns to us in the form of good vibes.

Message to My Freshman Students

Do your research elsewhere.

Never link to Wikipedia from your website.

Rule of thumb: When pulling changes from origin/develop onto your local develop use rebase. When finishing a feature branch merge the changes back to develop.

Speak your mind even if your voice shakes