valeriemettler's comments

I agree. Piecing together a bunch of extensions doesn't help improve my workflow. I love that it is all integrated here. Being able to share is great!

I started using https://histre.com/ a few months ago and I love it and would strongly recommend it. I can easily save information in notes, which has the option of being connected to a link or not. Then I can easily access the notes I created using tags I create myself (I love that it uses autocomplete!). Histre supports easily sharing your knowledge with others. You can share a single note with anyone, whether they are a histre user or not. You can publish a note just by tagging it with #pub (see https://histre.com/pub/valeriemettler/ for an example). You can also create a team and have a shared notebook where the entire team can have one central place to share and access useful information on any given topic. I recently got my team at work to start using it and they absolutely love it!

I also use histre to help me with any research I do online, especially when I start a new project at work. It's nice to be able to quickly collect things and have them already organized for me. Plus it keeps me from having to keep a million tabs open, which is a relief! ;) Thanks for making it!

I do have a feature request for you: I'd like to be able to share my project research links and notes with just my team. That would make histre super useful to me.

In my experience, closures are a topic that always comes up. It is also important to know how to handle a closure inside of a for loop. I've been asked about "this" binding, coercion, and CSS specificity. I've had to solve problems that required me to know about how to use stacks, trees, and nested for loops. Other topics that have come up are how to architect an app, concurrency, memoization, building out and handling api endpoints, and pass by reference vs. pass by value.

You may not think databases are a front-end topic, but I have been asked about them on more than one occasion. Prepare to talk about sharding, natural primary keys, what your favorite database is and why, etc.

Something that has been extremely useful for me is to have a project that I've built myself to show and talk about during the interview. Although I have had one interview where I was asked to talk in detail about how I built some of my projects that are in my github, I like to respond to general technical questions while referencing something I've built. A lot of times the interviewer will then use my app as a starting point into a discussion for how I would scale it. Here's an example of an app I built quickly and have used for discussion in interviews: http://moviemap.xyz/ More here: http://valeriemettler.com/

Software Engineer with design and UX/UI skills who is passionate about visual problem solving.

Location: San Francisco Bay Area

Remote: Flexible

Willing to relocate: No

Technologies: Ruby, Ruby on Rails, Javascript, Angular.js, Backbone.js, JQuery, Less, JSON, SQLite, PostegreSQL, MySQL, RSpec, Capybara, Jasmine, Heroku, Coda, AWS, Responsive web design, UX/UI Design, Adobe Photoshop, Adobe Illustrator, Adobe InDesign, Git

LinkedIn: http://www.linkedin.com/in/valeriemettler

Portfolio: http://valeriemettler.com

Email: [email protected]

Web developer with design and UX/UI skills who is passionate about helping organizations solve problems.

Location: San Francisco Bay Area

Remote: Flexible

Willing to relocate: No

Technologies: Ruby, Ruby on Rails, Javascript, Angular.js, Backbone.js, JQuery, Less, JSON, SQLite, PostegreSQL, MySQL, RSpec, Capybara, Jasmine, Heroku, Coda, AWS, Responsive web design, UX/UI Design, Adobe Photoshop, Adobe Illustrator, Adobe InDesign, Git

LinkedIn: http://www.linkedin.com/in/valeriemettler

Email: valeriemettler at gmail