Raygun Blog

I've been assembling a list of these lately for a book that I'm working on. (http://startingandsustaining.com) Some of the categories are fairly loose as some apps don't fit nicely into categorical buckets, but hopefully this is a helpful list.

--Browser/Email Testing

BrowserStack (http://www.browserstack.com)

Litmus (http://litmus.com)

--Bug/Issue Tracking

BugHerd (http://bugherd.com)

Lighthouse (http://lighthouseapp.com)

Sifter (http://sifterapp.com) (Disclaimer: I built this.)

--Planning & Project Management

Sprintly (http://sprint.ly)

Podio (https://podio.com)

Flow (http://www.getflow.com)

Interstate (http://interstateapp.com)

Basecamp (http://basecamp.com)

Apollo (http://www.apollohq.com)

Pivotal (http://www.pivotaltracker.com)

Asana (http://www.asana.com)

Trello (https://trello.com)

Blossom (https://www.blossom.io)

Trajectory (https://www.apptrajectory.com)

--Business & Traffic Analytics

KissMetrics (http://kissmetrics.com)

MixPanel (http://mixpanel.com)

DigMyData (http://digmydata.com)

--Continuous Integration / Code Quality

Travis (https://travis-ci.org)

Circle (http://circleci.com)

CodeClimate (http://codeclimate.com)

Sempaphore (https://semaphoreapp.com)

--Dashboards

Ducksboard (http://ducksboard.com)

Geckoboard (http://www.geckoboard.com)

Instrumental (https://instrumentalapp.com)

--Error/Exception Handling

Sentry (https://getsentry.com)

Coalmine (https://www.getcoalmine.com)

HoneyBadger (https://www.honeybadger.io)

BugSnag…

Raygun | Seattle, US & Wellington, NZ | Engineering & Sales | Permanent Full time | Onsite

----------------------------
----------------------------
----------------------------
-------------------

Raygun gives developers the power to create perfect software experiences on a global scale.

----------------------------
----------------------------
----------------------------
-------------------

Https://raygun.com/careers

Sales Roles | Seattle, US

Sales Development Rep
Account Executive
VP of Sales
Customer Success Manager

Get in on the ground floor of an already successful SaaS business! How? Raygun (https://raygun.com) is setting up a sales office in Seattle – it’s first sales office globally. The Raygun Platform is already in use with thousands of customers in more than 100 countries. We’re a high growth, but profitable, business. We achieved this with a great product coupled with great marketing. Simply put, you’ll be helping find new leads for a product that has proven value to software development teams in a rapidly growing market.

Engineering Roles | Wellington, NZ

Software Engineer - We are always on the look out for awesome software engineers

You love coding to the brink of obsession! The code you write is clear, easy to maintain and unit test. You care about the user and you get a kick out of building features they love using. You will excel in a collaborative and agile environment where we deploy continuously, measure everything and take…

Raygun | Developer Evangelist | San Francisco | https://raygun.com | Negotiable

As a full time Raygun Developer Evangelist you'll be responsible for spreading the word about Raygun to developers around the world, online and in person. Raygun is growing FAST and needs social coders to help us reach and enable even more developers to build better software.

A successful Developer Evangelist has equally strong technical and people skills. You love to code, but you love to talk to people about code just as much. The ideal candidate is a software developer interested to share their knowledge and passion with other developers.

Does this sound like you?

* You build apps and code in your spare time just for fun.
* You love teaching others about new things.
* You blog about your technical escapades and discoveries.
* You participate in online communities like Twitter, Stack Overflow and Hacker News.
* You attend hackathons, conferences and meetups to build new things and network with other people.
* You keep up with new technologies, trying many of them out for yourself.
* You enjoy giving technical talks and presentations.

If you regularly do many of these activities, you'll enjoy being a Developer Evangelist!

Candidates can apply for this exciting role at - https://raygun.workable.com/jobs/246682

https://raygun.com/careers

>After watching that talk, I would have loved somebody in the audience to point out instance like this https://raygun.com/blog/10-costly-software-errors-history/ and ask for Hickey's comments.
Needless to say I really don't agree with that list, as history shows the inconsistency, typos, lack basic units and the ability to express them in a computation etc., have been more catastrophic than he believes them to be.

From the list you cite, only three of 10 errors are caused by "typos", "lack of basic units" and type errors.

And this is just a particular list.

Recalling Rich Hickey list, the things that cause more problem in code, from worst to less damaging:

Domain Complexity
Misconception

10x

Place Oriented Programming
Weak support for information
Brittleness/Coupling
Language model complexity
Parochialism/context
weak support for Names
Distribution
Resource utilization
Runtime intangibility
Libraries
Concurrency

10x

Inconsistency
Typos

I'm pretty sure that if we compile a list of real-life cases where the major reasons of failure according to Rich Hickey have caused trouble, the list of examples would be immense, compared to "typos".

Looks like a top notch implementation that's had some serious effort put into it for solving their unique pain points around deploys and monitoring. My colleagues and I at Raygun (https://raygun.io) have created an error tracking service that from an overview ticks the boxes that Haystack supports, and a whole bunch more besides for dev teams who don't happen to be GitHub :)

Tools like these become pretty invaluable when releasing code into the wild, and aside from lifecycle benefits like greatly reducing the cost of the maintenance phase, an error tracker can also alert and hand the data needed to fix the bug right to the person who can, greatly increasing dev sanity (no more relying on support ticket ping pong, and removes the onus on the end user to report the bug). Also, surfacing the attack vectors and the frequency of which adversaries attack code exposed to the web is rather eye opening.

https://www.androidpolice.com/2018/03/22/google-warning-developers-include-prominent-crash-reporting-disclosures-apps-face-removal/

https://www.reddit.com/r/androiddev/comments/868ie7/google_play_violation_about_disclosure_of_crash/

https://docs.instabug.com/docs/gdpr

https://stackify.com/about/gdpr/

https://raygun.com/gdpr

https://www.loggly.com/about/privacy-policy/

https://www.sumologic.com/compliance/what-is-gdpr/

https://logsentinel.com/gdpr-practical-guide-developers/

https://help.papertrailapp.com/kb/how-it-works/security-compliance/

https://www.landoop.com/blog/2017/12/apache-kafka-gdpr-compliance/

https://www.splunk.com/en_us/solutions/solution-areas/security-and-fraud/compliance/gdpr-compliance.html

https://www.elastic.co/gdpr

https://www.google.com/intl/en/cloud/security/gdpr/