Opbeat’s mission is to help developers operate their code together. And to do so, we have found that you need at a minimum four key components: Application performance metrics, release tracking, error logging and workflow.
Can you guess how long it takes an engineer to type a 60 character password into an iPhone?
Too damn long.
Good password practices are a key part of both personal and professional data security, but actually typing a large number of variable-case letters, numbers and symbols into a password field on a mobile phone is a time-consuming and error-prone process. We are simply spending far too much of our lives just logging into things.
Logging in to things is agonizing on mobile, and it is even more painful if you use good passwords. To help ease this pain we have added two new features to our iPhone app.Read on→
As developers, we have watched with knowing and wide eyes as the technological world around us has evolved. Somewhere along the way, a few bright souls realized something crazy – developers are people, just like the users of the software we create. And suddenly, no longer were the trappings of geekdom limited simply to the dark sorceries of the command line. Our tools have evolved, and we along with them.Read on→
This week, we are doing great progress on a bunch of new features that are not ready for prime time yet, but we figured we would leave you a little something for the weekend anyway. Read on→
It has been a while since we made a Friday Links post, so we figured we would treat you to a list of some Longreads we have been enjoying recently.
This is part two in our miniseries about our research trip.
“Dude. It is Andrew McCollum. The co-founder of Facebook.”
This was around 10pm on September 29th, 2012 in a small San Francisco hotel room on 5th and Mission – the evening before our meeting with Andrew McCollum. Read on→
This is part one in our new miniseries about our research trip.
“Spend half of the money on flight tickets and go validate your hypothesis. Then spend the other half building a prototype.”
This week, the whole team has been hard at work, updating both some general things in Opbeat (information architecture, how we handle notifications and the like), and the more specific stuff as well, like getting under the skin of how to group errors and display them (it is not the straight forward task it sounds like, but that’s alright).
We like coffee. The wake-up coffee. The pause-and-think-coffee. The crunch-mode coffee. The coffee I’m drinking while writing this blog post.
It’s always interesting to meet hackers with common interests, and to try to engage in the community that helped us get to where we are. Sometimes, that community can need a little help getting organized. This is what we learned from arranging our first local meetup.