drum

Even though you may not feel good at LeetCode type questions, study algorithms and data structures anyways!

Try watching YouTube videos, reading 'Cracking the Coding Interview' and get familiar with the programing language you are most competent with already or are trying to get a job with.

The best way to make up for a gap in resume or short stints at other companies is to prove you have the technical knowledge anyways.

The demo videos in the 'Installable' section should be up in your hero with the benefits listed alongside as subtitles. It took me a while to fully understand what your service does.

Coloft (closed), ROC (closed), and now Spaces - which is owned by Regus.

I have nothing but positive things to say about coworking spaces after having worked at them for the last 3 years. I've met great friends, business partners and clients. I think they'll continue to be important as the freelance and remote working economies grow.

Cool dialogue between PG and Jeff Atwood (StackOverflow cofounder) on the tweet thread - From Jeff: “You can always borrow concepts and ideas from other startups, too. It's good to look, and understand the competitive landscape in detail, but not to obsess over.“

Doh! Thanks for asking. Voltron is a white labeled version of Jira (which I did not realize when writing my post). Edited.

After using Jira for the last 2 years, Atlassian has struck me as the 800 pound gorilla that's resting on its laurels.

On my dashboard, I'm consistently annoyed by being shown the option of creating a new user account and having to decipher the UI to choose wether my ticket is a bug or feature during mission critical moments. Just give me one big button that says 'Create Ticket', we'll figure out the rest later. Secondly, why aren't tickets shown on the dashboard by default? When I log in, I'd expect to see what's going on, not have them tucked away in the nav menu.

Recently during a mission critical ticket, email responses to Jira threads were not creating new messages in Jira, creating massive delays in communication with the team until we figured out messages weren't posting. Diagnosing the issue later, it seemed to be due to file attachments in the email responses.

The problem I have with statements like this are that they apply to every large framework, not just Rails. ASP, Django, Zend, Cocoa etc. A combination of libraries are bound to be hard to update two major versions later when methods and variables are deprecated.